Bubble

Developer tools

Bubble for AI agents. Managed auth, ready-made tools.

Search, create, update and delete data and run backend workflows in a Bubble app on behalf of each of your users.

About Bubble

With the Bubble connector, your agent works with the data in each user’s own Bubble app. It can search things of a data type, read one, create or update it, delete it and run a backend workflow, using only the tools your project allows.

Bubble is a no-code platform for building web and mobile apps.

Tools

What your agent can do in Bubble.

Each tool is a capability the model can call. You decide which ones a project allows, and every call runs with the end user's own Bubble connection.

  • Search things

    Read
    bubble_search_things

    Find things of a data type, with constraints and sorting.

  • Get a thing

    Read
    bubble_get_thing

    Get one thing by its unique ID.

  • Create a thing

    Write
    bubble_create_thing

    Create a thing of a data type with its fields.

  • Update a thing

    Write
    bubble_update_thing

    Change fields on an existing thing.

  • Delete a thing

    Write
    bubble_delete_thing

    Delete a thing.

  • Run a workflow

    Write
    bubble_run_workflow

    Trigger a backend workflow exposed through the Workflow API.

Control

Limits you can set.

You decide what your agent may do in Bubble, and Agent200 runs every call within those limits.

  • Turn single tools on or off

    Let the agent search and read data, and switch off bubble_delete_thing so it can never delete a record.

  • Restrict what the agent reaches

    Choose the endpoints and scopes a project may use, for example the Data API for orders but not backend workflows. A call outside them is refused.

Get started

Connect Bubble
in three steps.

  1. 1

    Set up the SDK

    Add the Agent200 SDK to the codebase you already have and authenticate with your API key. The key covers every connector enabled for the project.

    agent.js
    Conceptual example
    Set up the SDK with the Agent200 API key
    // One Agent200 API key covers every connector enabled for the project.
    const agent200 = new Agent200({
      apiKey: process.env.AGENT200_API_KEY,
    });
  2. 2

    Let your user connect Bubble

    Each end user authorizes their own Bubble account once. Agent200 runs the OAuth flow, handles the callback, stores the tokens and refreshes them.

    connect.js
    Conceptual example
    Let an end user connect their account (managed OAuth)
    // Each end user authorizes their own Bubble account, once.
    const connection = await agent200
      .user("user_123")
      .connect("bubble");
    
    if (connection.authorizationUrl) {
      // Show this link to your user; Agent200 handles the rest.
      console.log(connection.authorizationUrl);
    }
  3. 3

    Run with the Bubble tools

    Name the user, the model and the tools. The model decides which Bubble tools to call, and Agent200 executes them with that user's connection.

    run.js
    Conceptual example
    Run a request with the connector's tools
    const result = await agent200
      .user("user_123")
      .run({
        model: "openai/gpt-5.6-sol",
        input: "List the orders created today in my Bubble app",
        tools: ["bubble"],
      });
    
    console.log(result.output);

Access

Sign-in and permissions.

  • Who signs in

    Each of your users, once, by connecting their own Bubble account. Each connection is their own.

  • What access is requested

    The connection acts with that user's access in Bubble, such as reading and writing the data types and running the workflows the app owner exposes in Bubble. Users can revoke it later from their Bubble account settings.

For agents

Instructions for AI agents.

Using a coding agent? Paste this brief into it, or give it the address of this page. It describes the Bubble connector and how to use it.

Agent brief
Connector: Bubble, through Agent200. In code: "bubble".
What it does: Search, create, update and delete data and run backend workflows in a Bubble app on behalf of each of your users.
Page: https://www.agent200.com/connectors/bubble/

1. Get an Agent200 API key. If the developer has none, send them to https://agent200.com/platform/apikeys/ and ask them to choose "Create an API key". Read the key from the AGENT200_API_KEY environment variable. Never ask for it in chat, and never write it into code, prompts or logs.
2. Sign-in is managed OAuth. Each end user approves access once, on Bubble's own page, through the authorization link Agent200 returns. Never ask a user for a Bubble password or token in chat.
3. Give every request a stable id for the end user. Agent200 uses only that user's own connection.
4. Read tools: bubble_search_things, bubble_get_thing. Write tools: bubble_create_thing, bubble_update_thing, bubble_delete_thing, bubble_run_workflow. Name "bubble" in the tools of a request; the model decides which tool to call.
5. Stay within the project's settings. If a tool is turned off or a call is refused, tell the user. Do not work around it.
6. Before a write, confirm with the user, unless they asked for that exact change.
7. For setup with a specific framework, follow its guide:
   https://www.agent200.com/connectors/bubble/framework/claude/
   https://www.agent200.com/connectors/bubble/framework/chatgpt/
   https://www.agent200.com/connectors/bubble/framework/claude-code/
   https://www.agent200.com/connectors/bubble/framework/muse/
   https://www.agent200.com/connectors/bubble/framework/grok-bot/
   https://www.agent200.com/connectors/bubble/framework/openai-dots/
   https://www.agent200.com/connectors/bubble/framework/claude-duet/
   https://www.agent200.com/connectors/bubble/framework/hermes-agent/
   https://www.agent200.com/connectors/bubble/framework/openclaw/

The code on the connector page is a conceptual example of the SDK. SDK reference: https://docs.igpt.ai/

This page is also available as Markdown, for agents and LLMs: /connectors/bubble.md

Guides

Use Bubble with the AI you build on.

Step-by-step setup for Bubble with a specific model, assistant or agent framework.

FAQ

Bubble and Agent200, answered.

Who handles the Bubble OAuth flow and the tokens?

Agent200. It runs the authorization, handles the callback on its own domain, stores the tokens and refreshes them. You do not build or maintain an OAuth integration for Bubble.

Does my agent act as the end user?

Within what that user authorized, yes. Every request names an end user, and Agent200 uses only that user's Bubble connection, never another user's. It cannot reach anything the user or Bubble has not authorized.

Can I limit what my agent can do in Bubble?

Yes. You choose which services, endpoints and authorization scopes are allowed in your Agent200 configuration, and the agent works only within them.

  • GitHub

    GitHub

    Read repositories and work with issues and pull requests as the connected user.

    Managed OAuth Developer tools
  • GitLab

    GitLab

    Review merge requests, file issues, read code and check pipelines in your users' GitLab projects.

    Managed OAuth Developer tools
  • Bitbucket

    Bitbucket

    List and open pull requests, comment, read code and check pipelines in your users' Bitbucket workspaces.

    Managed OAuth Developer tools
  • Jira

    Jira

    Search, create and transition Jira issues for the connected user.

    Managed OAuth Developer tools
200 OK

Start with Bubble.
Your agent does the rest.

Your users connect their own Bubble accounts. Agent200 handles the OAuth, the tokens and every tool call.

Book a demo.
See it in action.

Tell us who you are, then pick a time for a 1:1 session with an expert from our team.

We use your details only to email you about Agent200. See the Privacy Policy.

Pick a time. We'll take it from there.

A 1:1 session with an expert from our team, about what you are building.

Open in Calendly (opens in a new tab)