Record
AI-generatedOverview
The Cubable Trigger node starts an n8n workflow when specific events occur in Cubable records. It listens for events such as record creation, updates, and deletions from specified sources like User, API, Automation, or Form. This node is useful for automating workflows based on changes in Cubable data, such as syncing records, sending notifications, or triggering downstream processes when records are modified.
Use Case Examples
- Trigger a workflow when a new record is created by a user in a specific Cubable table.
- Start a workflow when records are updated via API calls, including previous field values for comparison.
- Listen for record deletions triggered by automation and process cleanup tasks accordingly.
Properties
| Name | Meaning |
|---|---|
| Authentication | Selects the authentication method to connect to Cubable, currently supporting an Access Token. |
| Base | Specifies the Cubable Base to monitor for record events. Can be selected from a list or entered by ID. |
| Table | Specifies the Cubable Table within the selected Base to monitor for record events. Can be selected from a list or entered by ID. |
| Source Types | Specifies the sources of events to listen for, such as User, API, Automation, or Form. |
| Event Types | Specifies the types of record events to listen for, such as creation, update, or deletion. |
| Additional Options | Configures additional filters and output options for the triggered records. |
Output
JSON
headers- HTTP headers from the webhook request.params- Parameters from the webhook request.query- Query parameters from the webhook request.body- Body content of the webhook request, including event details.webhookUrl- The URL of the webhook that triggered the event.executionMode- Indicates if the workflow was triggered in 'test' or 'production' mode.payload- The detailed event payload fetched from Cubable, containing the record event data.
Dependencies
- Cubable API access with an access token credential
Troubleshooting
- Webhook creation or deletion failures may occur due to invalid Base or Table IDs or network issues. Verify IDs and network connectivity.
- If no events trigger the workflow, ensure the webhook URL is correctly registered in Cubable and the event filters (source types, event types) match the expected events.
- Errors fetching event payloads may indicate expired or invalid webhook credentials; re-creating the webhook may resolve this.
Links
- Cubable API Webhooks Documentation - Official documentation for managing webhooks and event payloads in Cubable.