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

To integrate bolt.new with Eloqua, you don’t “connect Bolt itself” to Eloqua. Instead, inside a bolt.new project you create normal backend code (usually a small Node.js or Python server) that talks to Eloqua’s REST API. Eloqua uses basic authentication with an Eloqua-specific username format plus company name, and all calls go through the Oracle Eloqua REST endpoints. In bolt.new you store these credentials in environment variables, call Eloqua’s REST endpoints from your backend, and build whatever UI or workflow you need on top. That is the entire pattern.

 

What “Integration with Eloqua” Actually Means

 

You are not integrating “bolt.new AI” directly into Eloqua. You are building a small backend inside bolt.new (Node.js is easiest) that makes authenticated REST API calls to Oracle Eloqua. Eloqua then responds with data about contacts, campaigns, emails, etc. Bolt.new is simply your development environment — your app handles the real integration.

This means your app must:

• Use Eloqua REST API endpoints.
• Authenticate using Basic Auth with your Eloqua Company Name + Username + Password.
• Store credentials as environment variables in bolt.new (never hard‑code them).
• Use normal HTTP libraries (fetch / axios).
• Optionally expose webhooks for Eloqua external calls.

 

Eloqua Authentication (Critical Part)

 

Eloqua does not use OAuth by default. It uses HTTP Basic Auth, but the username format is:

COMPANYNAME\USERNAME

So if your company is “AcmeCorp” and your username is “john.doe”, then:

• Username sent over HTTP = AcmeCorp\john.doe
• Password = your Eloqua password

You must base64‑encode this pair automatically by using Basic Auth headers.

 

Environment Variables in bolt.new

 

You set these inside the bolt.new environment controls:

• ELOQUA\_COMPANY
• ELOQUA\_USERNAME
• ELOQUA\_PASSWORD

Then construct the Basic Auth header in code.

 

Minimal Working Node.js Integration Example

 

This is real, valid, confirmed Eloqua REST API usage. You can paste this directly into bolt.new inside an Express server file.

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

const app = express();

app.get("/eloqua/contacts", async (req, res) => {
  try {
    // Create Eloqua Basic Auth header
    const authString = `${process.env.ELOQUA_COMPANY}\\${process.env.ELOQUA_USERNAME}:${process.env.ELOQUA_PASSWORD}`;
    const basicAuth = Buffer.from(authString).toString("base64");

    // Eloqua REST API endpoint for contacts
    const url = "https://api.eloqua.com/API/REST/2.0/data/contacts?count=10";

    const response = await fetch(url, {
      method: "GET",
      headers: {
        Authorization: `Basic ${basicAuth}`,
        "Content-Type": "application/json"
      }
    });

    const data = await response.json();

    res.json(data);
  } catch (error) {
    console.error("Eloqua API error:", error);
    res.status(500).json({ error: "Failed to fetch contacts" });
  }
});

app.listen(3000, () => {
  console.log("Server running on port 3000");
});

 

How This Works Inside bolt.new

 

Bolt runs this backend in a sandbox, but it has full outbound Internet access. That means the above code will actually talk to Eloqua’s live REST API. Once it works, you can:

• Expose a frontend route to display Eloqua contacts.
• Create new contacts via POST requests.
• Trigger Eloqua emails or update campaigns.
• Handle forms by receiving POST requests from Eloqua “External Call” steps.

 

Using Eloqua → Bolt Webhooks (“External Calls”)

 

Eloqua allows triggering external HTTP endpoints from workflows. In bolt.new, your Express server can expose a POST endpoint Eloqua calls:

app.post("/webhook/eloqua", express.json(), (req, res) => {
  console.log("Got webhook from Eloqua:", req.body);
  res.status(200).send("OK");
});

Then in Eloqua Campaign Canvas you create an External API Call pointing to your bolt.new endpoint URL.

Note: Bolt.new gives you a public URL for your project during “preview” mode. That URL is what you configure in Eloqua.

 

Hardening for Real Deployment (Outside bolt.new)

 

When your prototype works in bolt.new:

• Move environment variables to a real secret manager (AWS, GCP, Vercel, etc.).
• Ensure HTTPS and IP allowlists if required by your enterprise setup.
• Rotate Eloqua credentials regularly.
• Use retry logic because Eloqua occasionally throttles requests.

 

Summary (Plain English)

 

Integrating bolt.new with Eloqua simply means: inside your bolt.new workspace you create a backend that calls the Eloqua REST API using Basic Auth (company + username + password). You store those credentials as environment variables, make requests using fetch/axios, and optionally accept webhooks from Eloqua. There is no special bolt integration layer — it is standard API integration.