Overview

The Ragic Trigger node listens for webhook events from the Ragic platform, specifically for create, update, or delete record events. It is designed to trigger workflows in n8n when these events occur in Ragic, enabling automation based on changes in Ragic data. Common use cases include syncing data between Ragic and other systems, triggering notifications, or updating related records in other applications when Ragic records are created, updated, or deleted.

Use Case Examples

1. Trigger a workflow when a new record is created in Ragic to send a notification email.
2. Start a process to update a CRM system when a Ragic record is updated.
3. Automatically archive related data when a record is deleted in Ragic.

Properties

Output

JSON

• bodyData - Contains the data received from the Ragic webhook event, representing the details of the record change that triggered the workflow.

Dependencies

• Requires an API key credential for Ragic (ragicTriggerApi) to authenticate webhook subscription management and event reception.

Troubleshooting

• Ensure the API key credential is correctly configured and has the necessary permissions to manage webhooks in Ragic.
• The 'Webhook Event' property must not be empty; otherwise, the node will throw an error indicating that the webhook event cannot be empty.
• Verify that the webhook URL registered in Ragic matches the URL generated by the node to avoid webhook subscription failures.
• Common errors may include authentication failures or webhook subscription errors, which can be resolved by checking API key validity and webhook URL correctness.

Links

• Ragic Webhooks Documentation - Official documentation on how webhooks work in Ragic, useful for understanding event types and webhook setup.