Bubble OAuth Register App
Send an OAuth authorization request using the supplied client ID and redirect URI, and return the supplied credentials, HTTP status and any redirect location.
Bubble is a visual programming language and a PaaS developed by Bubble Group.
Send an OAuth authorization request using the supplied client ID and redirect URI, and return the supplied credentials, HTTP status and any redirect location.
Bulk create up to 1,000 Bubble Things via newline-separated JSON, with Create via API permission. Creation can partially succeed, so check the per-item results.
Upload base64-encoded or plain-text content as a temporary file and return its storage key, name, and MIME type.
Tool to create a new Thing. Use when providing a complete JSON payload to add a new record.
Tool to delete a Bubble Thing by its unique ID. Use when you need to remove a specific record via the Bubble Data API.
Tool to download a file given its URL. Use when you need to retrieve file content for subsequent upload tests.
Tool to retrieve the auto-generated Swagger JSON for enabled APIs. Use after enabling the Swagger file in your Bubble app's API settings.
Tool to exchange an authorization code or refresh token for an OAuth2 access token. Use after obtaining an authorization code or when refreshing an expired token.
Retrieve a Bubble Thing by data type and unique ID. Returned fields depend on the app's privacy rules and the client's access; the Data API must be enabled and the data type exposed.
Initiate OAuth authorization with a GET request and return the redirect location, or the request URL if no redirect is supplied. An authorization endpoint URL can be supplied explicitly.
Tool to modify selected fields on a Thing by its unique ID. Use after confirming the Thing exists.
Replace all editable fields on a Bubble Thing by its unique ID. Omitted fields are left empty or reset to their configured defaults.
Trigger a Bubble API workflow using an HTTP GET request. API workflows are server-side workflows in Bubble that can be triggered externally. Use GET for simple workflows that don't require a request body (parameters passed as query strings). For workflows requiring complex data or file uploads, use the POST version instead. Before using: The workflow must be created in Bubble's workflow editor and marked as "Expose as a public API workflow". The Bubble app must have API access enabled in its subscription.
Triggers a Bubble API workflow by name using a POST request. Use this tool to execute backend workflows in your Bubble application. The workflow must be configured in your Bubble app's API Workflows section with "Expose as public API workflow" enabled. Pass any required parameters as a JSON object in the parameters field.
Upload a file to a Bubble app's storage. The upload can target the connected app, a custom domain or subdomain, or a specified upload URL, and can include additional form fields.
The Bubble integration connects your Dench AI CRM directly to Bubble, so agents can read and act on your Bubble data as part of everyday work — answering questions in chat, keeping your CRM in sync, and running automations without anyone copying data between tools.
15 actions are available for agents to invoke on your behalf. Every call runs through Bubble's own authorization, scoped to the account you connect.
Sign in to your Dench workspace and open Integrations.
Find Bubble and click Connect — you'll authorize access through Bubble's own sign-in flow. No API keys or code required.
Ask an agent to use Bubble in chat, or call it from an automation.
Manage or disconnect the connection any time from workspace settings.
The Dench Bubble integration connects your AI CRM to Bubble, so AI agents can work with your Bubble data as part of chats, automations, and CRM workflows. You connect your account once, and every agent in your workspace can use it — governed by your workspace permissions.
The Bubble integration currently exposes 15 actions, including Bubble OAuth Register App, Bulk Create Things, Create Temp File, Create Thing, Delete Thing By ID, and Download File. Agents invoke them on your behalf from chat or from automations.
No. You connect Bubble from your Dench workspace using Bubble's own sign-in and authorization flow — no API keys to copy, no glue code to maintain.
Connections are authorized through Bubble's own authentication flow, and Dench stores only the authorization needed to act on your behalf. You can review and disconnect the Bubble connection from your workspace settings at any time.