Actions28
- Task Actions
- Chat Message Actions
- User Actions
- Quest Actions
- Group Actions
- Content Actions
- Inbox Actions
- Skill (Spell) Actions
- Cron Actions
Overview
This node operation retrieves messages from an inbox, either fetching all messages or using pagination to load messages page by page. It is useful for scenarios where users need to access conversation messages, such as customer support systems, chat applications, or any messaging platform integration. For example, it can be used to load all messages in a conversation or to load messages page-wise for better performance and user experience.
Use Case Examples
- Load all messages from the inbox to analyze conversation history.
- Fetch messages page by page to display in a chat interface with pagination controls.
Properties
| Name | Meaning |
|---|---|
| All Messages | Whether to load all messages or use pagination. |
| Conversation GUID | GUID of the conversation to filter messages. Leave empty to get all messages. |
| Page Number | Load the messages of the selected page, with 10 messages per page. |
| Request Options | Additional request options such as batching, SSL certificate validation, proxy settings, and timeout configuration. |
Output
JSON
messages- Array of inbox messages retrieved from the API.conversationId- The GUID of the conversation for which messages were retrieved.page- The page number of the messages retrieved when pagination is used.
Dependencies
- Requires an API key credential for authentication to access the inbox messages API.
Troubleshooting
- If the node returns no messages, verify that the conversation GUID is correct or empty to fetch all messages.
- If pagination is used, ensure the page number is within the valid range of available pages.
- Timeout errors may occur if the server is slow to respond; increase the timeout setting if needed.
- SSL certificate validation errors can be bypassed by enabling the 'Ignore SSL Issues' option, but this is insecure and should be used with caution.