Overview

The Trengo Trigger node listens for specific webhook events from the Trengo platform. It is designed to trigger workflows in n8n when certain events occur in Trengo, such as receiving inbound messages, sending outbound messages, ticket updates, voice call events, and more. This node is useful for automating responses or actions based on real-time events in Trengo, like updating CRM systems, sending notifications, or logging activities.

Use Case Examples

1. Trigger a workflow when an inbound message is received in Trengo to automatically create a support ticket.
2. Start a workflow when a ticket is closed to update customer records or send follow-up emails.
3. Listen for voice call events to log call details or trigger call analytics processes.

Properties

Output

JSON

• body - The normalized webhook event data received from Trengo, containing details about the specific event that triggered the workflow.

Dependencies

• Requires Trengo API credentials for authentication to manage webhook lifecycle (create, check, delete).

Troubleshooting

• Webhook verification may fail if the Trengo signature header is missing or incorrect, resulting in the workflow not triggering. Ensure the webhook secret is correctly stored and used for signature verification.
• If webhook creation fails or the response does not contain expected data (id, signing_secret, type), the node will throw an error. Verify API credentials and permissions.
• If the webhook is deleted externally or becomes invalid, the node will attempt to recreate it. If this fails, check API connectivity and credentials.

Links

• Trengo Webhooks Documentation - Official documentation for Trengo webhook events and setup.