Zalo User icon

Zalo User

Quản lý người dùng Zalo

Actions9

Overview

This node manages Zalo user interactions, specifically allowing you to send friend requests on the Zalo platform. It is useful in scenarios where you want to automate social engagement or grow your network by programmatically sending friend invitations with personalized messages.

For example, a marketing automation workflow could use this node to send friend requests to a list of potential customers, including a custom message introducing the brand or product.

Properties

Name Meaning
User ID The unique identifier of the Zalo user to whom you want to send the friend request.
Message The accompanying message that will be sent along with the friend request invitation.

Output

The node outputs JSON data containing:

  • status: A string indicating the success status of the operation (e.g., "success").
  • response: The detailed response from the Zalo API regarding the friend request action.

Each output item corresponds to an input item and includes the paired item index for traceability.

No binary data output is produced by this node.

Dependencies

  • Requires valid Zalo API credentials, including authentication cookies, device IMEI, and user agent strings.
  • The node internally uses a Zalo API client library to perform login and send friend requests.
  • Proper configuration of these credentials within n8n is necessary for successful execution.

Troubleshooting

  • Common Issues:

    • Invalid or expired authentication credentials may cause login failures.
    • Incorrect User ID format or non-existent users will result in errors when sending friend requests.
    • Network connectivity issues can prevent communication with the Zalo API.

  • Error Messages:

    • "Login failed": Indicates inability to authenticate with Zalo using provided credentials. Verify and refresh credentials.
    • Errors related to invalid parameters typically mean required fields like User ID or Message are missing or malformed.
    • API rate limits or restrictions might cause temporary failures; consider adding retry logic or delays.

  • Resolution Tips:

    • Ensure all required properties are correctly set.
    • Confirm that the API credentials are up-to-date and have necessary permissions.
    • Check network access and firewall settings.
    • Enable error handling in the workflow to capture and manage exceptions gracefully.

Links and References

Discussion