Bubble With Proxy icon

Bubble With Proxy

Consume the Bubble Data API with proxy support

Actions5

Overview

This node, named "Bubble With Proxy," allows users to interact with the Bubble Data API while optionally routing requests through a proxy server. It supports operations on Bubble data objects such as retrieving, creating, updating, and deleting them.

A common use case is when you want to automate workflows that involve Bubble.io app data but need to route API calls through a proxy for security, compliance, or network reasons. For example, you might retrieve a specific object by its ID or update an object's properties programmatically within an n8n workflow.

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 "Use Proxy" is true.
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 retrieve or delete.

Output

The node outputs JSON data representing the result of the requested operation:

  • For Get operation: Outputs the retrieved object data as JSON.
  • For Create operation: Outputs the created object data as JSON.
  • For Update operation: Outputs { success: true } indicating the update was successful.
  • For Delete operation: Outputs { success: true } indicating the deletion was successful.
  • For Get All operation: Outputs an array of objects matching the query parameters.

No binary data output is produced by this node.

Dependencies

  • Requires an API authentication credential to access the Bubble Data API.
  • Supports optional proxy configuration via the "Use Proxy" and "Proxy URL" properties.
  • Relies on internal helper functions (bubbleApiRequest, bubbleApiRequestAllItems) to perform HTTP requests to the Bubble API.

Troubleshooting

  • Invalid JSON in Filters: When using filters in the "Get All" operation with JSON input, invalid JSON will cause an error. Ensure filter JSON is well-formed.
  • Missing Required Fields: "Type Name" and "Object ID" are required for certain operations; missing these will cause errors.
  • Proxy Misconfiguration: If "Use Proxy" is enabled but the "Proxy URL" is incorrect or unreachable, API requests will fail.
  • API Authentication Errors: Ensure the API key or authentication token is valid and has sufficient permissions.
  • Operation Not Supported: Only the "Object" resource with operations like get, create, update, delete, and getAll are supported.

Links and References

Discussion