Overview
This node sends messages via the Zalo API using a connection authenticated by a cookie. It is useful for automating message sending to Zalo users or groups, supporting features like message quoting, mentions, urgency levels, and attachments. Practical applications include customer support automation, marketing campaigns, or internal team notifications on Zalo.
Use Case Examples
- Sending a text message to a specific user thread with normal urgency.
- Sending an urgent message to a group with quoted content and user mentions.
- Sending a message with one or more image attachments via public URLs.
Properties
| Name | Meaning |
|---|---|
| Thread ID | The ID of the Zalo thread to which the message will be sent. |
| Type | The type of the 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 sent message, such as message ID, sender ID, and content. |
| Mentions | Details of users mentioned in the message, including user ID, position, and length of the mention. |
| Attachments | One or more image or file attachments to include in the message, specified by public URLs. |
Output
JSON
success- Indicates if the message was sent successfully (true or false).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 recipient (user or group).messageContent- The content and metadata of the sent message, including text, urgency, quotes, mentions, and attachments.
Dependencies
- Zalo API accessed via an API key credential with cookie, IMEI, and user agent for authentication.
Troubleshooting
- Common issues include failure to initialize the Zalo API due to invalid or expired credentials (cookie, IMEI, or user agent).
- Errors sending messages may occur if the thread ID is invalid or the API rejects the message content or attachments.
- If sending typing events fails, it logs an error but continues sending the message.
- To resolve credential issues, verify and refresh the cookie and related authentication details.
- Ensure that attachment URLs are publicly accessible and valid to avoid upload errors.