Bubble
for LuumenAI
Read Bubble app data and API schemas, then change records as approved steps.
Connect the Bubble app your team runs on and Luumen can read it for context: pull a single Thing by ID, inspect the auto-generated Swagger for the enabled Data and Workflow APIs, download a stored file. Changes to records — creating, patching, replacing, deleting Things — are previewed and approved before they run. Authentication is by API key.
The Bubble toolbox
15 tools: 5 read, 10 write. Reads answer instantly. Writes require approval by default. Everything is logged.
- ReadGet Thing By IDRetrieves a single Thing (record) from a Bubble Data Type by its unique ID.
- ReadDownload FileDownload a file given its URL.
- ReadGet Bubble API Swagger JSONRetrieve the auto-generated Swagger JSON for enabled APIs.
- ReadOAuth AuthorizeInitiate OAuth2 authorization flow for Bubble.
- ReadBubble OAuth Register AppValidate/initialize OAuth application credentials with Bubble.
- WriteBulk Create ThingsBulk create multiple Things in Bubble via newline-separated JSON. Approval by default
- WriteCreate ThingCreate a new Thing. Approval by default
- WriteDelete Thing By IDDelete a Bubble Thing by its unique ID. Approval by default
- WritePatch Thing By IDModify selected fields on a Thing by its unique ID. Approval by default
- WriteReplace Thing by IDReplace all editable fields on a Thing by its Unique ID. Approval by default
- WriteCreate Temp FileUpload bytes as a temporary file to Cloudflare R2 and return an S3 key. Approval by default
- WriteUpload FileUpload a file to Bubble storage. Approval by default
- WriteGet OAuth Access TokenExchange an authorization code or refresh token for an OAuth2 access token. Approval by default
- WriteTrigger Bubble Workflow via GETTrigger a Bubble API workflow using an HTTP GET request. Approval by default
- WriteTrigger Bubble Workflow via POSTTriggers a Bubble API workflow by name using a POST request. Approval by default
One prompt, start to finish
What a governed Bubble run looks like inside Luumen.
Questions
Authorize once with API token. Luumen lists the scopes each action needs before you approve the connection, and credentials never appear in the chat.
Read actions answer immediately. Anything that writes — bulk create things, create thing, delete thing by id, patch thing by id, and more — is shown as a plan and requires approval by default, including the 1 action classified as destructive. Administrators configure that per tool, so you decide exactly which actions can ever run unattended.
You decide. Actions are granted per agent, skill, and team, and per environment — production is not staging. Read access can be broad while writes stay narrow.
Every call to Bubble — read or write, approved or declined — is recorded with the actor, the input, and the result, and can be linked to the ticket or change record.
Often connected alongside
All integrations
GitHubRepos, actions, and runbook code as context and as actions.
GitLabMerge requests and pipelines proposed, triggered, and rolled back.
BitbucketRead commits, diffs, and branches in Bitbucket, then open the fix as a held write.
Azure DevOpsAzure DevOps repos and pipelines as context — and as approved actions.Put Bubble to work with Luumen
Connect in minutes. Every action scoped, approved, and audited from day one.