SUPPA Event Trigger
AI-generatedOverview
This node acts as a trigger for events from the Suppa API via webhooks. It listens for changes in a specified table (entity) such as creation, update, or deletion of records, and triggers workflows accordingly. This is useful for automating processes based on real-time data changes in Suppa, such as syncing data, sending notifications, or updating other systems.
Use Case Examples
- Trigger a workflow when a new record is created in a specific Suppa table.
- Trigger a workflow when records are updated or deleted in a Suppa table, optionally filtering by specific fields or conditions.
Properties
| Name | Meaning |
|---|---|
| Таблиця Name or ID | Select the table (entity) in Suppa to monitor for events. You can choose from a list or specify an ID using an expression. |
| Event | Select one or more event types to listen for: Create (insert), Update, or Delete events on the selected table. |
| Поля Names or IDs | Optionally select specific fields to monitor for updates. Only changes to these fields will trigger the webhook. You can choose from a list or specify IDs using an expression. |
| Фільтри (JSON) | Optional JSON filters to apply additional conditions for triggering the webhook. Only events matching these filters will trigger the workflow. |
Output
JSON
workflowData- Array containing the JSON data received from the Suppa webhook event.
Dependencies
- Requires Suppa API credentials including base URL and API key for authentication.
Troubleshooting
- Webhook creation or existence check may fail if API credentials are incorrect or the Suppa API is unreachable.
- If no events trigger the workflow, verify that the correct table, events, fields, and filters are configured.
- Errors during webhook deletion or creation may indicate permission issues or invalid parameters.
Links
- n8n Expressions Documentation - Reference for using expressions to specify dynamic values in node parameters.