Overview
This node acts as a webhook trigger for the CoachTrigger live event system. It listens for specific predefined events from the CoachTrigger API and triggers workflows in n8n when those events occur. This is useful for automating processes based on user interactions or scheduled message batches related to an AI coaching platform.
Common scenarios include:
- Reacting to new chat messages sent by users.
- Handling activation events of the AI coach for a user.
- Processing feedback received on AI coach messages.
- Triggering workflows on daily morning or evening message batches.
- Responding to user messages directed at the AI coach.
- Capturing clicks on the regenerate icon in the chat interface.
For example, you could use this node to automatically log new chat messages into a CRM, send notifications when the AI coach activates for a user, or analyze feedback on AI coach messages.
Properties
| Name | Meaning |
|---|---|
| Events | The specific webhook event to listen for. Options: - 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 JSON data representing the payload received from the CoachTrigger webhook for the selected event. The structure of this JSON depends on the event type but generally contains all relevant information sent by the CoachTrigger system about that event.
If the event is one of the supported types (e.g., "newChatMessage", "aiCoachActivation"), the entire request body is passed through as the output JSON.
No binary data output is produced by this node.
Dependencies
- Requires an API key credential for authenticating with the CoachTrigger API.
- Needs network access to
https://a.coachtrigger.comendpoints for webhook subscription management and receiving webhook calls. - The node uses HTTP POST webhooks with dynamic paths based on the selected event.
Troubleshooting
- Invalid trigger key error: If the incoming webhook request does not contain the expected trigger key header matching the configured API key, the node will throw an "Invalid trigger key" error. Ensure the correct API key is set in the node credentials and that the CoachTrigger service is sending the correct key.
- Unknown event error: If the node receives a webhook event not listed in its supported options, it will throw an "Unknown event" error. Verify that the event name matches one of the predefined options.
- Webhook subscription failures: The node manages webhook subscriptions via the CoachTrigger API. Network issues or invalid credentials can cause subscription creation or deletion to fail. Check connectivity and API key validity if webhooks do not activate properly.
Links and References
- CoachTrigger API Documentation (hypothetical link, replace with actual if available)
- n8n Webhook Trigger Node Guide: https://docs.n8n.io/nodes/n8n-nodes-base.webhook/