Zalo Reminder icon

Zalo Reminder

Quản lý nhắc nhở Zalo

Actions4

Reminder → List

AI-generated

Overview

This node interacts with a reminder system via the Zalo API, specifically focusing on managing reminders within user or group chat threads. The "List" operation under the "Reminder" resource retrieves a paginated list of reminders for a specified chat thread.

Common scenarios where this node is beneficial include:

  • Fetching upcoming reminders for a particular user or group conversation.
  • Displaying reminders in an external dashboard or application.
  • Automating workflows based on existing reminders in chats.

Practical example:

  • A workflow that lists all reminders for a specific group chat to send summary notifications or perform batch updates.

Properties

Name Meaning
Thread Type The type of chat thread:
• User — Reminder for an individual user.
• Group — Reminder for a group chat.
Thread ID The unique identifier of the chat thread (either a User ID or Group ID). Required field.
Page The page number of the reminder list to retrieve, starting from 1. Defaults to 1.
Count Number of reminders per page to fetch, with a maximum of 50. Defaults to 20.

Output

The node outputs an array of items, each containing a json object representing a reminder retrieved from the Zalo API. Each reminder's JSON structure includes details such as title, emoji, start time, repeat settings, and identifiers relevant to the reminder.

If an error occurs during retrieval and the node is configured to continue on failure, the output item will contain a JSON object with an error field describing the issue.

No binary data output is produced by this node.

Dependencies

  • Requires an API authentication token credential to access the Zalo API.
  • Uses the Zalo API client internally, which requires valid session cookies, device IMEI, and user agent strings obtained from the credential.
  • The base URL for API requests is set to the Zalo API endpoint.
  • No additional environment variables are explicitly required beyond the API credential.

Troubleshooting

  • Common issues:

    • Invalid or expired API credentials leading to authentication failures.
    • Providing an incorrect or non-existent Thread ID causing empty or error responses.
    • Requesting pages beyond available data returns empty results.

  • Error messages:

    • Errors prefixed with "Zalo API:" indicate issues communicating with the Zalo service, often due to invalid credentials or network problems.
    • Validation errors if required properties like Thread ID are missing.

  • Resolutions:

    • Verify and refresh API credentials.
    • Confirm the Thread ID corresponds to an existing user or group.
    • Adjust pagination parameters to valid ranges.

Links and References

Discussion