- Category: app builder
- Auth: API_KEY
- Composio-managed OAuth available? N/A
- Tools: 15
- Triggers: 0
- Slug:
BUBBLE - Version: 20261101_00
Tools
Bulk Create Things
Bulk Create Things
Slug:
BUBBLE_DATA_BULK_CREATE_THINGSBulk 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.Input Parameters
Full URL override for the bulk endpoint. If provided, the request will be sent to this URL as-is, ignoring ‘typename’, ‘custom_domain’, and ‘subdomain’.
Output
Create Thing
Create Thing
Slug:
BUBBLE_DATA_CREATE_THINGTool to create a new Thing. Use when providing a complete JSON payload to add a new record.Input Parameters
JSON object mapping field names to values for the new Thing. Required fields must be provided (e.g., ‘email’ for the User type).
Full URL override for the create endpoint. If provided, the request will be sent to this URL as-is, ignoring ‘typename’, ‘custom_domain’, and ‘subdomain’.
Output
Delete Thing By ID
Delete Thing By ID
Slug:
BUBBLE_DATA_DELETE_THING_BY_IDTool to delete a Bubble Thing by its unique ID. Use when you need to remove a specific record via the Bubble Data API.Input Parameters
Full URL override for the delete endpoint. If provided, the request will be sent to this URL as-is, ignoring ‘typename’, ‘custom_domain’, and ‘subdomain’.
Output
Get Thing By ID
Get Thing By ID
Slug:
BUBBLE_DATA_GET_THING_BY_IDRetrieve 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.Input Parameters
The unique identifier of the Thing to retrieve. This is the value returned in the ‘_id’ or ‘id’ field when the Thing was created. Bubble typically uses format like ‘1234567890123x123456789012345678’.
The Bubble Data Type name (case-sensitive). This is the custom data type defined in your Bubble app (e.g., ‘user’, ‘order’, ‘product’). Check your Bubble app’s Data tab for available types.
Full URL override for the GET endpoint. If provided, the request will be sent to this URL as-is, ignoring ‘typename’, ‘custom_domain’, and ‘subdomain’.
Output
Patch Thing By ID
Patch Thing By ID
Slug:
BUBBLE_DATA_PATCH_THING_BY_IDTool to modify selected fields on a Thing by its unique ID. Use after confirming the Thing exists.Input Parameters
JSON object of fields to update. Each key is an existing field name; each value must match the field’s type.
Full URL override for the patch endpoint. If provided, the request will be sent to this URL as-is, ignoring ‘typename’, ‘custom_domain’, and ‘subdomain’.
Output
Replace Thing by ID
Replace Thing by ID
Slug:
BUBBLE_DATA_PUT_REPLACE_THING_BY_IDReplace all editable fields on a Bubble Thing by its unique ID. Omitted fields are left empty or reset to their configured defaults.Input Parameters
Mapping of each editable field name to its new value. Omitted editable fields will be reset to their default values.
Full URL override for the PUT endpoint. If provided, the request will be sent to this URL as-is, ignoring ‘typename’, ‘custom_domain’, and ‘subdomain’.
Output
Download File
Download File
Create Temp File
Create Temp File
Upload File
Upload File
Slug:
BUBBLE_FILE_UPLOADUpload 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.Input Parameters
Full URL override for the upload endpoint (e.g., https://httpbin.org/post)
Output
Get Bubble API Swagger JSON
Get Bubble API Swagger JSON
Get OAuth Access Token
Get OAuth Access Token
Slug:
BUBBLE_O_AUTH_ACCESS_TOKENTool 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.Input Parameters
Must be ‘refresh_code’ when exchanging a refresh token for a new access token. Note: Bubble uses ‘refresh_code’ instead of the standard OAuth 2.0 ‘refresh_token’ value.
Full URL to the token endpoint. If provided, takes precedence over domain/subdomain/metadata-derived URL.
Output
Bubble OAuth Register App
Bubble OAuth Register App
Trigger Bubble Workflow via GET
Trigger Bubble Workflow via GET
Slug:
BUBBLE_WORKFLOW_TRIGGER_GETTrigger 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.Input Parameters
Bubble deployment branch to target. Use ‘live’ for production workflows or ‘version-test’ for development/testing workflows.
Query string parameters to pass to the workflow, matching the workflow’s defined inputs. Each key should match a parameter name configured in your Bubble workflow. Values can be strings, numbers, booleans, or simple objects. Example: {‘user_id’: ‘123’, ‘send_email’: true, ‘priority’: 1}
Name of the API workflow to trigger (as defined in Bubble’s workflow editor). This is the exact name you gave the workflow, which becomes part of the endpoint URL. Example: if your workflow is named ‘send_email’, use ‘send_email’.
Output
Trigger Bubble Workflow via POST
Trigger Bubble Workflow via POST
Slug:
BUBBLE_WORKFLOW_TRIGGER_POSTTriggers 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.Input Parameters
Deployment branch to target. Use ‘live’ for production environment or ‘version-test’ for development/testing environment.
JSON body parameters to pass to the workflow, matching the workflow’s configured input parameters. Use ISO 8601 format for dates (e.g., ‘2024-01-15T10:30:00Z’), and unique IDs (strings) for Bubble data type references.
URL-friendly name of the Bubble API workflow to trigger. This is the name you configured in your Bubble app’s API Workflows section, converted to lowercase with hyphens instead of spaces (e.g., ‘send-email’, ‘process-payment’).