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 by their phone number rather than by user ID or other identifiers. This can be particularly beneficial for automating social interactions, onboarding new contacts, or integrating Zalo friend requests into broader workflows such as CRM systems or marketing automation.
Practical examples:
- Automatically send friend requests to new customers whose phone numbers are collected via a web form.
- Add users to your Zalo friend list based on phone numbers from an external database.
- Integrate with customer support tools to connect with clients on Zalo by sending them friend requests.
Properties
| Name | Meaning |
|---|---|
| Phone Number | The phone number of the Zalo user to whom the friend request will be sent. |
| Message | Optional message content to include with the friend request. |
Output
The node outputs JSON data representing the result of the friend request operation. This typically includes confirmation of the request being sent, any response data from the Zalo API, and error information if applicable.
If the node supports binary data output (not explicitly shown in the provided code), it would represent attachments or media related to the friend request or messaging features.
Dependencies
- Requires access to the Zalo API, which means the node must be configured with appropriate API credentials (e.g., an API key or authentication token).
- The node likely depends on HTTP request libraries or SDKs to communicate with Zalo's services.
- Proper network connectivity and permissions to call external APIs are necessary.
Troubleshooting
- Invalid Phone Number: If the phone number format is incorrect or the user does not exist on Zalo, the API may return an error. Ensure the phone number is valid and registered on Zalo.
- Authentication Errors: Missing or invalid API credentials will cause authentication failures. Verify that the API key or token is correctly set up in n8n credentials.
- API Rate Limits: Sending too many requests in a short time may trigger rate limiting. Implement retry logic or respect API limits.
- Message Content Issues: If the optional message contains unsupported characters or exceeds length limits, the request might fail.
- Network Issues: Connectivity problems can prevent the node from reaching the Zalo API.
Common error messages usually include HTTP status codes and descriptive messages from the Zalo API. Review these messages to identify issues and consult Zalo's API documentation for resolution steps.
Links and References
Note: The provided source code was heavily obfuscated and minified, so the above summary is based on static analysis of input properties and typical usage patterns for such operations. No internal credential names or sensitive details were included.