Zalo Tag icon

Zalo Tag

Quản lý thẻ (tag) trong Zalo
Join our community

Overview

This node is designed to interact with a service that manages labels or tags (referred to as "thẻ" in Vietnamese). The primary and currently only supported action is to list all available tags. This functionality is useful when you want to retrieve and work with the full set of tags from an external system, for example, to display them, filter data by tags, or synchronize tags with another system.

A practical example use case would be:

  • Fetching all tags from a project management or content labeling system to populate a dropdown menu in a workflow.
  • Synchronizing tag lists between two different platforms by first retrieving all tags from one system.

Properties

Name Meaning
Hành đỘng Action to perform; options: "Danh Sách Thẻ" (List all tags)

The property "Hành đỘng" (Action) lets the user select what operation to perform. Currently, the only option is to list all tags.

Output

The node outputs an array of items where each item contains a JSON object with the following structure:

  • success: A boolean indicating if the request was successful.
  • labels: An array containing the list of tags retrieved from the external service.

Example output JSON snippet:

{
  "success": true,
  "labels": [
    "tag1",
    "tag2",
    "tag3"
  ]
}

There is no indication that the node outputs binary data.

Dependencies

  • The node requires an API key credential to authenticate requests to the external service managing the tags.
  • It uses an internal client class instantiated with cookie, IMEI, and user agent information extracted from credentials or environment.
  • The node depends on asynchronous calls to this client to fetch the list of tags.
  • No explicit environment variables are mentioned, but proper configuration of the API authentication token/credential is necessary.

Troubleshooting

  • Common issues:

    • Authentication failure due to missing or invalid API key credential.
    • Network errors or timeouts when connecting to the external service.
    • Unexpected response format causing JSON parsing errors.

  • Error messages:

    • If the client instance cannot be created, the node throws an error indicating failure to initialize the connection.
    • If the action selected is not recognized, the node will not return any data.
    • Errors during the API call are caught and re-thrown with additional context.

  • Resolutions:

    • Ensure the API key credential is correctly configured and valid.
    • Verify network connectivity to the external service.
    • Check for updates or changes in the external service API that might affect compatibility.

Links and References

No external links or references are provided in the source code or properties. For further details, consult the documentation of the external service managing the tags or the n8n community forums for similar node implementations.

Discussion