Zalo Tag
AI-generatedOverview
This node, named "Zalo Tag," is designed to manage tags within the Zalo platform. It currently supports listing all tags associated with a Zalo account. This functionality is useful for users who want to retrieve and work with their existing tags in Zalo, such as for organizing contacts or messages by categories.
A practical example would be a marketing automation workflow where you need to fetch all available tags from Zalo to dynamically assign them to contacts or segment audiences based on those tags.
Properties
| Name | Meaning |
|---|---|
| Hành đỘng | Action to perform; options: "Danh Sách Thẻ" (List all tags) |
Output
The node outputs an array of JSON objects, each containing:
success: A boolean indicating if the operation was successful (true).labels: An array representing the list of tags retrieved from Zalo.
Example output JSON structure:
{
"success": true,
"labels": [
{
"id": "tag_id_1",
"name": "Tag Name 1"
},
{
"id": "tag_id_2",
"name": "Tag Name 2"
}
// ... more tags
]
}
No binary data output is produced by this node.
Dependencies
- Requires an API key credential to connect to the Zalo platform.
- Uses the Zalo API client library internally to authenticate and fetch tag data.
- The credential must include a valid cookie, device IMEI, and user agent string for authentication.
- Proper configuration of these credentials in n8n is necessary for the node to function.
Troubleshooting
- Login Initialization Failure: If the node cannot initialize the Zalo API client, it throws an error indicating failure to start the API and suggests checking login information. This usually means the provided credentials are invalid or expired.
- Login Error Message: Errors during login will include the message "Lỗi đăng nhập Zalo" followed by the specific error details. Users should verify that the cookie, IMEI, and user agent values are correct and up to date.
- Empty or Missing Tags: If no tags are returned, ensure that the connected Zalo account actually has tags created.
- Credential Issues: Make sure the API key credential is properly set up in n8n with all required fields filled.