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

The short answer is: you don’t “integrate Bolt.new itself” with Intercom. Bolt.new is just your AI-assisted development workspace. What you actually do is build code inside Bolt.new that talks to Intercom through their official REST API or their official Webhooks.
In practice, this means you create a small backend service inside Bolt (Node.js usually), load your Intercom credentials as environment variables, and make authenticated HTTPS requests to Intercom’s API. That’s the whole integration.

 

How the integration actually works (high‑level)

 

You use Bolt.new to generate your backend code, UI, tests, and wiring. But the real integration happens through Intercom’s REST API.

• You get Intercom credentials (usually a Personal Access Token or a Service Account).
• You store them as environment variables inside Bolt.new’s project environment.
• You write a backend route in Bolt (Node/Express or any stack) that calls Intercom’s REST API using HTTPS.
• You optionally expose your own webhook endpoints and register them inside Intercom for incoming events (new conversations, messages, user activity).

That’s it. Nothing magical — just normal API-based integration inside Bolt.

 

Step-by-step instructions

 

This walks a junior dev through what to actually do inside bolt.new.

• Inside Intercom, go to Settings → Developers → Your Apps and create an internal app.
• Copy your Access Token (string starting with “Bearer …”).
• Open your Bolt.new project and create an environment variable, for example INTERCOM\_TOKEN.
• Scaffold a simple backend route that uses this token to call Intercom.

 

Minimal working backend example (Node/Express)

 

This is a real, minimal, fully-valid sample that works with Intercom’s REST API for listing users.

// server.js
import express from "express"
import fetch from "node-fetch"  // For bolt.new Node projects, this works as expected

const app = express()

app.get("/intercom/users", async (req, res) => {
  try {
    const response = await fetch("https://api.intercom.io/users", {
      method: "GET",
      headers: {
        "Authorization": `Bearer ${process.env.INTERCOM_TOKEN}`, // Your env var
        "Accept": "application/json"
      }
    })

    const data = await response.json()
    res.json(data)
  } catch (err) {
    console.error(err)
    res.status(500).json({ error: "Failed to call Intercom API" })
  }
})

app.listen(3000, () => console.log("Server running on port 3000"))

 

Inside Bolt, you can hit /intercom/users to verify the integration works.

 

If you want Intercom → your app (webhooks)

 

Intercom can push events to your Bolt-created backend via webhooks.

• Create a route like /webhooks/intercom.
• Expose it externally (Bolt has built-in preview URLs).
• Register this URL inside Intercom under App Webhooks.
• You’ll start receiving JSON events like new conversations, messages, etc.

 

Example webhook receiver

 

// webhook.js
import express from "express"
const router = express.Router()

router.post("/webhooks/intercom", express.json(), (req, res) => {
  // Intercom sends event in req.body
  console.log("Intercom webhook event:", req.body)

  res.status(200).send("ok")
})

export default router

 

Security notes

 

• Never hardcode Intercom tokens in Bolt code; always use environment variables.
• Use HTTPS-only (Bolt’s preview URLs already do this).
• Webhook endpoints should validate Intercom signatures if you move to production.

 

How to think about this when deploying outside Bolt

 

Bolt gives you the scaffold and interactive testing, but the integration pattern doesn’t change elsewhere. In production, you will:

• Deploy the same backend code to your real environment (Vercel, Railway, Render, AWS…)
• Move environment variables to your production secrets store
• Update Intercom webhook URLs to your real domain

 

This is the valid and complete way to integrate Bolt.new-built apps with Intercom — simply by writing normal API + webhook code inside Bolt, using Intercom’s official auth tokens.