Zalo User Interact icon

Zalo User Interact

Gửi tin nhắn và tương tác với Zalo User

Overview

This node operation allows users to create a note or reminder within a specified group on the Zalo platform. It supports setting a title for the note, optionally scheduling a reminder time, configuring repetition frequency, and pinning the note within the group. This functionality is useful for team collaboration, event planning, or task management where group members need to be reminded of important dates or notes.

Practical examples:

  • Scheduling a daily stand-up meeting reminder in a project group.
  • Creating a pinned note with key project deadlines.
  • Setting weekly recurring reminders for group events or polls.

Properties

Name Meaning
Group Id The unique identifier of the Zalo group where the note/reminder will be created.
Tiêu đề nhắc hẹn (noteTitle) The title or subject of the note/reminder.
Thời gian nhắc hẹn (startTime) The scheduled date and time for the reminder. If omitted, the note is created without a reminder time.
Lặp lại (repeat) The frequency at which the reminder repeats. Options: Không lặp (No repeat), Hàng ngày (Daily), Hàng tuần (Weekly), Hàng tháng (Monthly).
Ghim nhắc hẹn (pinAct) Boolean flag indicating whether to pin the note/reminder in the group chat.

Output

The node outputs an array of JSON objects representing the result of the note creation operation. Each object contains details about the created note/reminder, including success status and any relevant metadata returned by the Zalo API.

If binary data output is supported (not explicitly shown in the provided code), it would typically represent attachments or media related to the note, but this node primarily deals with JSON responses.

Dependencies

  • Requires access to the Zalo API with appropriate permissions to manage group notes/reminders.
  • Needs an API authentication token or API key credential configured in n8n to authorize requests.
  • The node uses internal helper classes and methods (e.g., G2 client) to interact with the Zalo service.
  • No external file system or other third-party services are explicitly required based on the provided code.

Troubleshooting

  • Common issues:

    • Invalid or missing Group Id: Ensure the Group Id corresponds to an existing Zalo group accessible by the authenticated user.
    • Missing required fields like noteTitle: The node requires a title for the note; omitting it will cause errors.
    • Incorrect date/time format for startTime: Use ISO 8601 or the datetime format expected by the node.
    • Insufficient permissions or invalid API credentials: Verify that the API key or token has rights to create notes in the target group.
  • Error messages:

    • Authentication failures: Check API credentials and refresh tokens if necessary.
    • Validation errors for input properties: Confirm all required inputs are provided and correctly formatted.
    • API rate limits or service unavailability: Retry after some time or check Zalo API status.

Links and References


Note: The analysis is based solely on static code inspection and provided property definitions. Runtime behavior, dynamic imports, or obfuscated code parts were not executed or resolved.

Discussion