Actions25
- Message Actions
- Friend Actions
- Get 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 by specifying their phone number, optionally including a personalized message with the request.
Common scenarios include:
- Automating social network growth by adding contacts from a phone list.
- Integrating Zalo friend requests into CRM or marketing workflows.
- Sending customized friend requests with messages for better engagement.
Example use case:
- You have a list of phone numbers collected from an event and want to send friend requests to all attendees 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 JSON data representing the result of the friend request operation. This typically includes success status and any response details from the Zalo API.
If the node supports binary data output (e.g., attachments), it would be summarized here, but this operation focuses on JSON responses related to friend requests.
Dependencies
- Requires an active connection to the Zalo API with appropriate authentication credentials (an API key or token).
- The node depends on internal SDK or HTTP client libraries to communicate with Zalo's service.
- Proper configuration of API credentials in n8n is necessary for successful execution.
Troubleshooting
- Invalid Phone Number: If the phone number format is incorrect or the user does not exist on Zalo, the request will fail. Ensure the phone number is valid and registered on Zalo.
- Authentication Errors: Missing or invalid API credentials will cause authorization failures. Verify that the API key/token is correctly set up in n8n.
- Rate Limits: Sending too many requests in a short time may trigger rate limiting by Zalo. Implement delays or batch processing to avoid this.
- Network Issues: Connectivity problems can cause request failures. Check your network and proxy settings if applicable.
- Error Messages: The node logs error details in its output. Review these messages for specific API errors or exceptions to guide resolution.
Links and References
Note: Internal credential names and implementation details are omitted to comply with best practices.