SUPPA 2.0 Event Trigger icon

SUPPA 2.0 Event Trigger

Get data from Suppa API via webhooks

SUPPA 2.0 Event Trigger

AI-generated

Overview

This node acts as a trigger for events from the Suppa API via webhooks. It allows users to listen for create, update, and delete events on specified tables within the Suppa system. The node is useful for automating workflows that need to respond to changes in data stored in Suppa tables, such as syncing data, sending notifications, or triggering other processes when records are inserted, updated, or deleted.

Use Case Examples

  1. Trigger a workflow when a new record is created in a specific Suppa table.
  2. Trigger a workflow when a record is updated in a Suppa table to synchronize changes with another system.
  3. Trigger a workflow when a record is deleted from a Suppa table to perform cleanup tasks.

Properties

Name Meaning
Таблиця Name or ID Select the Suppa table to monitor for events. Users 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, and Delete.
Поля Names or IDs Optionally select specific fields to monitor for changes. Only events involving these fields will trigger the webhook.
Фільтри (JSON) Optional JSON filters to apply additional conditions for triggering the webhook.

Output

JSON

  • id - ID of the webhook event data.
  • url - URL of the webhook.
  • entity - Entity (table) information related to the event.
  • isActive - Indicates if the webhook subscription is active.
  • name - Name of the webhook subscription.

Dependencies

  • Suppa API with an API key credential for authentication

Troubleshooting

  • Ensure the API credentials are correctly configured and valid to authenticate with the Suppa API.
  • Verify that the selected table exists and the user has permission to access it.
  • Check that the webhook URL is correctly set and accessible from the Suppa API.
  • If the webhook is not triggering, verify that the event types and filters are correctly configured.
  • Common error messages include authorization errors (401) due to missing or invalid API keys, and errors related to invalid JSON filters.

Links

Discussion