Zalo Send Message icon

Zalo Send Message

Gửi tin nhắn qua API Zalo sử dụng kết nối đăng nhập bằng cookie

Zalo Send Message → Gửi tin nhắn

AI-generated

Overview

This node sends messages through the Zalo API using a logged-in session authenticated by a cookie. It supports sending text messages to individual users or groups, with options for urgency levels, mentions, quoting previous messages, and attaching images. It is useful for automating communication on the Zalo platform, such as sending notifications, alerts, or conversational messages in personal or group chats.

Use Case Examples

  1. Sending a text message to a specific user with normal urgency.
  2. Sending a message to a group chat with mentions of specific users.
  3. Quoting a previous message in a reply.
  4. Sending a message with one or more image attachments.

Properties

Name Meaning
ID cuộc trò chuyện / Thread ID The ID of the conversation (user or group) to send the message to.
Loại cuộc trò chuyện Select the type of conversation: individual user or group.
Nội dung tin nhắn / Message Content The content of the message to send.
Độ khẩn cấp / Urgency Select the urgency level of the message.
Tùy chọn nâng cao / Advanced Options Additional options for the message such as mentions, quoting a previous message, and attachments (images).

Output

JSON

  • success - Indicates if the message was sent successfully.
  • response - The response object from the Zalo API after sending the message.
  • threadId - The ID of the conversation where the message was sent.
  • threadType - The type of the conversation (user or group).
  • messageContent - The content and metadata of the sent message, including urgency, mentions, quotes, and attachments.

Dependencies

  • Zalo API credentials with cookie-based authentication

Troubleshooting

  • Ensure the Zalo API credentials are correctly set with a valid cookie, IMEI, and user agent, as the node requires these to initialize the API client.
  • If the message sending fails, check the error message for details such as invalid thread ID, missing required fields, or API initialization failure.
  • Attachments require valid public URLs; ensure the URLs are accessible and the images can be downloaded.
  • When quoting messages, ensure the quoted message data is correctly provided or auto-detected from the previous node's output.

Discussion