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

To integrate Bolt.new with Pipedrive, you don’t connect “Bolt” itself to Pipedrive. Instead, inside Bolt.new you build a small backend (Node.js or Python) that talks to Pipedrive’s REST API using a Pipedrive API token or OAuth. Bolt.new simply hosts your code while you develop. You’ll create API routes, store your Pipedrive API token in environment variables, and call Pipedrive endpoints such as creating deals, updating contacts, or searching leads.

 

What You Actually Do

 

You integrate Pipedrive the same way you integrate any external SaaS in Bolt.new: by calling its REST API through server‑side code. Pipedrive provides two authentication styles — an API Token for simple server-side scripts, or OAuth 2.0 if you need per-user access. Inside Bolt.new, the simplest, safest method is storing a Pipedrive API Token in environment variables and making standard HTTPS requests from your server routes.

• Bolt.new’s environment variables hold your token so it isn’t exposed in your frontend.
• Your backend route accepts data from the UI.
• Your backend then calls Pipedrive’s REST API using fetch/axios with the token.

 

Step‑By‑Step Setup (Safe + Real)

 

Below is a practical, valid pattern that works inside a Bolt.new Node.js project.

• Create a server route (API endpoint) inside Bolt.new.
• Store PIPEDRIVE_API_TOKEN and PIPEDRIVE_BASE_URL in environment variables (e.g., https://api.pipedrive.com/v1).
• Write backend code that calls a Pipedrive endpoint.
• Call that backend route from the frontend.

 

// server/pipedrive.js
// Example: Create a new Deal in Pipedrive using REST API

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

const router = express.Router();

router.post("/create-deal", async (req, res) => {
  try {
    const { title, value, currency } = req.body;

    const url = `${process.env.PIPEDRIVE_BASE_URL}/deals?api_token=${process.env.PIPEDRIVE_API_TOKEN}`;

    const response = await fetch(url, {
      method: "POST",
      headers: { "Content-Type": "application/json" },
      body: JSON.stringify({
        title,
        value,
        currency
      })
    });

    const data = await response.json();
    res.json(data);
  } catch (err) {
    console.error("Pipedrive error:", err);
    res.status(500).json({ error: "Failed to create deal" });
  }
});

export default router;

 

Frontend Call

 

This is how your Bolt.new frontend would call that backend route:

 

// Example: Button triggers creation of a Pipedrive deal

async function createDeal() {
  const response = await fetch("/api/create-deal", {
    method: "POST",
    headers: { "Content-Type": "application/json" },
    body: JSON.stringify({
      title: "New Lead from Bolt",
      value: 1500,
      currency: "USD"
    })
  });

  const result = await response.json();
  console.log(result); // Shows Pipedrive API response
}

 

Authentication Notes

 

• API Token (recommended for simple server-side integrations): Generated in Pipedrive under "Personal Preferences → API". Use it only on the server, never in frontend code.
• OAuth: Only if each user needs access to their own Pipedrive account. Requires redirect URLs and token exchange. Works in Bolt.new, but more setup.

 

Common Real‑World Pipedrive Endpoints You Can Call

 

• Create or update Deals: POST /deals
• Create or update Persons (Contacts): POST /persons
• Create Activities: POST /activities
• Search: GET /searchResults

All follow the same pattern: construct the URL, pass your API token, send JSON.

 

Data Safety & Deployment

 

• Keep API tokens inside Bolt.new environment variables.
• Never expose tokens in the browser console or client code.
• When moving outside Bolt.new, move environment variables to your real hosting provider (Vercel, AWS, etc.). Nothing about the integration changes.

 

This is the correct, real, production‑safe way to integrate Bolt.new AI with Pipedrive: use your backend inside Bolt.new to call the Pipedrive REST API with proper authentication and environment variable management.