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

To integrate Bolt.new AI with Google Ads, you don’t “plug Bolt into Google Ads directly.” Instead, you build a normal full‑stack integration inside a Bolt.new project: your backend calls the Google Ads API using OAuth2 credentials, Bolt.new simply hosts your code while you prototype. The key steps are: create a Google Cloud project, enable Google Ads API, configure OAuth2 (or a service account if using a manager account + offline flow), store credentials in Bolt.new environment variables, and then call the Google Ads REST endpoints or use the official Google Ads API client libraries inside your Bolt backend. There is no special magic — just standard API integration.

 

What You’re Actually Doing When You “Integrate Bolt.new with Google Ads”

 

You are doing three things:

• Creating a backend service (Node.js typically) inside Bolt.new.
• Authenticating that backend with Google Ads using OAuth2 or service account + impersonation.
• Calling Google Ads API endpoints to read or modify campaigns, ads, metrics, etc.

Bolt.new is simply the coding workspace. All real integration happens through Google’s normal API channels.

 

Step-by-Step: Setting Up Google Ads API Access

 

These steps are the real required sequence for any Google Ads integration, whether inside Bolt.new or your own environment.

• Create a Google Cloud project at console.cloud.google.com.
• Enable the Google Ads API in the project.
• Go to APIs & Services → Credentials and create an OAuth 2.0 Client ID (Web application).
• Add a redirect URI for your Bolt backend. During prototyping, this is usually:
  https://<your-bolt-id>.bolt.run/oauth/callback
• Copy the client_id and client_secret into Bolt.new environment variables.
• Obtain a developer token from Google Ads account (in Tools → API Center). Initially it's “test” mode until Google approves it.
• If managing multiple accounts, get the Login-Customer-ID for your manager account.

 

Configure Bolt.new Environment Variables

 

In Bolt.new “Environment” panel, define:

• GOOGLE_CLIENT_ID
• GOOGLE_CLIENT_SECRET
• GOOGLE_DEVELOPER_TOKEN
• GOOGLE_LOGIN_CUSTOMER\_ID (optional, for MCC accounts)

These values never go in source code — only environment variables.

 

Implement OAuth2 Flow (Bolt Backend)

 

Your backend must expose two routes:

• A “login” route that redirects the user to Google’s OAuth screen.
• A “callback” route that receives the authorization code and exchanges it for access + refresh tokens.

Here is a real Node.js example you can drop directly into a Bolt.new Express backend:

 

// auth.js

import express from "express";
import axios from "axios";
import querystring from "querystring";

const router = express.Router();

router.get("/google/start", (req, res) => {
  const redirectUri = encodeURIComponent("https://your-bolt-id.bolt.run/oauth/callback");
  const scope = encodeURIComponent("https://www.googleapis.com/auth/adwords");

  const url =
    "https://accounts.google.com/o/oauth2/v2/auth?" +
    `client_id=${process.env.GOOGLE_CLIENT_ID}` +
    `&redirect_uri=${redirectUri}` +
    `&response_type=code&access_type=offline&prompt=consent&scope=${scope}`;

  res.redirect(url);
});

router.get("/oauth/callback", async (req, res) => {
  const code = req.query.code;

  const tokenRes = await axios.post(
    "https://oauth2.googleapis.com/token",
    querystring.stringify({
      code,
      client_id: process.env.GOOGLE_CLIENT_ID,
      client_secret: process.env.GOOGLE_CLIENT_SECRET,
      redirect_uri: "https://your-bolt-id.bolt.run/oauth/callback",
      grant_type: "authorization_code"
    }),
    { headers: { "Content-Type": "application/x-www-form-urlencoded" } }
  );

  // Store tokenRes.data.refresh_token securely (database, encrypted)
  console.log("Tokens received:", tokenRes.data);

  res.send("OAuth completed.");
});

export default router;

 

Calling Google Ads API From Bolt Backend

 

You have two options: REST or the official client library. REST works well inside Bolt prototypes.

Example REST call to retrieve campaigns:

 

// googleAds.js

import axios from "axios";

export async function listCampaigns(accessToken, customerId) {
  const query = "SELECT campaign.id, campaign.name FROM campaign ORDER BY campaign.id";

  const res = await axios.post(
    `https://googleads.googleapis.com/v15/customers/${customerId}/googleAds:search`,
    { query },
    {
      headers: {
        Authorization: `Bearer ${accessToken}`,
        "developer-token": process.env.GOOGLE_DEVELOPER_TOKEN,
        "login-customer-id": process.env.GOOGLE_LOGIN_CUSTOMER_ID // required for MCC
      }
    }
  );

  return res.data;
}

 

Hardening for Production

 

• Store refresh tokens in a database, encrypted.
• Rotate OAuth credentials if leaked.
• Use a proper backend URL (domain, HTTPS) instead of the temporary Bolt.run URL.
• Serve the OAuth callback from your production backend, not the Bolt workspace.

 

Key Points to Remember

 

• Bolt.new does not integrate with Google Ads automatically — you write the integration.
• You must follow the normal Google Ads API authentication flow.
• The most important piece is obtaining OAuth refresh tokens and storing them safely.
• Once authenticated, everything is just HTTP requests or client library calls.