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

The short version: You don’t “integrate Bolt.new with LinkedIn Ads” directly. Bolt.new is just a coding workspace with an AI assistant. What you actually do is build a backend (Node/Express inside the Bolt sandbox) that talks to the real LinkedIn Marketing Developer API. To do this, you must use LinkedIn OAuth 2.0, obtain a Marketing Developer Program–approved app, generate an access token, and then call the LinkedIn Ads endpoints from your Bolt-generated server code. In other words, Bolt.new does not have any special LinkedIn connector; you integrate by calling LinkedIn’s REST endpoints with the correct OAuth tokens stored in environment variables.

 

What “Integrating Bolt.new AI with LinkedIn Ads” Actually Means

 

Inside bolt.new, you generate code that:

• Uses LinkedIn’s REST Marketing API (Campaigns, Ad Accounts, Creatives, Reporting).
• Handles OAuth 2.0 Authorization Code Flow to obtain an access token.
• Stores tokens in Bolt Environment Variables (bolt.new → Environment tab, typically named LINKEDIN_CLIENT_ID, LINKEDIN_CLIENT_SECRET, etc.).
• Makes HTTP requests using fetch or axios from your Bolt backend.

Bolt.new does not automatically authenticate against LinkedIn for you. You still need to implement the OAuth flow and call the LinkedIn Ads endpoints exactly as LinkedIn documents.

 

Step-by-step: How you build the integration correctly

 

This is the practical real-world workflow you would follow, both in bolt.new and production later:

• Create a LinkedIn Developer App at LinkedIn’s Developer Portal.
• Request Marketing Developer Program approval (required for Ads APIs — without approval your app cannot access ad accounts).
• Enable r_ads,r_ads_reporting,r_ads\_leadgen or whichever permissions you need.
• Inside bolt.new, set environment variables:
  LINKEDIN_CLIENT_ID
  LINKEDIN_CLIENT_SECRET
  LINKEDIN_REDIRECT_URI
• Implement the OAuth 2.0 Authorization Code Flow:
  • Redirect user → LinkedIn login
  • User approves permissions
  • LinkedIn sends you back a code
  • Your backend exchanges the code → access\_token
• Use the access\_token to hit LinkedIn Ads endpoints.

This flow is standard and fully supported inside bolt.new because you are just writing normal backend code.

 

Example: OAuth callback + fetching LinkedIn Ad Accounts (Node/Express)

 

This is real working code, suitable for bolt.new’s Node server template.

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

const app = express();

// Load env vars in bolt.new (set these in Environment tab)
const clientId = process.env.LINKEDIN_CLIENT_ID;
const clientSecret = process.env.LINKEDIN_CLIENT_SECRET;
const redirectUri = process.env.LINKEDIN_REDIRECT_URI;

// Step 1: Redirect user to LinkedIn auth page
app.get("/auth/linkedin", (req, res) => {
  const url =
    "https://www.linkedin.com/oauth/v2/authorization" +
    `?response_type=code&client_id=${clientId}` +
    `&redirect_uri=${encodeURIComponent(redirectUri)}` +
    "&scope=r_ads%20r_ads_reporting";

  res.redirect(url);
});

// Step 2: OAuth callback → exchange code for access token
app.get("/auth/linkedin/callback", async (req, res) => {
  const code = req.query.code;

  const tokenRes = await fetch("https://www.linkedin.com/oauth/v2/accessToken", {
    method: "POST",
    headers: {
      "Content-Type": "application/x-www-form-urlencoded"
    },
    body:
      `grant_type=authorization_code` +
      `&code=${code}` +
      `&redirect_uri=${encodeURIComponent(redirectUri)}` +
      `&client_id=${clientId}` +
      `&client_secret=${clientSecret}`
  });

  const tokenJson = await tokenRes.json();

  // Store securely in DB or session
  const accessToken = tokenJson.access_token;

  res.json({ accessToken });
});

// Example: Fetch ad accounts for the authenticated user
app.get("/linkedin/adAccounts", async (req, res) => {
  const accessToken = req.headers.authorization; // or from DB/session

  const apiRes = await fetch(
    "https://api.linkedin.com/v2/adAccountsV2?q=search",
    {
      headers: {
        Authorization: `Bearer ${accessToken}`
      }
    }
  );

  const data = await apiRes.json();
  res.json(data);
});

app.listen(3000, () => {
  console.log("LinkedIn integration server running");
});

 

Important Real Constraints You Must Know

 

• LinkedIn Ads API is locked behind Marketing Developer Program approval. You cannot skip this; without approval your tokens cannot access ad accounts or reporting.
• OAuth Tokens expire quickly, and you must handle refresh tokens if your app workflow needs long-term access.
• Bolt.new can store env vars securely, but you should never hardcode secrets in the code.
• LinkedIn enforces strict rate limits. Your integration must handle rate-limit 429 responses.
• If you only need lead data, you can subscribe to LinkedIn Lead Gen Webhooks, but you still need OAuth + permissions.

 

How You Use Bolt.new AI Effectively Here

 

Bolt helps you by scaffolding the Node backend, generating OAuth routes, producing test requests, and wiring the UI—but the actual integration is entirely through the documented LinkedIn REST API. You remain responsible for tokens, permissions, and making sure the app has Marketing Developer Program approval.

So: integration is absolutely possible, but nothing is “automatic.” You implement LinkedIn’s OAuth 2.0 + Ads API endpoints inside bolt.new exactly as you would in any project.