Zalo Reminder icon

Zalo Reminder

Quản lý nhắc nhở Zalo

Actions4

Reminder → Create

AI-generated

Overview

This node allows users to create reminders in a chat environment, specifically targeting either individual users or groups. It is useful for automating notifications or alerts within conversations, such as reminding team members about meetings, deadlines, or recurring events.

Practical examples include:

  • Setting a daily reminder for a user to submit a report.
  • Creating a weekly group reminder for a team meeting.
  • Scheduling a one-time alert with a custom emoji and title.

Properties

Name Meaning
Thread Type The type of conversation where the reminder will be set. Options: "User" or "Group".
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 to associate with the reminder. Defaults to ⏰ (alarm clock).
Start Time The timestamp indicating when the reminder should start.
Repeat Mode How often the reminder repeats. Options: None, Daily, Weekly, Monthly.

Output

The node outputs an array of JSON objects representing the created reminders. Each output item contains the details returned by the underlying API after creating the reminder, including confirmation data such as reminder ID, title, timing, and repeat settings.

No binary data output is produced by this node.

Dependencies

  • Requires an API key credential for authenticating with the external Zalo API service.
  • The node internally uses a client class instantiated with cookie, IMEI, and user agent values obtained from the authentication response.
  • The base URL for API requests is fixed to the Zalo API endpoint.
  • Proper configuration of credentials and network access to the Zalo API is necessary.

Troubleshooting

  • Authentication errors: If the node fails to authenticate, ensure that the provided API key credential is valid and has the necessary permissions.
  • Invalid Thread ID: Providing an incorrect or non-existent thread ID will cause the API call to fail. Verify the ID corresponds to an existing user or group.
  • Missing required fields: The node requires Thread ID and Title at minimum; omitting these will result in errors.
  • API errors: Any error messages from the Zalo API are caught and rethrown with additional context. Check the error message for details and verify API limits or request formats.
  • Date format issues: The Start Time must be a valid date/time string convertible to a timestamp. Invalid formats may cause failures.

Links and References

Discussion