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

To integrate Bolt.new with Teamwork, you don’t connect “Bolt” itself — you make your Bolt.new project call the real Teamwork REST API using a standard API Key (or OAuth if you need user‑level actions). In practice inside Bolt.new you create a backend route, load the Teamwork API key into environment variables, and then perform authenticated HTTPS requests to Teamwork (for example, creating tasks, reading projects, posting comments). That’s the entire integration pattern: Teamwork is just an external REST service, and Bolt.new is your coding workspace where you wire that API into your full‑stack app.

 

What Teamwork Actually Provides

 

Teamwork exposes a real, documented REST API that supports operations like tasks, projects, time logs, comments, webhooks, and users. Authentication is done using Basic Auth with your API key as the username and an empty password.

• API docs: https://developer.teamwork.com/
• Your API key is found in Teamwork: Profile → API & Mobile
• Base URL example: https://yourcompany.teamwork.com

 

How Bolt.new Fits Into This

 

Bolt.new provides a server runtime where you can write Node.js/Express (or similar) backend routes. There is no built‑in “Teamwork integration button” — you wire it manually like any other external API. The pattern is:

• Store secrets in Bolt environment variables
• Write backend route → perform fetch() → return JSON to your frontend
• Optional: build UI to trigger actions (e.g., create a Teamwork task)

 

Step‑By‑Step: Wire Teamwork API in Bolt.new

 

Below is the simplest, real, working integration pattern: a backend route that creates a task inside a Teamwork project.

 

1. Set environment variables in Bolt

 

• TEAMWORK_API_KEY = your actual API key
• TEAMWORK_BASE_URL = something like https://yourcompany.teamwork.com

 

2. Create a backend route in Bolt.new

 

// routes/teamwork.js
import express from "express";
import fetch from "node-fetch";

const router = express.Router();

router.post("/create-task", async (req, res) => {
  try {
    const { content, projectId } = req.body;

    // Teamwork requires Basic Auth: API_KEY as username, empty password
    const authHeader = "Basic " + Buffer.from(process.env.TEAMWORK_API_KEY + ":").toString("base64");

    const response = await fetch(
      `${process.env.TEAMWORK_BASE_URL}/projects/${projectId}/tasks.json`,
      {
        method: "POST",
        headers: {
          "Authorization": authHeader,
          "Content-Type": "application/json"
        },
        body: JSON.stringify({
          todo-item: { // Teamwork requires this exact structure
            content: content
          }
        })
      }
    );

    const data = await response.json();
    res.json(data);

  } catch (err) {
    res.status(500).json({ error: err.message });
  }
});

export default router;

 

3. Register the route in your main server file

 

// server.js
import express from "express";
import teamworkRoute from "./routes/teamwork.js";

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

app.use("/teamwork", teamworkRoute); // enables /teamwork/create-task

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

 

4. Call the backend from your Bolt frontend

 

// Example React handler in Bolt.new
async function createTask() {
  const result = await fetch("/teamwork/create-task", {
    method: "POST",
    headers: { "Content-Type": "application/json" },
    body: JSON.stringify({
      content: "Example task created from Bolt",
      projectId: "12345" // your real project ID
    })
  });

  const data = await result.json();
  console.log("Teamwork response:", data);
}

 

Important Notes

 

• You must use HTTPS because Teamwork rejects unsecured requests.
• Task payloads must use Teamwork’s exact field names (e.g., todo-item).
• If you need user-specific permissions, switch from API-key auth to OAuth 2 (Teamwork supports this).
• You can add webhooks in Teamwork to notify your Bolt backend about task changes.

 

This is the clean, real-world pattern: environment variables → backend route → fetch to Teamwork → return → UI. This works the same way in Bolt for prototyping and production servers outside Bolt.