Actions16
- User Actions
- Activity Actions
- Message Actions
Overview
This node interacts with a Coach Trigger development server API to manage messages related to AI coaching. Specifically, the "Create a Message as AI Coach" operation allows sending a message from an AI coach to a receiver user within the system. This is useful in scenarios where automated coaching messages need to be sent programmatically, such as delivering personalized advice, feedback, or motivational content generated by an AI model.
Practical examples include:
- Sending AI-generated coaching tips to employees based on their performance data.
- Delivering translated coaching messages to users in different languages.
- Tracking and managing AI coach conversations with users for training or support purposes.
Properties
| Name | Meaning |
|---|---|
| Authentication | Choose between "Company Api" (using a company API key) or "System Api" (using a system API key). |
| Coach User ID | The user ID of the AI coach sending the message. |
| Receiver User ID | The user ID of the message recipient. |
| Message | The main content of the message to send. |
| Message Translated | Optional translated version of the message content. |
| LLM Model | The large language model used to generate the message (optional). |
| Token In | Token count for input to the language model (optional, treated as sensitive). |
| Token Out | Token count for output from the language model (optional, treated as sensitive). |
| Run ID | Identifier for the run/session of the AI coach interaction (optional). |
| Thread ID | Identifier for the conversation thread (optional). |
| Type | A string representing the message type; default is "0". |
Output
The node outputs JSON data representing the response from the Coach API after creating the AI coach message. The exact structure depends on the API response but typically includes details about the created message such as IDs, timestamps, status, and any metadata returned by the service.
No binary data output is involved in this operation.
Dependencies
- Requires access to the Coach Trigger development server API at
https://dev.mymatrixapp.com/crmApi/. - Requires either a company API key credential or a system API key credential configured in n8n for authentication.
- Network connectivity to the API endpoint must be available.
Troubleshooting
- Authentication errors: Ensure that the correct API key credential is selected and properly configured. Using the wrong authentication option or invalid keys will cause authorization failures.
- Missing required fields: The "Coach User ID" and "Receiver User ID" are mandatory. Omitting these will result in errors from the API.
- Invalid message content: If the message or translated message contains unsupported characters or formats, the API might reject the request.
- API endpoint unreachable: Network issues or incorrect endpoint URLs can cause request failures. Verify connectivity and endpoint correctness.
- Token counts: Providing non-numeric or malformed token counts may cause unexpected behavior; ensure these are valid strings representing numbers if used.
Links and References
- Coach Trigger API Documentation (Assumed URL for reference, replace with actual if available)
- n8n Documentation on HTTP Request Node for understanding how API calls work in n8n.