Overview
The Cubable Trigger node listens for events occurring in a Cubable database environment and starts an n8n workflow when those events happen. It is designed to react to changes in records within specified bases and tables, such as record creation, updates, or deletions. This node is useful for automating workflows that depend on real-time data changes in Cubable, like syncing data to other systems, sending notifications, or triggering downstream processes.
Typical use cases include:
- Automatically processing new records added by users or external APIs.
- Responding to updates made via automation or forms.
- Tracking deletions to maintain data consistency elsewhere.
For example, you could configure the node to trigger whenever a user creates or updates a record in a specific table, then use the output data to update a CRM system or send an alert email.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authenticating with Cubable; currently supports "Access Token". |
| Base | The Cubable base (database) to monitor for record events. Can be selected from a list or specified by ID. |
| Table | The specific table within the base to watch for record events. Can be selected from a list or specified by ID. |
| Source Types | Specifies which sources of events to listen for. Options: User, API, Automation, Form. For example, selecting "User" triggers on user-made changes, while "API" triggers on programmatic changes. |
| Event Types | Types of record events to listen for. Options: Record Created, Record Updated, Record Deleted. You can select one or more event types to trigger the workflow accordingly. |
| Additional Options | Collection of optional settings to refine the trigger behavior: • Trigger on Specific Fields: Only trigger if changes occur in specified custom fields. • Include Specific Field Values: Include values of specified fields in output. • Include Previous Values: Whether to include previous field values when changes occur (boolean). |
Output
The node outputs JSON data representing the event payload received from Cubable. This includes:
- Metadata about the event such as base ID, webhook ID, and cursor for pagination.
- The actual record data involved in the event, including current and optionally previous values of fields depending on configuration.
- Headers, query parameters, and body of the webhook request for context.
The output is structured as a single JSON object under the json key in the main output. There is no binary data output.
Dependencies
- Requires an active Cubable account with API access.
- Needs an API authentication token (access token) configured in n8n credentials.
- The node interacts with Cubable's webhook API to create, check, and delete webhooks dynamically.
- Network connectivity to Cubable's API endpoints is necessary.
Troubleshooting
- Webhook Creation Failures: Errors during webhook creation may indicate invalid base or table IDs, insufficient permissions, or network issues. Verify IDs and API credentials.
- Invalid Base/Table ID Format: The node validates IDs against a regex pattern. Ensure IDs conform to the expected format (a 26-character string starting with digits 0-7).
- Missing Event Data: If the workflow triggers but no meaningful data appears, check that the event types and source types are correctly configured to match your use case.
- Permission Denied Errors: Make sure the API token has sufficient rights to manage webhooks and read data from the specified base/table.
- Webhook Not Triggering: Confirm that the webhook URL registered in Cubable matches the one provided by n8n and that the workflow is active.
Links and References
- Cubable API Documentation (for details on webhook setup and event payloads)
- n8n Webhook Node Documentation (general webhook usage in n8n)
- Cubable Trigger GitHub Repository (if available for source and updates)