Zalo Reminder icon

Zalo Reminder

Quản lý nhắc nhở Zalo

Actions4

Reminder → Remove

AI-generated

Overview

This node interacts with a reminder system on the Zalo platform, specifically allowing users to remove existing reminders. It is useful in scenarios where scheduled notifications or reminders need to be canceled or deleted from either individual user chats or group chats.

Practical examples include:

  • Removing a personal reminder set for a user chat.
  • Deleting a group reminder that is no longer relevant.

Properties

Name Meaning
Thread Type The type of conversation where the reminder exists. Options: "User" (personal chat), "Group" (group chat).
Thread ID The unique identifier of the conversation (either User ID or Group ID) where the reminder is set. Required.
Reminder ID The unique identifier of the reminder to be removed. Required.

Output

The node outputs an array of JSON objects corresponding to each input item processed. Each output item contains:

  • json: The response from the Zalo API after attempting to remove the specified reminder. This typically includes confirmation of deletion or error details.
  • pairedItem: Metadata linking the output to the original input item.

No binary data is produced by this node.

Dependencies

  • Requires an API key credential for authenticating with the Zalo API.
  • Uses the Zalo API endpoint at https://openapi.zalo.me/v2.0/oa/reminder.
  • The node internally uses a helper class to interact with the Zalo API, which requires cookie, IMEI, and user agent information obtained from the authentication process.

Troubleshooting

  • Common issues:

    • Invalid or missing Thread ID or Reminder ID will cause the API call to fail.
    • Incorrect Thread Type may lead to the reminder not being found or deleted.
    • Authentication failures if the API key or credentials are invalid or expired.

  • Error messages:

    • Errors returned from the Zalo API are caught and rethrown with additional context, e.g., "Zalo API: <error message>".
    • If the node is configured to continue on failure, errors for individual items are returned in the output JSON under an error field.

  • Resolution tips:

    • Verify that all required fields (Thread ID, Reminder ID) are correctly provided.
    • Ensure the API key credential is valid and has necessary permissions.
    • Confirm the Thread Type matches the actual conversation type of the reminder.

Links and References

Discussion