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

To integrate Bolt.new with Zoom, you don’t “connect Bolt to Zoom directly.” What you actually do is: you build code inside a Bolt.new project that talks to the official Zoom REST API using OAuth or Server‑to‑Server OAuth credentials, then you run and test that integration inside Bolt’s sandbox. Bolt is simply your development and automation workspace — the integration is just standard HTTPS API calls plus auth. The real work is: creating a Zoom app (in Zoom Marketplace), generating credentials, storing them as environment variables in Bolt.new, and writing API routes or server functions that call Zoom’s endpoints (create meetings, read users, manage recordings, handle webhooks, etc.).

 

What “Bolt.new + Zoom integration” actually means

 

In practical terms: your Bolt.new project is a full-stack app (Node/Express, Next.js, Python, etc.). That app uses Zoom’s official REST API by sending authenticated HTTPS requests. That’s the whole integration.

• You authenticate using Zoom OAuth (user-level) or Server‑to‑Server OAuth (service-level).
• You store secrets in Bolt.new’s environment variables panel.
• You call Zoom’s API endpoints using fetch or an HTTP client.
• You optionally expose endpoints that Zoom webhooks call back into (meetings.started, recordings.completed, etc.).

 

Step‑by‑step: How to integrate Zoom inside a Bolt.new project

 

This is the simplest, real, production-valid flow.

• Create a Zoom app: Go to https://marketplace.zoom.us → Develop → Build App.
• Choose Server-to-Server OAuth if you want your app to call Zoom without user login. This is the most common for internal automations.
• Copy the generated accountId, clientId, clientSecret.
• In Bolt.new, open the Environment Variables panel and add:
  ZOOM_ACCOUNT_ID, ZOOM_CLIENT_ID, ZOOM_CLIENT_SECRET.

 

Generate Zoom access tokens inside Bolt

 

Zoom’s Server‑to‑Server OAuth returns an access token via a POST request. You should never hard‑code tokens; always fetch fresh ones.

// utils/getZoomToken.js
export async function getZoomToken() {
  const tokenUrl = "https://zoom.us/oauth/token";

  const params = new URLSearchParams();
  params.append("grant_type", "account_credentials");
  params.append("account_id", process.env.ZOOM_ACCOUNT_ID);

  const basicAuth = Buffer.from(
    process.env.ZOOM_CLIENT_ID + ":" + process.env.ZOOM_CLIENT_SECRET
  ).toString("base64");

  const res = await fetch(tokenUrl, {
    method: "POST",
    headers: {
      Authorization: "Basic " + basicAuth,
      "Content-Type": "application/x-www-form-urlencoded"
    },
    body: params
  });

  const data = await res.json();
  return data.access_token;
}

 

Call Zoom APIs from Bolt

 

Here’s a real example of creating a Zoom meeting from inside a Bolt.new backend route.

// routes/createMeeting.js
import express from "express";
import { getZoomToken } from "../utils/getZoomToken.js";

const router = express.Router();

router.post("/", async (req, res) => {
  try {
    const token = await getZoomToken();

    const zoomRes = await fetch("https://api.zoom.us/v2/users/me/meetings", {
      method: "POST",
      headers: {
        Authorization: "Bearer " + token,
        "Content-Type": "application/json"
      },
      body: JSON.stringify({
        topic: "Bolt.new + Zoom Integration",
        type: 1 // instant meeting
      })
    });

    const data = await zoomRes.json();
    res.json(data);
  } catch (err) {
    res.status(500).json({ error: err.message });
  }
});

export default router;

• This code can be scaffolded and run inside Bolt.new immediately.
• The API call is real and works with actual Zoom accounts.
• Bolt.new is just executing normal Node.js runtime code.

 

Handling Zoom webhooks inside Bolt.new

 

If you want Zoom to notify your Bolt app when a meeting starts, ends, or a recording finishes, you enable Event Subscriptions in your Zoom app and point them at a route in Bolt. Example:

// routes/zoomWebhook.js
import express from "express";
const router = express.Router();

router.post("/", async (req, res) => {
  // Zoom sends JSON with event type and payload
  console.log("Webhook event:", req.body.event);

  // Always return 200 so Zoom knows you received it
  res.status(200).send();
});

export default router;

Bolt’s preview server gives you a public URL for testing webhooks. For production you’d re‑deploy to a real host.

 

Authentication choices (simple explanation)

 

• Server-to-Server OAuth: No user clicks “approve.” Your app uses credentials to get tokens. Best for automation, backend tasks, internal tools.
• OAuth (3‑legged): A user is redirected to Zoom, logs in, approves permissions. Needed for user-specific data or public apps.

Both work fully inside Bolt.new because they’re just HTTP calls.

 

What you cannot do

 

• Bolt.new cannot “magically sync” with Zoom without writing code. You must use the API.
• No direct SDK auto-binding. You call Zoom endpoints yourself (or install Zoom’s SDK manually).
• No bypassing Zoom OAuth rules — you follow their standard auth models.

 

Summary

 

Integrating Bolt.new with Zoom means building normal API calls (REST) inside a Bolt project using Zoom OAuth credentials stored as environment variables. You create a Zoom app, fetch tokens, call endpoints, optionally receive webhooks, and test everything right in Bolt. Nothing magical — just clean API integration.