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

The direct answer: You integrate Bolt.new with Mailchimp the same way you would in any normal full‑stack environment — by calling Mailchimp’s official REST API using an API key or OAuth token, storing the secret inside Bolt.new environment variables, and then writing backend routes (Node.js/Express in Bolt) that make authenticated requests to Mailchimp endpoints such as /lists/{list\_id}/members. Bolt.new does not provide a built‑in Mailchimp connector. You build the integration yourself using HTTP requests, Mailchimp’s documented API, and environment variables for secrets.

 

What “Bolt.new integration with Mailchimp” actually means

 

Inside Bolt.new you build a small full‑stack app. The backend can call external APIs like Mailchimp. Bolt does not have direct plugins; you do it the same way you would anywhere else: configure API keys → write fetch/axios requests → test in the Bolt preview server → ship.

Mailchimp exposes a REST API. You authenticate using:

• API Key + Server Prefix (simpler; good for prototyping)
• OAuth (recommended for production where users connect their own Mailchimp accounts)

In Bolt.new, you store the Mailchimp API key in Environment Variables so it is not exposed to the frontend.

 

Step-by-step: Build this in Bolt.new

 

This example shows the cleanest way to integrate: a Node.js backend route inside Bolt that subscribes an email to a Mailchimp audience list.

• Create a backend route in Bolt (for example in /server/index.js).
• Store MAILCHIMP_API_KEY and MAILCHIMP_SERVER_PREFIX (looks like us21) in Bolt’s environment variables.
• Use fetch to call Mailchimp’s API from the backend where secrets are safe.

 

// server/index.js
import express from "express";
import fetch from "node-fetch"; // only if node version requires. Bolt supports it.

const app = express();
app.use(express.json());

app.post("/api/subscribe", async (req, res) => {
  const { email } = req.body;

  const apiKey = process.env.MAILCHIMP_API_KEY;        // stored in Bolt env vars
  const serverPrefix = process.env.MAILCHIMP_SERVER;   // e.g. "us21"
  const listId = process.env.MAILCHIMP_LIST_ID;        // your audience ID

  const url = `https://${serverPrefix}.api.mailchimp.com/3.0/lists/${listId}/members`;

  const result = await fetch(url, {
    method: "POST",
    headers: {
      "Authorization": `apikey ${apiKey}`,
      "Content-Type": "application/json"
    },
    body: JSON.stringify({
      email_address: email,
      status: "subscribed"
    })
  });

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

export default app;

 

Frontend (Bolt) calling your backend route

 

This happens in your React/Next.js or plain JS code. The frontend never touches secrets — it only calls your backend.

// Example React component in Bolt
async function subscribe(email) {
  const response = await fetch("/api/subscribe", {
    method: "POST",
    headers: { "Content-Type": "application/json" },
    body: JSON.stringify({ email })
  });

  return await response.json();
}

 

How authentication works

 

Mailchimp uses a very simple pattern:

• Your API key looks like: 123abc-us21
• The last part (us21) is your server prefix
• All API URLs start with: https://us21.api.mailchimp.com/3.0/
• Authorization header is literal: Authorization: apikey YOUR_API_KEY

Bolt.new does not change that flow. You follow it exactly.

 

If you need OAuth (users connecting their own Mailchimp)

 

Mailchimp uses a standard OAuth 2 flow. In Bolt.new:

• Implement an OAuth redirect route
• Exchange Mailchimp’s "code" for an access token
• Store access tokens server-side (Bolt runtime supports this with in-memory/demo only; real hosting would use DB)

This is more advanced but fully possible — identical to a normal Node/Express OAuth integration.

 

Key limits and warnings

 

• Never put API keys in frontend JS; always use backend routes.
• Mailchimp free-tier limits API calls; avoid rapid polling.
• Mailchimp list IDs are not secret; API keys are.
• Bolt previews reset state on restart; do not depend on persistent local storage for tokens.

 

Summary

 

You integrate Bolt.new with Mailchimp by calling Mailchimp’s REST API from Bolt’s backend using a Mailchimp API key stored in environment variables. Bolt acts like any normal Node.js server — you build routes, make authenticated fetch requests, and expose simple endpoints your frontend calls. Everything uses standard REST and Mailchimp’s documented authentication, with no proprietary Bolt hooks or plugins.