Zalo User Interact

Overview

This node operation "Send Friend Request With User Id" for the resource "Friend" allows users to send a friend request on the Zalo platform by specifying the target user's ID. It optionally supports sending a personalized message along with the friend request.

Common scenarios where this node is beneficial include automating social interactions, growing a contact list programmatically, or integrating Zalo friend requests into broader workflows such as CRM systems or marketing automation pipelines.

Practical example:

• Automatically send friend requests to new leads imported from a database, including a custom greeting message to increase acceptance rates.

Properties

Output

The node outputs an array of JSON objects corresponding to each input item processed. Each object contains at least:

• A boolean field indicating success or failure of the friend request.
• Additional metadata or error information if the request failed.

If binary data is output (not evident in this operation), it would represent any files or media associated with the request, but this operation primarily deals with JSON responses.

Dependencies

• Requires an API key credential for authenticating with the Zalo platform.
• Depends on the Zalo API endpoint that handles sending friend requests by user ID.
• The node uses internal HTTP request libraries and possibly file system access for attachments (though not relevant here).
• Proper configuration of authentication credentials in n8n is necessary.

Troubleshooting

Common Issues

• Invalid User Id: If the provided User Id does not exist or is malformed, the API will reject the request.
• Authentication Failure: Missing or invalid API credentials will cause authorization errors.
• Rate Limiting: Sending too many friend requests in a short time may trigger rate limits.
• Message Length: Exceeding allowed message length might cause the request to fail.

Error Messages and Resolutions

• "User not found": Verify the User Id is correct and the user exists on Zalo.
• "Unauthorized" or "Invalid token": Check that the API key credential is correctly set up and valid.
• "Too many requests": Implement delays or retries to respect API rate limits.
• "Message too long": Shorten the message content to comply with API restrictions.

Links and References

• Zalo Official API Documentation (generic link, replace with actual if available)
• n8n documentation on Creating Custom Nodes
• Best practices for handling API rate limits in automation workflows.

Note: This summary is based solely on static analysis of the provided source code and property definitions without runtime execution or dynamic import resolution.