Actions6
Chỉnh Sửa Lịch Hẹn
AI-generatedOverview
This node operation allows users to edit an existing appointment (reminder) in Zalo, a messaging platform. It is useful for scenarios where users need to update details of scheduled reminders such as title, emoji, start time, and repeat frequency within personal or group conversations. For example, a user can change the meeting title or reschedule the start time of a team meeting reminder.
Use Case Examples
- Editing a reminder in a personal chat to update the meeting title and start time.
- Modifying a group chat reminder to change the emoji and repeat frequency.
Properties
| Name | Meaning |
|---|---|
| Loại Hội Thoại | Specifies the type of conversation where the reminder exists, either personal (user) or group. |
| ID Người Dùng (Bắt Buộc) | The user ID for personal conversation reminders. Required when thread type is 'user'. |
| ID Nhóm (Bắt Buộc) | The group ID for group conversation reminders. Required when thread type is 'group'. |
| Tiêu Đề (Bắt Buộc) | The title of the reminder appointment. |
| Biểu Tượng Cảm Xúc | Emoji representing the reminder appointment. |
| Thời Gian Bắt ĐầU | The start time of the reminder. If left empty, the current time is used. |
| Chế Độ Lặp Lại | The repeat frequency of the reminder, such as no repeat, daily, weekly, or monthly. |
| ID Lịch Hẹn (Bắt Buộc) | The ID of the reminder to be edited or removed. |
Output
JSON
threadId- ID of the conversation (user or group) where the reminder belongs.threadType- Type of the conversation, either 'user' or 'group'.reminderId- ID of the reminder being edited.title- Updated title of the reminder.emoji- Updated emoji representing the reminder.startTime- Updated start time of the reminder as a timestamp.repeat- Updated repeat frequency of the reminder.success- Indicates if the edit operation was successful.error- Error message if the edit operation failed.
Dependencies
- Zalo API credentials including cookie, IMEI, and user agent for authentication.
Troubleshooting
- Ensure that the Zalo API credentials (cookie, IMEI, user agent) are correctly set and valid; otherwise, the node will fail to initialize the API and throw an error.
- The 'reminderId' property is mandatory for editing a reminder; missing or invalid IDs will cause validation errors.
- If the operation type is incorrect or unsupported, the node throws an 'Unknown operation' error.
- Handle errors gracefully by enabling 'Continue On Fail' to avoid stopping the entire workflow on individual item failures.