Overview
This node acts as a webhook trigger for the Suppa API, allowing users to receive real-time updates from specified tables within the Suppa system. It listens for create, update, and delete events on chosen tables and triggers workflows when such events occur. This is particularly useful for automating processes that depend on changes in data records, such as syncing databases, sending notifications, or updating dashboards.
For example, you can configure this node to trigger a workflow whenever a new record is inserted into a customer table, enabling immediate follow-up actions like sending welcome emails or updating CRM systems.
Properties
| Name | Meaning |
|---|---|
| Таблиця Name or ID | Select the table to monitor for events. You can choose from a list of available tables or specify a table ID via expression. |
| Event | Choose one or more event types to listen for: Create (insert), Update, Delete. |
| Поля Names or IDs | Optionally select specific fields within the table to monitor for updates. If left empty, all fields are considered. |
| Фільтри (JSON) | Additional filters in JSON format to narrow down which webhook events should trigger the workflow based on field values. |
Output
The node outputs JSON data representing the event payload received from the Suppa API webhook. This JSON contains details about the record change event, including the affected table, event type, and relevant field data.
No binary data output is produced by this node.
Dependencies
- Requires an API key credential for authenticating with the Suppa API.
- The node depends on the Suppa API's webhook subscription endpoints to register, verify, and delete webhooks.
- Network access to the Suppa API base URL must be configured.
- No additional environment variables are required beyond the API authentication setup.
Troubleshooting
- Webhook registration failure: If the node cannot create or verify the webhook subscription, ensure the API key is valid and has sufficient permissions. Also, confirm that the node’s webhook URL is accessible from the Suppa API.
- Empty webhook payloads: The node treats empty POST bodies as health-check pings and responds with success without triggering workflows. Ensure your Suppa instance sends actual event data.
- Filter misconfiguration: Incorrect JSON syntax in the filters property may cause webhook creation to fail or unexpected filtering behavior. Validate JSON format carefully.
- Event not triggering: Verify that the selected events match those emitted by the Suppa API for the chosen table and that the webhook subscription is active.
Links and References
- n8n Expressions Documentation
- Suppa API documentation (not publicly linked here; refer to your Suppa API provider for details)