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

You integrate Bolt.new with Todoist the same way you integrate any app with Todoist: by calling the Todoist REST API from the code you write inside the Bolt.new workspace. Bolt.new does not have a built‑in Todoist connector — you add the integration explicitly using Todoist’s official API endpoints plus your Todoist API token stored in Bolt.new environment variables. After that, your Bolt.new backend (Node/Express or similar) can create tasks, read tasks, close tasks, etc., just like any other external API integration.

 

What the integration actually is

 

You write normal backend code (usually Node.js in Bolt.new) that talks to Todoist’s real API via HTTPS. Todoist provides a REST API with endpoints like /tasks, and you authenticate using a personal API token. This token must be kept secret — in Bolt.new you place it in the environment variable panel and reference it in your code.

There is no magical AI connection. It’s just your backend calling Todoist’s API. The AI in Bolt.new helps you scaffold files, write code, debug, and test — but the integration itself is regular HTTP calls.

 

Step-by-step overview

 

• Create a new Bolt.new project (Node backend + optional frontend).
• Open the environment variables panel and add something like TODOIST_API_TOKEN.
• Write backend routes that call Todoist’s API using fetch or axios.
• Test the endpoints inside Bolt.new using the built‑in API tester or temporary UI.
• Later, deploy outside Bolt (Vercel, Render, etc.) using real environment variables.

 

Real code example: creating a Todoist task from Bolt.new

 

// backend/todoist.js

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

const router = express.Router();

// POST /api/todoist/create
router.post("/create", async (req, res) => {
  const { content } = req.body;    // text of the task
  const token = process.env.TODOIST_API_TOKEN;

  if (!token) {
    return res.status(500).json({ error: "Missing TODOIST_API_TOKEN" });
  }

  try {
    const response = await fetch("https://api.todoist.com/rest/v2/tasks", {
      method: "POST",
      headers: {
        "Authorization": `Bearer ${token}`,
        "Content-Type": "application/json"
      },
      body: JSON.stringify({
        content: content  // task description
      })
    });

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

  } catch (err) {
    res.status(500).json({ error: "Todoist API error", details: err.message });
  }
});

export default router;

 

This code is real and works today: you send a POST request to your own backend’s /api/todoist/create, and it creates a Todoist task via the official Todoist REST API.

 

Add the route to your server

 

// backend/server.js

import express from "express";
import todoistRoutes from "./todoist.js";

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

app.use("/api/todoist", todoistRoutes);

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

 

How to test it inside Bolt.new

 

• Run the backend in Bolt.new’s preview server.
• Open the “API Tester” panel or use a simple HTML form that POSTs to /api/todoist/create.
• Send { "content": "Buy milk" }.
• Look in your real Todoist app — the task appears instantly.

 

Auth details you must understand

 

• Todoist personal API tokens are long‑lived and tied to your user.
• You never hardcode the token in code — only environment variables.
• For production apps, Todoist also supports OAuth2 if you need users to log in with their own Todoist accounts.

 

When you deploy outside Bolt.new

 

Your integration is standard Node code, so deployment is normal: put TODOIST_API_TOKEN in the hosting provider’s environment variables and run the server. Nothing Bolt‑specific changes; the integration remains real HTTPS calls to Todoist’s API.

 

This is the complete, real, practical way to integrate Bolt.new AI with Todoist: use Todoist’s official REST API, store the API token in Bolt.new environment variables, and let Bolt's AI help you scaffold and iterate the Node code that calls those endpoints.