Zalo Send Message
AI-generatedOverview
This node sends messages via the Zalo API using a login authenticated by a cookie. It supports sending messages to individual users or groups, with options for message urgency, quoting previous messages, mentioning users, and attaching images via URLs. It is useful for automating communication on the Zalo platform, such as sending notifications, alerts, or conversational messages programmatically.
Use Case Examples
- Sending a text message to a specific user thread with normal urgency.
- Sending an urgent message to a group thread with quoted content from a previous message.
- Sending a message with user mentions and multiple image attachments to a group.
Properties
| Name | Meaning |
|---|---|
| Thread ID | The ID of the thread to which the message will be sent. |
| Type | The type of message recipient, either a user or a group. |
| Message | The content of the message to be sent. |
| Urgency | The urgency level of the message, affecting how it is marked or prioritized. |
| Quote Message | Optional quoted message details to include in the message, referencing a previous message. |
| Mentions | Details of users mentioned in the message, including their ID and position in the message text. |
| Attachments | One or more image attachments to include in the message, specified by public URLs. |
Output
JSON
success- Indicates if the message was sent successfully.response- The response object returned from the Zalo API after sending the message.threadId- The ID of the thread to which the message was sent.threadType- The type of the thread (user or group).messageContent- The content and metadata of the sent message, including text, urgency, quotes, mentions, and attachments.
Dependencies
- Zalo API accessed via a cookie-based login, requiring credentials including a license code, cookie, IMEI, and user agent string.
Troubleshooting
- Common issues include failure to initialize the Zalo API due to invalid or expired credentials, resulting in login errors.
- Errors sending messages may occur if the thread ID is invalid or the API rejects the message content or attachments.
- Attachment download failures can happen if the provided image URLs are invalid or inaccessible.
- If the node is set to continue on fail, errors will be reported in the output JSON; otherwise, execution will stop with an error.