Bubble
Read, write and trigger workflows against a Bubble app's own Data API and Workflow API.
About
Bubble ships in the w6w first-party pack. It declares 8 actions, 2 health checks, and the host runs its code in a sandbox that never sees the credential.
- App id
io.w6w.bubble- Version
- 0.1.0
- Author
- w6w
- Licence
- MIT
- Categories
- Developer Tools · Databases
Overview
Bubble is a no-code app builder, and this app talks to the two API surfaces a Bubble application itself exposes: the Data API (direct CRUD against whichever Data Types the builder has turned on) and the Workflow API (triggering the app’s own named, server-side API Workflows).
Because every Bubble app is its own deployment with its own database schema, the shapes here stay generic — a Data Type name and a JSON object of fields, rather than fixed field lists — so this app works against any Bubble application, not one specific schema. Search, read, create, update, replace, delete and bulk-create cover the Data API’s full surface; triggering an API Workflow by name covers the Workflow API, for anything the app builder has wired up beyond plain CRUD, from sending an email to running a multi-step process.
Left out on purpose: user-level authentication (logging a specific end-user in runs through a bespoke API Workflow every app builder designs differently, with no fixed endpoint to call generically) and bulk update/delete, which Bubble’s Data API does not offer at all — only bulk create.
Build with Bubble
Three routes to the same 8 actions. The Workflow tab is generated from Bubble's own manifest and carries its real ids, so it is copy-pasteable; the Code and CLI examples are the same call for any action on any app, so every app-specific value in them is a blank you fill in.
Replace Thing
data-replace Overwrite every editable field of a thing. Fields left out are cleared or reset to their default — use Update Thing to change only some fields.
A workflow step names the app and the action, and the editor fills in the
connection when you pick one. This is the Step shape from the
workflow spec, carrying Bubble's real ids.
{
"manifestVersion": "2",
"name": "bubble-example",
"steps": [
{
"id": "data-bulk-create",
"uses": {
"app": "io.w6w.bubble",
"action": "data-bulk-create",
"connection": "conn_YOUR_CONNECTION_ID"
},
"with": {
"type": "<type>",
"records": "<records>"
}
}
]
}Here are some of the things you can do
-
Bulk Create Things
performdata-bulk-create -
Create Thing
performdata-create -
Get Thing
readdata-get -
List Things
searchdata-list -
Replace Thing
performdata-replace
+3 more actions available
Every app-specific value here is a blank you have to fill in. An
app action is reached through the connection that authenticates it, so the
address is a connection id, not the app id — and connections belong to your account,
so a public page cannot know yours. Create one for Bubble, then fill in
the three blanks: conn_YOUR_CONNECTION_ID, the action key, and the
parameters that action declares. The call itself is real — the shape is transcribed
from the studio's own snippet builder, which prints the same kind of blanks — but
nothing in it is specific to Bubble. The Workflow tab is where this app's
real ids are.
npm install @w6w/sdkyarn add @w6w/sdkpnpm add @w6w/sdkdeno add npm:@w6w/sdkimport { W6wClient, isActionRun } from "@w6w/sdk";
// Reads W6W_BASE_URL and W6W_TOKEN from the environment when omitted.
const client = new W6wClient();
const envelope = await client.run({
urn: "conn_YOUR_CONNECTION_ID",
action: "data-bulk-create",
payload: {
type: "<value>",
records: "<value>",
},
});
if (isActionRun(envelope)) console.log(envelope.value);npm install -g @w6w/cliw6w run conn_YOUR_CONNECTION_ID --action data-bulk-create --payload '{"type":"<value>","records":"<value>"}'Give an AI agent Bubble — without giving it Bubble's credentials. One MCP endpoint exposes every app, function and workflow the caller is entitled to, as tools it can discover and run. Access is granted per team while we onboard.
One tool call{
"name": "w6w_invoke",
"arguments": {
"ref": "app:io.w6w.bubble#data-bulk-create",
"input": {
"type": "<type>",
"records": "<records>"
}
}
}
Every tool names its target with a single ref. The
app: form above doesn't name a connection at all — the
host resolves which of the caller's Bubble connections to sign
with, and refuses rather than guesses when the answer is ambiguous.
What the agent gets
Credentials it can't read
The token is attached host-side, at the moment of the call. It is never a tool argument, never in the model's context, and never in a transcript — so a prompt injection has nothing to exfiltrate.
A tool surface scoped to the caller
Tools are derived per end user from what that person has actually connected and is entitled to — not one shared bot identity carrying the union of everyone's access.
A durable workflow in one call
Multi-step work runs on the workflow engine and returns a run handle the agent can poll — retries, branching and state survive the conversation that started them.
Health-aware discovery
Bubble's declared health checks are on the surface too, so an agent can tell "the vendor is down" from "your credential expired" before it burns a retry on either.
The MCP surface is part of the hosted platform. Bubble itself is MIT, and the runtime that executes it is source-available (FSL).
Health checks
Bubble declares its own checks, so its health is a property of the app rather than something the host guesses at.
Bubble platform status
status.bubble.io's Main Bubble Environment component — the shared runtime every Bubble app's Data and Workflow API depends on.
Bubble app reachable
This connection's own app, via an unauthenticated request Bubble's router must still identify the app to answer — an expired token must not make a healthy app look down.