Actions116
- 💬 Chats Actions
- 👤 Contacts Actions
- 👥 Groups Actions
- Get Info Admin Only
- Set Messages Admin Only
- Get Messages Admin Only
- Get Invite Code
- Revoke Invite Code
- Get Participants
- Add Participants
- Remove Participants
- Promote To Admin
- Demote To Admin
- Create Group
- Get Groups
- Join Info Group
- Join Group
- Refresh Groups
- Get Group
- Delete Group
- Leave Group
- Get Chat Picture
- Set Picture
- Delete Picture
- Set Description
- Set Subject
- Set Info Admin Only
- 🖥️ Sessions Actions
- 🆔 Profile Actions
- 🖼️ Screenshot Actions
- 📤 Chatting Actions
- 📢 Channels Actions
- 🟢 Status Actions
- ✅ Presence Actions
- 🏷️ Labels Actions
- 🔍 Observability Actions
- 🔑 Auth Actions
Overview
This node operation retrieves chat data from a specified session. It is useful for scenarios where you need to fetch and analyze chat conversations, such as monitoring customer support interactions, extracting chat history for reporting, or integrating chat data into other workflows.
Use Case Examples
- Fetching the latest 100 chats sorted by conversation timestamp to analyze recent customer interactions.
- Retrieving chats sorted by name in ascending order for alphabetical listing in a dashboard.
Properties
| Name | Meaning |
|---|---|
| Session | The name of the session from which to retrieve chats. This is required to identify the chat source. |
| Sort By | The field by which to sort the retrieved chats, such as conversation timestamp, id, or name. |
| Sort Order | The order in which to sort the chats, either descending (newest first) or ascending (oldest first). |
| Limit | The maximum number of chat records to retrieve. A value of 0 means no limit. |
| Offset | The number of chat records to skip before starting to collect the result set, useful for pagination. |
| Request Options | Additional request settings such as batching, SSL certificate validation, proxy configuration, and request timeout. |
Output
JSON
chats- Array of chat objects retrieved from the specified session, containing chat details such as id, name, and timestamps.
Dependencies
- Requires an API key credential or session authentication to access chat data from the service.
Troubleshooting
- Ensure the session name is correct and active; an invalid session will result in no data or errors.
- Check network connectivity and proxy settings if requests fail or time out.
- If SSL certificate validation errors occur, consider enabling the option to ignore SSL issues, but be aware of security risks.
- Verify that the limit and offset values are set appropriately to avoid empty results or excessive data retrieval.