Caspio Trigger icon

Caspio Trigger

Starts the workflow when Caspio table events occur.
Join our community

Overview

The Caspio Trigger node starts an n8n workflow when specific events occur on Caspio tables, such as record creation, update, or deletion. It is useful for automating processes that depend on changes in Caspio data, like syncing data to other systems, sending notifications, or triggering downstream workflows. For example, it can trigger a workflow when a new customer record is added or when an existing record is updated with new information.

Use Case Examples

  1. Trigger a workflow when a new record is created in a Caspio table to send a welcome email.
  2. Trigger a workflow when a record is updated to synchronize changes with an external CRM.
  3. Trigger a workflow when a record is deleted to clean up related data in other systems.

Properties

Name Meaning
Notes Optional notes included in the webhook description for documentation or identification purposes.
Event Specifies which table event triggers the webhook: record creation, update, or deletion.
Table The Caspio table to monitor for the selected event. Can be selected from a list or specified by name.
When Any Field Is Changed For update events, determines if the webhook triggers on changes to any field (true) or only specific fields (false).
Field Names or IDs For update events when 'When Any Field Is Changed' is false, specifies which fields trigger the webhook when changed.
Send All Fields Determines whether to include all table fields in the webhook payload. Password fields are excluded for security.
Selected Field Names or IDs Specifies which fields to include in the webhook payload when 'Send All Fields' is false.
Advanced Options Additional configuration options including event sources that can trigger the webhook and whether to return temporary URLs for attachment fields.

Output

JSON

  • secret - Secret token included in the webhook payload for validation.
  • webhookId - Identifier of the webhook that triggered the event.
  • messageId - Unique identifier for the webhook message.
  • eventId - Identifier of the specific event that triggered the webhook.
  • callId - Call identifier for the webhook invocation.
  • accountId - Identifier of the Caspio account.
  • eventDate - Timestamp of when the event occurred.
  • eventType - Type of event that triggered the webhook (e.g., record created, updated, deleted).
  • objectName - Name of the Caspio table involved in the event.
  • data - Array containing the record data fields included in the webhook payload, filtered based on node configuration.

Dependencies

  • Requires Caspio OAuth2 API credentials for authentication.
  • Uses Caspio API endpoints to manage outgoing webhooks and events.

Troubleshooting

  • Webhook creation may fail if the table fields cannot be fetched; ensure the table name is correct and accessible.
  • Webhook validation errors occur if the secret token is missing or does not match; verify webhook secret configuration.
  • Webhook ID mismatch errors indicate the payload is from an unexpected webhook; check webhook URL and configuration.
  • If webhook deletion fails, ensure the API credentials have permissions to manage outgoing webhooks or delete the webhook manually in Caspio.
  • Test webhooks may conflict if not cleaned up; manually delete test webhooks in Caspio if errors occur.

Links

Discussion