Overview
This node acts as a webhook trigger for various events from the Coach Trigger system API. It listens for specific predefined webhook events related to user interactions and automated message batches within the Coach platform. When one of these events occurs, the node receives the event data and triggers the connected workflow.
Common scenarios where this node is beneficial include:
- Automating responses or follow-up actions when a new chat message is received.
- Tracking user engagement by reacting to AI coach activations or feedback on messages.
- Processing daily morning or evening message batches automatically.
- Handling user messages directed to the AI coach or regenerating content upon user request.
For example, you could use this node to start a workflow that logs every new chat message into a CRM system or to send notifications when users provide feedback on AI coach messages.
Properties
| Name | Meaning |
|---|---|
| Events | The specific webhook event to listen for. Options include: |
| - AI Coach Activation for User | |
| - AI Coach Message Feedback Received | |
| - Daily Evening Message Batch | |
| - Daily Morning Message Batch | |
| - New Chat Message | |
| - The Regenerate Icon Click | |
| - User Message to AI Coach |
Output
The node outputs the JSON payload received from the webhook event in the json output field. This payload contains the event-specific data sent by the Coach Trigger system corresponding to the selected event type.
No binary data output is produced by this node.
Dependencies
- Requires an API key credential for authenticating with the Coach Trigger system.
- The node registers and manages webhooks via HTTP requests to the Coach Trigger API endpoints.
- The webhook URL is dynamically constructed based on the selected event.
- Proper configuration of the API key credential in n8n is necessary for successful operation.
Troubleshooting
- Invalid trigger key error: If the incoming webhook request's trigger key header does not match the stored API key, the node will throw an "Invalid trigger key" error. Ensure the correct API key credential is configured and matches the key expected by the Coach Trigger system.
- Unknown event error: If an unsupported event name is somehow selected or received, the node throws an "Unknown event" error. Verify that the event property is set to one of the supported options.
- Webhook registration failures: If the node cannot create or delete webhooks on the external service, check network connectivity and API key permissions.
- Missing or incorrect credentials: The node requires a valid API key credential; missing or invalid credentials will prevent webhook setup and event processing.
Links and References
- Coach Trigger API Documentation (assumed, based on domain)
- n8n Webhook Trigger Node Guide: https://docs.n8n.io/nodes/n8n-nodes-base.webhook/