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 various operations on Bubble data objects, including creating, deleting, retrieving single objects, retrieving multiple objects ("Get Many"), and updating objects.
The "Get Many" operation for the "Object" resource fetches multiple entries of a specified data type from Bubble's database. Users can apply filters, sorting, and limits to refine the returned dataset. This is particularly useful when you want to retrieve lists of items matching certain criteria, such as all customers in a region or all orders above a certain amount.
Practical examples:
- Fetching all "Event" objects happening within a specific date range.
- Retrieving up to 50 "Product" objects that contain the word "coffee" in their name.
- Getting all "User" objects sorted by their signup date in descending order.
Properties
| Name | Meaning |
|---|---|
| Use Proxy | Whether to route API requests through a specified proxy server. |
| Proxy URL | The URL of the proxy server to use if "Use Proxy" is enabled (e.g., http://proxy.example.com:8080). |
| Type Name | The name of the Bubble data type (object type) to query. This defines which kind of objects will be retrieved. |
| Return All | Whether to return all matching results or limit the number of results returned. |
| Limit | Maximum number of results to return if "Return All" is false. Value must be between 1 and 100. |
| JSON Parameters | Whether to provide filter parameters as raw JSON instead of using the UI form fields. |
| Options | Additional options for filtering and sorting the results: |
| - Filters | A collection of filters to refine the search results. Each filter includes: • Key: Field name to filter on. • Constrain: Condition type (e.g., equals, not equal, text contains, greater than, geographic search, etc.). • Value: Value to compare against (not required for some constraints like "is empty"). |
| - Filters (JSON) | Alternative way to specify filters as a JSON array of constraint objects, allowing complex queries. |
| - Sort | Sorting options including: • Sort Field: Field to sort by (or _random_sorting for random order).• Descending: Boolean to indicate descending order. • Geo Reference: Address string used when sorting by geographic fields. |
Output
The output is a JSON array where each element represents an object retrieved from the Bubble Data API according to the specified filters and sorting. Each object contains its fields as key-value pairs corresponding to the Bubble data type's schema.
If "Return All" is true, all matching objects are returned; otherwise, only up to the specified limit are included.
No binary data output is produced by this operation.
Dependencies
- Requires an API authentication token credential configured in n8n to access the Bubble Data API.
- Optionally requires a proxy server URL if "Use Proxy" is enabled.
- Relies on internal helper functions to make HTTP requests to the Bubble API endpoints.
Troubleshooting
- Invalid JSON in Filters (JSON): If the JSON provided in the "Filters (JSON)" property is malformed, the node will throw an error indicating the filters must be valid JSON. To fix, ensure the JSON syntax is correct.
- Empty or Incorrect Type Name: Providing an incorrect or empty "Type Name" will result in failed API calls or empty responses. Verify the exact data type name as defined in your Bubble app.
- Proxy Connection Issues: If "Use Proxy" is enabled but the proxy URL is incorrect or unreachable, API requests will fail. Confirm the proxy URL and network accessibility.
- Limit Exceeded: Setting a "Limit" outside the allowed range (1-100) may cause errors. Ensure the limit is within the specified bounds.
- Filter Constraints Misuse: Using incompatible constraint types for field types (e.g., "text contains" on a numeric field) may lead to unexpected results or errors. Match constraints appropriately to field types.