Zalo Reminder icon

Zalo Reminder

Quản lý nhắc nhở Zalo

Actions4

Reminder → Edit

AI-generated

Overview

This node allows editing reminders in a chat system, supporting both user and group conversations. It is useful for updating existing reminder details such as title, emoji, start time, and repeat mode. Typical use cases include modifying scheduled notifications or alerts sent to individual users or groups within a messaging platform.

For example, you can update the title and start time of a reminder previously set for a user chat or change the repeat frequency of a group reminder from daily to weekly.

Properties

Name Meaning
Thread Type The type of conversation: "User" (reminder for an individual user) or "Group" (for a group chat).
Thread ID The unique identifier of the conversation (either User ID or Group ID). Required.
Title The title or subject of the reminder. Required.
Emoji An emoji symbol representing the reminder. Default is ⏰.
Start Time The timestamp indicating when the reminder should start.
Repeat Mode How often the reminder repeats: None, Daily, Weekly, or Monthly.
Reminder ID The unique identifier of the reminder to edit. Required.

Output

The node outputs an array of JSON objects, each representing the result of the edit operation on a reminder. Each output item contains:

  • json: The response data from the API after editing the reminder, which includes updated reminder details.
  • pairedItem: Metadata linking the output to the corresponding input item.

No binary data output is produced by this node.

Dependencies

  • Requires an API key credential for authenticating with the external chat/reminder service.
  • Uses an SDK client initialized with authentication cookies, device identifiers, and user agent strings obtained from the credentials.
  • The base URL for API requests is preset to the chat platform's API endpoint.
  • Proper configuration of the API authentication token and related parameters in n8n credentials is necessary.

Troubleshooting

  • Common issues:

    • Invalid or expired API credentials causing authentication failures.
    • Providing incorrect or missing Reminder ID will prevent the node from locating the reminder to edit.
    • Incorrect Thread ID or Thread Type mismatch may cause errors or no updates.
    • Date/time format errors for the Start Time property.

  • Error messages:

    • Errors containing "Zalo API" indicate problems communicating with the external API, often due to invalid credentials or network issues.
    • Validation errors if required fields like Reminder ID, Thread ID, or Title are missing.

  • Resolutions:

    • Verify that the API key credential is valid and has not expired.
    • Double-check all required properties are provided and correctly formatted.
    • Ensure the Thread Type matches the actual conversation type for the given Thread ID.
    • Confirm date/time values are valid ISO timestamps or compatible formats.

Links and References

Discussion