Actions26
- Collections Actions
- Records Actions
- Fields Actions
- Chats Actions
- Files Actions
- User Contacts Actions
- Triggers Actions
Overview
This node operation, "List Messages" under the "Chats" resource, retrieves a paginated list of messages from a specific chat within a collection. It is useful for scenarios where you want to programmatically access chat history or analyze conversations in batches. For example, you might use it to fetch customer support chat logs for sentiment analysis or to archive chat messages for compliance purposes.
Properties
| Name | Meaning |
|---|---|
| Collection Id | The unique identifier of the collection that contains the chat. |
| Chat Id | The unique identifier of the chat whose messages you want to list. |
| Page Number | The page number of results to retrieve, starting at 0. Defaults to 0 (first page). |
| Page Size | The number of messages to return per page. Defaults to 10. |
| Roles | An array of message roles to filter by (e.g., sender roles like user, system, assistant). |
| Send Date Order By | The order in which messages are sorted by their send date; either ascending ("asc") or descending ("desc"). Defaults to "asc". |
Output
The output JSON contains an array of message objects corresponding to the requested page and filters. Each message object typically includes details such as message content, sender role, timestamp, and any other metadata provided by the API. This allows downstream nodes to process or analyze individual messages.
If the node supports binary data output (not indicated here), it would represent attachments or media associated with messages, but this operation focuses on textual message listing.
Dependencies
- Requires an API key credential configured in n8n to authenticate requests to the Cogfy Tables API.
- The base URL for the API must be set in the credentials configuration.
- The node depends on the Cogfy Tables API service being available and accessible.
Troubleshooting
- Missing or invalid Collection Id or Chat Id: The node requires valid identifiers to fetch messages. Ensure these IDs are correct and exist in your Cogfy Tables environment.
- Authentication errors: If the API key or base URL is misconfigured, the node will fail to connect. Verify credential settings.
- Pagination issues: Requesting a page number beyond the available range may return empty results. Adjust page number accordingly.
- Invalid roles filter: The roles property expects a JSON array. Providing malformed JSON or unsupported roles may cause errors or no results.
- API rate limits or downtime: If the API service is down or rate-limited, the node will throw errors. Retry after some time or check service status.