Actions11
Overview
This node acts as a webhook trigger for live chat escalations within a chatbot system. It listens for events where a live chat session is escalated, typically from an automated chatbot to a human agent or another escalation process. This trigger is useful in workflows that need to react immediately when a live chat escalation occurs, such as notifying support teams, logging escalation details, or initiating follow-up actions.
Practical examples include:
- Automatically sending an alert email or Slack message to customer support when a chat is escalated.
- Logging escalation events into a CRM or database for analytics.
- Triggering additional automation steps like creating a support ticket or updating customer records.
Properties
| Name | Meaning |
|---|---|
| Chatbot Name or ID | Select the chatbot by name or specify its ID. Determines which chatbot's live chat escalations to listen for. |
| Webhook | Hidden property representing the webhook identifier used internally by the node. |
| Options | Collection of optional settings: |
| Enable Webhook Debug | Boolean flag to enable extra logging for debugging webhook requests and responses. |
Output
The node outputs JSON data representing the live chat escalation event received via the webhook. The output structure mirrors the payload sent by the chatbot platform when a live chat escalation occurs. This typically includes details about the chat session, user information, escalation context, timestamps, and any relevant metadata.
The output is provided as an array with one item per event, each containing a json field with the event data.
No binary data output is involved.
Dependencies
- Requires an API key credential for authenticating with the chatbot platform's API.
- Needs the base URL of the chatbot platform API configured in credentials.
- The node registers a webhook URL with the chatbot platform to receive live chat escalation events.
- The node depends on n8n's HTTP request helper methods to communicate with the chatbot API.
Troubleshooting
- Webhook registration failure: If the webhook cannot be registered, ensure the API key and base URL are correctly configured and have sufficient permissions.
- Missing or invalid chatbot ID: Selecting or specifying a valid chatbot is mandatory; otherwise, the webhook registration will fail.
- Invalid response format: If the chatbot platform returns unexpected data, the node may throw errors. Verify the platform's API status and compatibility.
- Debugging: Enable "Enable Webhook Debug" option to get detailed logs for troubleshooting webhook issues.
- Common error messages:
- "Base URL is missing in credentials": Check that the API base URL is set in the credentials.
- "Failed to register webhook": Indicates issues during webhook creation; verify network connectivity and API permissions.
- "Invalid response format": The API returned data not matching expected structure; check API version and response content.
Links and References
- n8n Expressions Documentation
- Chatbot platform API documentation (refer to your specific chatbot provider's docs for webhook setup and event formats)