Zalo StickerInstall

Overview

This node interacts with the Zalo Sticker service to retrieve a list of stickers based on a given name or keyword. It is useful for workflows that need to fetch sticker data from Zalo, such as automating content creation, messaging apps integration, or managing sticker collections.

A practical example: You want to get all stickers related to a specific theme or keyword (e.g., "happy") to display them in your app or use them in automated messages. By providing the keyword, the node fetches matching stickers; leaving it blank retrieves all available stickers.

Properties

Output

The node outputs an array of JSON objects, each representing a sticker or a set of stickers. Each output item contains:

• success: Boolean indicating if the request was successful.
• message: A descriptive message about the operation result.
• data: The actual sticker data returned by the Zalo API. This can be an array or object depending on the query.
• count (optional): Number of stickers returned when the data is an array.
• query (optional): The search keyword used for filtering stickers.
• error (if any): Error details if the request failed.

The output is paired with the input item index for traceability.

No binary data output is produced by this node.

Dependencies

• Requires an API key credential for authenticating with the Zalo service.
• Uses internal helper classes and methods to handle cookies, user agent, and device identifiers required by the Zalo API.
• No additional external services beyond Zalo's API are needed.
• Ensure proper configuration of the API authentication token in n8n credentials.

Troubleshooting

• Common issues:

  • Invalid or missing API authentication token will cause authentication failures.
  • Network connectivity problems may prevent access to the Zalo API.
  • Providing an invalid or malformed sticker name might return empty results.

• Error messages:

  • If the node cannot initialize the Zalo API client due to missing cookies or device info, it throws an error indicating failure to create the client.
  • API errors from Zalo are passed through in the error field of the output JSON.

• Resolutions:

  • Verify that the API key credential is correctly set up and has necessary permissions.
  • Check network connectivity and firewall settings.
  • Use valid sticker names or leave the field empty to get all stickers.

Links and References

• Zalo Official Developer Documentation (for API details)
• n8n documentation on Creating Custom Nodes