What has to be switched on in Bubble first?

Three things. The Data API must be enabled in the app's settings and the specific Data Type exposed before any record action works. A workflow must be marked "Expose as a public API workflow" before it can be triggered, and the app needs API access on its subscription. Bulk Create Things additionally needs Create via API permission.

What is the difference between patching and replacing a Thing?

Patch Thing By ID modifies only the fields you name and leaves the rest untouched. Replace Thing by ID overwrites all editable fields and resets any you omit back to their defaults. Lyro patches by default, because a replace silently wipes fields nobody mentioned.

When does Lyro use the POST workflow trigger instead of GET?

GET passes parameters as query strings and suits simple workflows with no body. POST is used when the workflow needs complex data or a file upload, with the parameters sent as a JSON object. Both call a workflow you already built in Bubble's editor rather than defining logic here.

How does Lyro attach a file to a record?

Create Temp File uploads the bytes to temporary storage and returns an S3 key that acts as a short-lived reference, and Upload File stores the file properly through Bubble's fileupload endpoint. The resulting reference is what gets persisted on a Thing.

Bubble MCP integration

Reads Bubble records by ID, creates them singly or in bulk, triggers your backend API workflows, and patches or deletes records that are wrong.

Connect Bubble See all integrations

15actions available

Three actions you can hand over today

Every action runs live through MCP. Nothing to build, nothing to maintain.

Get bubble API swagger JSON
Lyro retrieves the auto-generated Swagger JSON for enabled APIs. Developers see available Bubble endpoints and schemas without opening docs separately.
Upload file
Lyro uploads a file to Bubble storage instantly. Support interactions attach documents and assets without requiring manual file management.
Trigger bubble workflow via post
Lyro triggers a Bubble API workflow by name using a POST request. Conversations invoke custom processes and integrations without login.

See all 15 actions

How businesses use Bubble + Lyro

Each card is one request a support team gets, and the Bubble actions Lyro runs to close it.

Answer from a record in your Bubble app
Lyro fetches a Thing by its unique ID with all its custom and standard fields, reads the app's Swagger definition to know what is exposed, and downloads a file the record points at.
Get Thing By IDGet Bubble API Swagger JSONDownload File
Create a record from the conversation
Lyro adds a single Thing from a complete JSON payload, inserts many at once when a whole batch arrives, and uploads any file that has to be stored alongside them.
Create ThingBulk Create ThingsUpload File
Trigger a backend workflow you already built
Lyro calls an exposed API workflow by name, passing simple parameters as a query string or complex data as a JSON body, and stages a temporary file when the workflow needs one.
Trigger Bubble Workflow via POSTTrigger Bubble Workflow via GETCreate Temp File
Correct or remove a record
Lyro patches just the fields that changed, replaces the whole record when a full overwrite is intended, and deletes a Thing that should not exist any more.
Patch Thing By IDReplace Thing By IDDelete Thing By ID

How it works

Get started in 3 steps

Connect once, then just ask. There is no workflow builder to learn and nothing to maintain — Lyro reads the Bubble actions it has and picks the ones a request needs.

01
Connect Bubble
Authorize the Bubble account your team already uses — one consent screen, no API keys, no mapping tables. Lyro can only do what you granted that account, and you can disconnect it at any time.
02
Tell your agent what you need
Describe the job the way you would hand it to a teammate. Lyro maps it to the Bubble actions that close it and chains as many as the request needs.
03
Watch it work
The agent runs the actions inside the conversation the customer is already in, so nobody copies data between tabs and your team can take over at any point.
Get started free

Bubble · Lyro

Everything else about Bubble

Setup, permissions, and the limits of what Lyro can do inside Bubble.

Three things. The Data API must be enabled in the app's settings and the specific Data Type exposed before any record action works. A workflow must be marked "Expose as a public API workflow" before it can be triggered, and the app needs API access on its subscription. Bulk Create Things additionally needs Create via API permission.

Every action available in Bubble

All 15 actions your agent can call on Bubble, straight from the live MCP connection.

Bulk create things
Bulk create multiple Things in Bubble via newline-separated JSON.
Create thing
Create a new Thing.
Delete thing by ID
Delete a Bubble Thing by its unique ID.
Get thing by ID
Retrieves a single Thing (record) from a Bubble Data Type by its unique ID.
Patch thing by ID
Modify selected fields on a Thing by its unique ID.
Replace thing by ID
Replace all editable fields on a Thing by its Unique ID.
Download file
Download a file given its URL.
Create temp file
Upload bytes as a temporary file to Cloudflare R2 and return an S3 key.
Upload file
Upload a file to Bubble storage.
Get bubble API swagger JSON
Retrieve the auto-generated Swagger JSON for enabled APIs.
Get oauth access token
Exchange an authorization code or refresh token for an OAuth2 access token.
Oauth authorize
Initiate OAuth2 authorization flow for Bubble.
Bubble oauth register app
Validate/initialize OAuth application credentials with Bubble.
Trigger bubble workflow via get
Trigger a Bubble API workflow using an HTTP GET request.
Trigger bubble workflow via post
Triggers a Bubble API workflow by name using a POST request.