Actions16
- User Actions
- Activity Actions
- Message Actions
Overview
This node interacts with the CoachTrigger API to retrieve message history between two users. Specifically, the "Get Messages History" operation fetches a specified number of messages exchanged between a sender and a receiver. This is useful in scenarios where you want to analyze past communications, audit conversations, or display chat history within an automation workflow.
Practical examples:
- Retrieving recent chat messages between a coach and a user for review.
- Pulling message logs to trigger follow-up actions based on conversation content.
- Archiving communication history for compliance or reporting purposes.
Properties
| Name | Meaning |
|---|---|
| Authentication | Choose the authentication method: "Company Api" or "System Api". |
| Sender ID | The unique identifier of the message sender. |
| Receiver ID | The unique identifier of the message receiver. |
| Message Amount | The number of messages to retrieve from the history. |
| Type | (Optional) A string parameter that can specify a message type or category; default is "0". |
Output
The output is a JSON array containing the retrieved messages history data as returned by the CoachTrigger API. Each item in the output corresponds to one input execution and contains the full response JSON under the json property.
The structure of the JSON depends on the API response but typically includes details such as message content, timestamps, sender and receiver IDs, and possibly message metadata.
The node does not output binary data.
Dependencies
- Requires access to the CoachTrigger API.
- Requires either a "Company Api" or "System Api" authentication credential configured in n8n.
- Network connectivity to
https://www.coachtriggerapp.com/crmApi/message/history.
Troubleshooting
- Authentication errors: Ensure the correct API key or system key is provided and valid. Invalid or missing credentials will cause authorization failures.
- Missing required parameters: The node requires
senderId,receiverId, andmessagesAmount. Omitting any of these will likely result in errors or empty responses. - API rate limits or downtime: If the API service is unavailable or rate-limited, requests may fail or return errors. Check API status and retry later.
- Invalid JSON response: If the API returns malformed JSON, the node may throw parsing errors. Verify API stability and response format.
Links and References
- CoachTrigger API Documentation (assumed URL for reference)
- n8n Documentation on HTTP Request Node (for understanding HTTP request handling)
This summary focuses solely on the "Message" resource and the "Get Messages History" operation as requested.