Actions22
- Broadcasts Actions
- Embeddings Actions
- Contacts Actions
- Conversations Actions
- Tags Actions
Overview
This node interacts with the Cogfy Messenger API to retrieve all messages within a specific conversation. It is useful for scenarios where you need to fetch the entire message history or paginate through messages in a conversation thread, such as customer support chat logs, team communication archives, or any messaging platform integration.
For example, you might use this node to:
- Load all messages from a customer support conversation to analyze chat content.
- Retrieve paginated messages for display in a custom dashboard.
- Archive conversation messages for compliance or record-keeping.
Properties
| Name | Meaning |
|---|---|
| Conversation Id | The unique identifier of the conversation whose messages you want to retrieve. This is required. |
| Cursor | A pagination cursor used to fetch the next set of messages if the results are paginated. Optional. |
Output
The node outputs JSON data representing the messages retrieved from the specified conversation. The structure typically includes an array of message objects containing details such as message content, sender information, timestamps, and possibly metadata related to the conversation.
If the API supports pagination, the output may also include pagination cursors or tokens to fetch subsequent pages of messages.
No binary data output is indicated by the source code.
Dependencies
- Requires an API key credential for authenticating with the Cogfy Messenger API.
- The base URL for the API must be configured in the node credentials.
- The node depends on the Cogfy Messenger API being accessible and responsive.
Troubleshooting
- Missing or invalid Conversation Id: Ensure that the Conversation Id property is provided and correctly references an existing conversation.
- Pagination issues: If using the Cursor property, verify that the cursor value is valid and corresponds to the expected pagination token returned by previous requests.
- Authentication errors: Confirm that the API key credential is correctly set up and has sufficient permissions.
- API connectivity problems: Check network access and the correctness of the base URL configured in credentials.
- Unexpected API responses: Review the API documentation for any changes or limitations on message retrieval.
Links and References
- Cogfy Messenger API Documentation (example placeholder link)
- n8n Documentation on Creating Custom Nodes