Actions16
- User Actions
- Activity Actions
- Message Actions
Overview
This node integrates with the CoachTrigger Live API, enabling users to interact with various CoachTrigger services related to user data, activities, messages, and reports. It supports multiple operations such as retrieving user profiles, fetching KPI values, updating message translations, sending AI coach messages, and obtaining report data.
Typical use cases include:
- Fetching detailed user information by CRM or user ID.
- Accessing and updating key performance indicators (KPIs) for users.
- Managing message translations and AI-generated coaching messages.
- Retrieving historical message data between users.
- Obtaining daily or weekly report data for analysis.
For example, a company could automate the retrieval of user KPIs to monitor employee performance or send AI-generated coaching messages to users based on their activity data.
Properties
| Name | Meaning |
|---|---|
| Authentication | Choose between "Company Api" or "System Api" authentication methods. |
The node also supports many other input properties depending on the selected operation, including but not limited to:
| Name | Meaning |
|---|---|
| crmUserId | CRM user ID to fetch user data (used in "getUserData" operation). |
| teamId | Team ID to fetch team activities list (used in "getTeamActivitiesList"). |
| userId | User ID for various operations like getting activities, KPIs, reports, and user profile. |
| coachId | Coach ID for fetching user profile details. |
| activityDate | Date related to activity for KPI retrieval. |
| activityId | Activity ID for KPI retrieval. |
| kpiId | KPI identifier for updating KPI values. |
| kpiValue | Value to update for a specific KPI. |
| kpiDate | Date associated with KPI update. |
| messageId | Message ID for updating translations or AI message updates. |
| messageTranslation | Translation text for a message update. |
| message | Message content for updates or AI coach messages. |
| coachUserId | User ID of the coach sending AI messages or updating AI messages. |
| receiverUserId | User ID of the message recipient in AI coach messaging. |
| messageTranslated | Translated message content (optional in some operations). |
| llmModel | Language model used for AI message generation or updates. |
| tokenIn | Token count input for AI message processing. |
| tokenOut | Token count output for AI message processing. |
| runId | Run identifier for AI message context. |
| threadId | Thread identifier for AI message context. |
| senderId | Sender's user ID for fetching message history. |
| receiverId | Receiver's user ID for fetching message history. |
| messagesAmount | Number of messages to retrieve in history. |
| date | Date parameter for report data or questions list retrieval. |
| type | Type indicator used in some message-related operations. |
Output
The node outputs an array of JSON objects corresponding to the results of each executed operation. Each item contains the raw response from the CoachTrigger API parsed into JSON format.
The structure of the JSON output depends on the specific operation performed, for example:
- User data retrieval returns user profile details.
- KPI operations return KPI values or confirmation of updates.
- Message operations return message histories or confirmation of updates.
- Report operations return daily or weekly report data.
No binary data output is produced by this node.
Dependencies
- Requires valid API credentials for authentication, either via "Company Api" or "System Api" method.
- The node makes HTTP POST requests to endpoints under
https://www.coachtriggerapp.com/crmApi/. - Proper configuration of these credentials within n8n is necessary before using the node.
Troubleshooting
- Authentication errors: Ensure that the correct API key or trigger key is provided according to the selected authentication method.
- Missing required parameters: Many operations require specific IDs (e.g., userId, crmUserId, messageId). Verify all mandatory fields are filled.
- Invalid JSON responses: If the API returns unexpected data, check network connectivity and API status.
- Operation mismatch: Selecting an operation without providing its required parameters will cause errors; always match inputs to the chosen operation.
- API rate limits or permissions: If requests fail due to limits or access rights, consult the API provider for quota or permission adjustments.
Links and References
- CoachTrigger Official Website
- API documentation is implied but not explicitly linked in the code; consult CoachTrigger support for detailed API docs.