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 sending a sticker message to a specified Zalo user or group chat. It is useful in scenarios where you want to enhance communication with expressive stickers rather than plain text messages, such as sending reactions, greetings, or fun interactions within automated workflows.

Practical examples include:

  • Sending a "thank you" sticker after a customer completes a form.
  • Automatically replying with a "funny" sticker in group chats based on certain triggers.
  • Enhancing chatbot responses with relevant stickers for better engagement.

Properties

Name Meaning
User/Group Id The ID of the Zalo user or group chat where the sticker message will be sent.
Thread Type Specifies whether the target is a User (0) or a Group (1).
Sticker Keywords Keywords identifying the sticker to send, e.g., "cute", "funny".

Output

The node outputs an array of JSON objects representing the results of sending the sticker message(s). Each object typically contains:

  • A success flag indicating if the message was sent successfully.
  • Details about the sent message or error information if the sending failed.

If binary data is involved (not indicated here), it would represent media content related to the message.

Dependencies

  • Requires an active connection to the Zalo messaging platform via an API key credential.
  • The node depends on internal helper libraries and possibly file system access for attachments (though not directly relevant for sending stickers).
  • Proper configuration of authentication credentials in n8n is necessary to authorize API calls.

Troubleshooting

  • Invalid User/Group ID: If the provided thread ID does not exist or is incorrect, the node will fail to send the message. Verify the ID is correct.
  • Incorrect Thread Type: Selecting the wrong thread type (User vs Group) may cause errors or unexpected behavior.
  • Sticker Keyword Not Found: If the keyword does not match any available sticker, the message will not be sent. Use valid keywords supported by Zalo.
  • Authentication Errors: Missing or invalid API credentials will prevent the node from communicating with Zalo.
  • API Rate Limits: Excessive requests might lead to throttling; ensure usage complies with Zalo's API limits.

Common error messages usually contain details about the failure reason, such as authorization failures or invalid parameters. Review these messages and adjust inputs or credentials accordingly.

Links and References


Note: Internal variable names, credential types, and obfuscated code details have been omitted to comply with guidelines.

Discussion