Overview
This node enables interaction with the Bubble Data API, specifically supporting operations on Bubble data objects with optional proxy usage for API requests. It is useful when you want to programmatically create, retrieve, update, or delete Bubble database objects within an n8n workflow, especially in environments where direct API calls must be routed through a proxy server.
For the Delete Object operation, the node deletes a specified object of a given data type by its ID. This is beneficial for workflows that need to automate cleanup or removal of records from a Bubble app's database.
Example use case: Automatically deleting user records from a Bubble app when they unsubscribe from a service, ensuring data consistency without manual intervention.
Properties
| Name | Meaning |
|---|---|
| Use Proxy | Whether to route API requests through a proxy server (true/false). |
| Proxy URL | The URL of the proxy server to use if "Use Proxy" is enabled (e.g., http://proxy.example.com:8080). Required if proxy is used. |
| Type Name | The name of the Bubble data type (object type) to operate on (e.g., "user", "order"). |
| Object ID | The unique identifier of the object to delete. |
Output
The output JSON contains a simple confirmation of success for the delete operation:
{
"success": true
}
This indicates that the specified object was successfully deleted from the Bubble database.
No binary data output is produced by this operation.
Dependencies
- Requires an API authentication credential configured in n8n to access the Bubble Data API.
- Optional proxy configuration requires a valid proxy URL.
- Relies on internal helper functions to make HTTP requests to the Bubble API endpoints.
Troubleshooting
- Invalid Object ID or Type Name: If the provided object ID or type name does not exist in the Bubble app, the API will likely return an error. Verify that these values are correct and correspond to existing data types and records.
- Proxy Misconfiguration: If "Use Proxy" is enabled but the proxy URL is incorrect or unreachable, API requests will fail. Ensure the proxy URL is valid and accessible.
- API Authentication Errors: Missing or invalid API credentials will cause authentication failures. Confirm that the API key or token is correctly set up in n8n credentials.
- Network Issues: General network connectivity problems can prevent successful API calls. Check network status and firewall settings.
Common error messages may include:
- Unauthorized or 401 errors indicating credential issues.
- 404 Not Found if the object or type does not exist.
- Connection timeout or proxy errors if proxy settings are incorrect.
Resolving these typically involves verifying input parameters, credentials, and network/proxy configurations.