Actions22
- Get Actions
- Message Actions
- Friend Actions
- Group Actions
- Tool Actions
Overview
This node operation allows sending a friend request on the Zalo platform using a phone number. It is useful when you want to programmatically add someone as a friend on Zalo by specifying their phone number, optionally including a personalized message with the request.
Common scenarios include:
- Automating outreach or networking campaigns where you have users' phone numbers.
- Integrating Zalo friend requests into CRM or marketing workflows.
- Sending friend requests in bulk based on phone number lists.
Example:
You have a list of phone numbers collected from a signup form and want to send each user a friend request on Zalo with a welcome message.
Properties
| Name | Meaning |
|---|---|
| Phone Number | The phone number of the Zalo user to whom you want to send the friend request. |
| Message | Optional text message to include with the friend request. |
Output
The node outputs an array of JSON objects, each representing the result of sending a friend request for one input item. Each object contains at least a boolean success field indicating if the request was sent successfully, and may include additional details such as error messages if the request failed.
If the node supports binary data output (not explicitly shown), it would typically represent attachments or media related to the friend request, but this operation primarily deals with JSON responses.
Dependencies
- Requires access to the Zalo API, authenticated via an API key or token credential configured in n8n.
- Uses internal helper libraries for HTTP requests and file system operations.
- May require environment variables or credentials set up in n8n for authentication with Zalo.
Troubleshooting
- Invalid Phone Number: If the phone number format is incorrect or the user does not exist on Zalo, the API will reject the request. Ensure phone numbers are valid and formatted correctly.
- Authentication Errors: Missing or invalid API credentials will cause authorization failures. Verify that the API key/token is correctly configured.
- Rate Limits: Sending too many friend requests in a short time may trigger rate limiting by Zalo. Implement delays or batch processing to avoid this.
- Error Messages: The node logs errors with detailed messages. Common errors include network issues, invalid parameters, or server errors. Review the error output for troubleshooting.
Links and References
- Zalo Official API Documentation (general reference for API capabilities)
- n8n documentation on Creating Custom Nodes
- Best practices for Handling API Rate Limits
Note: Internal variable names, credential types, and obfuscated code details have been omitted to comply with guidelines.