Actions113
- Accounts Actions
- Account Users Actions
- Agent Bots Actions
- Users Actions
- Inbox API Actions
- Contacts API Actions
- Conversations API Actions
- Messages API Actions
- CSAT Survey Page Actions
- Account Agent Bots Actions
- Agents Actions
- Canned Responses Actions
- Canned Response Actions
- Custom Attributes Actions
- Contacts Actions
- Contact Actions
- Automation Rule Actions
- Help Center Actions
- Conversations Actions
- Conversation Assignment Actions
- Conversation Labels Actions
- Inboxes Actions
- Messages Actions
- Integrations Actions
- Teams Actions
- Custom Filters Actions
- Webhooks Actions
- Reports Actions
Overview
This node interacts with the Messages API of a chat platform to list all messages within a specific conversation. It is useful for retrieving the entire message history of a conversation between a contact and an inbox channel, enabling workflows that require message analysis, archiving, or further processing.
Practical examples include:
- Fetching conversation messages to display in a custom dashboard.
- Archiving chat histories for compliance or record-keeping.
- Triggering follow-up actions based on message content or timestamps.
Properties
| Name | Meaning |
|---|---|
| Inbox Identifier | The unique identifier of the inbox channel from which to retrieve messages. |
| Contact Identifier | The source ID of the contact involved in the conversation, obtained when the contact was created. |
| Conversation Id | The numeric ID representing the specific conversation whose messages are to be listed. |
Output
The node outputs a JSON array containing the messages of the specified conversation. Each item in the array represents a single message with details such as sender, timestamp, message content, and potentially other metadata depending on the API response.
If the API supports binary data (e.g., attachments), those would be included in the output as binary fields, but this node primarily focuses on textual message data.
Dependencies
- Requires an API key credential for authenticating with the chat platform's API.
- The base URL for the API must be configured in the node credentials.
- The node depends on the external chat platform's Messages API being accessible and responsive.
Troubleshooting
- Missing or invalid identifiers: Ensure that the Inbox Identifier, Contact Identifier, and Conversation Id are correctly provided and correspond to existing entities in the chat platform.
- Authentication errors: Verify that the API key credential is valid and has sufficient permissions to access conversation messages.
- API connectivity issues: Check network connectivity and the correctness of the base URL configured in credentials.
- Empty results: If no messages are returned, confirm that the conversation ID is correct and that there are messages in that conversation.
Links and References
- Refer to the chat platform’s official API documentation for detailed information about the Messages API and conversation message structure.
- n8n documentation on creating and using API credentials for authentication.