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

The direct answer is: you integrate Bolt.new with Freshsales the same way you integrate any normal backend with Freshsales — by calling Freshsales’ public REST APIs from server-side code inside your Bolt project, authenticated using a Freshsales API Key or OAuth. Bolt.new does not provide a special connector; you implement the integration using HTTP requests, environment variables, and typical API patterns.

 

What “integrating Bolt.new with Freshsales” actually means

 

Inside Bolt.new, you create a server route or backend function that talks to Freshsales’ REST API. Freshsales exposes endpoints to create leads, update contacts, log activities, etc. You call these endpoints using fetch/axios with the correct auth header ("Authorization: Token token=YOUR_API_KEY"). Bolt does not manage auth for you — you store the Freshsales API key in Bolt environment variables.

 

How Freshsales authentication works

 

• Freshsales gives you an API Key inside your Freshsales admin settings.
• API requests require an Authorization header with that key.
• The URL is always https://YOURDOMAIN.freshsales.io/api/...

In Bolt.new you place the API key in the environment variable panel (e.g., FRESH_API_KEY).

 

Minimal working backend integration inside Bolt.new

 

The example below shows a Bolt backend route that creates a lead in Freshsales. This is real Freshsales API syntax.

// bolt-api/routes/createFreshsalesLead.js

import { Router } from "express";
import fetch from "node-fetch";

const router = Router();

router.post("/", async (req, res) => {
  try {
    const { email, first_name, last_name } = req.body;

    const response = await fetch(
      `https://${process.env.FRESHSALES_DOMAIN}.freshsales.io/api/leads`,
      {
        method: "POST",
        headers: {
          "Authorization": `Token token=${process.env.FRESH_API_KEY}`,
          "Content-Type": "application/json",
        },
        body: JSON.stringify({
          lead: {
            email,
            first_name,
            last_name
          }
        })
      }
    );

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

  } catch (err) {
    res.status(500).json({ error: err.message });
  }
});

export default router;

 

This is exactly how you call Freshsales from any backend — Bolt is just hosting this backend for you during development.

 

Front-end example in Bolt.new

 

Your UI can simply call the above backend route:

// example front-end call inside Bolt.new

async function addLead() {
  const res = await fetch("/api/createFreshsalesLead", {
    method: "POST",
    headers: {
      "Content-Type": "application/json",
    },
    body: JSON.stringify({
      email: "[email protected]",
      first_name: "John",
      last_name: "Doe"
    })
  });

  const json = await res.json();
  console.log(json);
}

 

Where to store secrets in Bolt.new

 

• Open Bolt environment settings.
• Create FRESH_API_KEY and FRESHSALES\_DOMAIN.
• These variables are available server-side only (safe).

The Freshsales API key must never be placed in the front-end; always route through the backend as shown.

 

How to test inside Bolt.new

 

• Use Bolt’s built-in server logs panel to confirm API calls.
• Check Freshsales UI to verify leads or contacts appear.
• Print the response JSON to confirm the API schema matches your payload.

 

Hardening for production (outside Bolt)

 

• Move the code into your real backend (Node/Express, Next.js API routes, etc.).
• Use environment variables in your hosting platform.
• Configure API rate limits (Freshsales limits vary by plan).
• Add retry logic if you’ll be syncing large data sets.

This is the exact same integration you tested in Bolt, just running in your actual deployment environment.