Zalo OA icon

Zalo OA

Tương tác với Zalo Official Account API

Overview

This node interacts with the Zalo Official Account (OA) API to remove a follower from a specific tag. It is useful in scenarios where you want to manage your audience segmentation dynamically by untagging users who no longer fit certain criteria or campaigns.

For example, if you have tagged followers based on their interests or engagement levels, and a follower opts out of a campaign or changes preferences, this node can be used to remove that follower from the corresponding tag automatically.

Properties

Name Meaning
User ID The unique identifier of the follower to be removed from the tag.
Tag ID The unique identifier of the tag from which the follower will be removed.

Output

The node outputs a JSON object containing the response from the Zalo OA API after attempting to remove the follower from the tag. This typically includes success status and any relevant messages or error details returned by the API.

No binary data output is produced by this operation.

Dependencies

  • Requires an API key credential for authenticating with the Zalo Official Account API.
  • The node uses the Zalo OA API v3.0 endpoint /tag/rmfollowerfromtag to perform the removal.
  • Proper permissions must be granted to the API token, specifically the permission to manage tags and followers.
  • Network access to https://openapi.zalo.me/v3.0/oa is required.

Troubleshooting

  • Common Issues:

    • Invalid or expired access token: Ensure the API key/token is valid and refreshed as needed.
    • Incorrect User ID or Tag ID: Verify that both IDs exist and are correctly formatted.
    • Insufficient permissions: Confirm that the API token has the necessary rights to modify tags and followers.
    • API rate limits: Be aware of any rate limiting imposed by Zalo OA API.
  • Error Messages:

    • Errors from the API will be included in the output JSON under an error field with descriptive messages.
    • If the API call fails, the node logs the HTTP response status and error details to help diagnose issues.
    • Suggestions are provided in error responses to check parameters and access rights.

Links and References

Discussion