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

The short version is: there is no direct “Bolt.new ⇄ Flock” built‑in integration. To integrate them, you treat Flock like any external service that exposes an API. In practice, inside a Bolt.new project you call the Flock Webhooks API or the Flock Chat API (send messages, trigger bots, receive events) using normal HTTP requests, and you store your Flock tokens as environment variables. Bolt provides the workspace; the actual integration is just API calls you write yourself.

 

What Flock Actually Offers

 

Flock supports two real and documented integration mechanisms:

• Incoming Webhooks: You get a unique URL from Flock; you POST messages to it.
• Flock API (Chat/Users/Channels): REST endpoints you call using a Flock App Token or User Token.

There is no Flock SDK specifically for Bolt; you just use fetch/axios like any HTTP API.

 

How to integrate Flock inside a Bolt.new project

 

You follow a pattern that works for all external services:

• Step 1: Collect Flock credentials • Create a Flock App at: https://dev.flock.com • Enable “Bot” if you want your app to post to channels • Copy the Bot Token or User Token • Optional: create a Webhook URL in Flock for simple message posting
• Step 2: Add tokens to Bolt.new environment variables • In Bolt.new: project settings → Environment Variables • Add something like FLOCK\_TOKEN="xoxb-..." • Never hardcode secrets in code.
• Step 3: In your Bolt project, call Flock’s API via fetch() • Bolt's runtime allows HTTP requests normally • So you write backend routes that POST messages or fetch channel info.
• Step 4: If you need two‑way integration, expose a Bolt HTTP endpoint • In Bolt.new you can create an API route that receives POST requests • Register that URL as a Flock “Event Callback” or “Outgoing Webhook” • Flock will then push messages/events to your Bolt endpoint.

 

Example: Sending a Message from Bolt.new to Flock via Webhook

 

// /api/send-to-flock.js
export default async function handler(req, res) {
  try {
    const { text } = req.body

    // Your Flock incoming webhook URL
    const webhookUrl = process.env.FLOCK_WEBHOOK_URL

    const response = await fetch(webhookUrl, {
      method: "POST",
      headers: { "Content-Type": "application/json" },
      body: JSON.stringify({
        text: text  // Message you want to appear in a Flock channel
      })
    })

    const data = await response.text()
    res.status(200).json({ ok: true, flockResponse: data })
  } catch (err) {
    res.status(500).json({ ok: false, error: err.message })
  }
}

This works immediately in Bolt: you call `/api/send-to-flock` from your frontend, Bolt executes it server-side, and Flock receives the message.

 

Example: Using the Flock Chat API (with token auth)

 

// /api/flock-chat.js
export default async function handler(req, res) {
  try {
    const { text, channel } = req.body

    const token = process.env.FLOCK_TOKEN

    const response = await fetch("https://api.flock.com/chat.sendMessage", {
      method: "POST",
      headers: { "Content-Type": "application/json" },
      body: JSON.stringify({
        to: channel,     // Flock channel or user ID
        text,            // Message content
        token            // Bot or user token
      })
    })

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

This lets you fully control your Flock bot from within Bolt.new.

 

Receiving Events From Flock (two‑way integration)

 

You can also receive messages/events from Flock, for example when someone mentions your bot. In Flock developer console, set an “Event Callback URL” pointing to a Bolt route.

// /api/flock-events.js
export default async function handler(req, res) {
  // Flock will POST JSON here
  const event = req.body

  // You can log, react, or trigger Bolt workflows
  console.log("Incoming Flock event:", event)

  res.status(200).json({ ok: true })
}

Now your Bolt app participates in real-time workflows with Flock.

 

Hardening it outside Bolt.new

 

When you later move this out of Bolt into production, the integration stays identical: you deploy to your server, keep your tokens in environment variables, and continue calling Flock’s API over HTTPS. Bolt isn’t doing the integration — you are — using standard REST patterns.