Bolt.new AI and ScheduleOnce integration: Step-by-Step Guide 2025

To integrate Bolt.new with ScheduleOnce (now called OnceHub), you don’t connect “bolt” itself to ScheduleOnce. Instead, inside a Bolt.new project you write standard API‑based integrations. The correct approach is: create an API key in OnceHub, expose the endpoints you need (usually booking data via their REST API or receive booking events via webhooks), then call those APIs from your Bolt.new backend code using environment variables. Bolt.new is simply the workspace where you build the app that talks to ScheduleOnce.

 

What You Actually Do to Integrate Bolt.new and ScheduleOnce

 

You build a small backend inside Bolt.new that uses OnceHub’s real API and/or receives their webhook events. No magic connectors — just HTTPS requests and signatures from your Bolt.new server.

• Create API credentials inside your OnceHub account (they call these “API Keys”).
• Store that key in Bolt.new environment variables (never hard‑code it).
• Make REST API calls from your Bolt.new backend to fetch bookings, users, or schedules.
• Register a webhook URL (a Bolt.new route) in OnceHub so your app receives booking events.
• Process events such as new booking, rescheduled, canceled.

 

Step‑by‑Step: Proper Integration Flow

 

This is the correct real workflow you would use in Bolt.new.

• In OnceHub: Go to OnceHub dashboard → Settings → API & Webhooks → Create a new API key. Copy the API key and secret.
• In Bolt.new: Open the environment variable panel and add:
  ONCEHUB_API_KEY ONCEHUB_API_SECRET
• Create a backend route that calls the OnceHub REST API using those environment variables.
• Create a webhook handler route so ScheduleOnce can POST booking data to your app.

 

Example: Fetching Bookings from OnceHub (Node.js)

 

This is real working JavaScript using OnceHub’s REST API (public documentation). It runs fine inside a Bolt.new backend.

// Example Express route inside Bolt.new backend
// This fetches bookings from OnceHub using their REST API.

import express from "express";
import fetch from "node-fetch";

const router = express.Router();

router.get("/api/bookings", async (req, res) => {
  try {
    const response = await fetch("https://api.oncehub.com/v2/bookings", {
      method: "GET",
      headers: {
        "Content-Type": "application/json",
        "user-id": process.env.ONCEHUB_API_KEY,      // OnceHub uses these headers
        "api-key": process.env.ONCEHUB_API_SECRET    // for authentication
      }
    });

    const data = await response.json();
    res.json(data);

  } catch (err) {
    console.error("Error fetching bookings:", err);
    res.status(500).json({ error: "Failed to fetch from OnceHub" });
  }
});

export default router;

 

Example: Receiving ScheduleOnce Webhooks in Bolt.new

 

You must create a POST endpoint and paste that URL into OnceHub's webhook settings.

// This receives booking event posts from OnceHub webhooks

import express from "express";
const router = express.Router();

router.post("/webhooks/oncehub", async (req, res) => {
  // OnceHub sends JSON booking events here
  const event = req.body;

  console.log("Received OnceHub event:", event);

  // TODO: Save to DB, send Slack notifications, trigger AI actions, etc.

  res.status(200).send("OK");
});

export default router;

 

Important Notes for a Junior Developer

 

• No OAuth needed for most internal apps — API key + secret is enough.
• Never hard‑code the key; always use Bolt.new env vars.
• Webhook URLs must be public for ScheduleOnce to reach them.
• Bolt.new does not “talk to APIs automatically”; you must write the HTTP requests yourself.
• You can test everything directly in Bolt.new’s built‑in browser and logs.

 

Summary

 

The integration is simply building a Bolt.new backend that calls OnceHub’s REST API with API credentials stored in environment variables and optionally receives webhooks from OnceHub. This is the real, production‑valid way to integrate “Bolt.new + ScheduleOnce.”