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

AI-generated

Overview

This node sends styled text messages to a specified thread, which can be either a user or a group. It supports rich text formatting within the message content, allowing users to emphasize parts of their message using bold, italic, underline, strikethrough, colored text, and custom font sizes. Additionally, it supports sending multiple image attachments alongside the message.

Common scenarios for this node include:

  • Sending notifications or alerts with different urgency levels to individual users or groups.
  • Dispatching formatted announcements or updates where text styling improves readability and emphasis.
  • Sharing images or files along with textual information in chat threads.

Practical example:

  • A team lead sends an urgent, bolded message with red-colored text to a project group, attaching screenshots relevant to the update.

Properties

Name Meaning
Thread ID The identifier of the thread (chat) where the message will be sent. This is required.
Type The type of the message recipient: either a single user (User) or a group chat (Group).
Message The content of the message supporting style formatting tags such as [b]bold[/b], [i]italic[/i], [u]underline[/u], [s]strikethrough[/s], [c:red]colored text[/c], and [f:20]font size[/f]. Colors supported are red, orange, yellow, green. Multiple styles can be combined.
Urgency The urgency level of the message: Default, Important, or Urgent. This may affect how the message is handled or displayed on the receiving end.
Debug Mode Boolean flag to enable debug mode, which outputs detailed logs about the message processing steps. Useful for troubleshooting.
Attachments One or more image attachments to send with the message. Each attachment requires specifying the type (currently only "Image URL/File URL") and the public URL of the image or file.

Output

The node outputs JSON data containing the result of the message sending operation. The output includes:

  • success: Boolean indicating if the message was sent successfully.
  • response: The raw response from the underlying messaging service.
  • threadId: The ID of the thread where the message was sent.
  • threadType: The type of the thread (user or group).
  • messageContent: The processed message content including any parsed styles.
  • attachments (if any): Information about attachments sent.
  • debugInfo (if debug mode enabled): Detailed logs of the message processing.

No binary data output is produced by this node.

Dependencies

  • Requires an API key credential or similar authentication token configured in n8n to access the messaging service.
  • Uses an external messaging client library instantiated with session cookies, device IMEI, and user agent strings retrieved from credentials.
  • Supports sending messages via this client, which handles the actual communication with the messaging platform.

Troubleshooting

  • Common issues:

    • Invalid or missing thread ID will cause the message sending to fail.
    • Incorrect or expired authentication credentials will prevent connection to the messaging service.
    • Malformed message content or unsupported style tags might not render correctly.
    • Attachment URLs must be publicly accessible; otherwise, attachments won't be delivered.

  • Error messages:

    • Errors related to missing or invalid credentials suggest checking the API key or session details.
    • Connection errors indicate network issues or incorrect service endpoint configuration.
    • Debug mode provides detailed console logs that help identify at which step the failure occurs.

  • Resolution tips:

    • Verify all required properties are set correctly.
    • Ensure the API key or authentication token is valid and has necessary permissions.
    • Confirm attachment URLs are reachable without authentication.
    • Enable debug mode to get verbose output for diagnosing problems.

Links and References

  • n8n Documentation
  • Messaging service API documentation (not provided here; refer to your messaging platform's official docs)
  • Styling syntax reference (based on supported tags: [b], [i], [u], [s], [c:<color>], [f:<size>])

Discussion