Actions25
- 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 connect with someone on Zalo but only have their phone number, not their user ID. The node can optionally include a personalized message with the friend request.
Common scenarios:
- Automating outreach campaigns where you have a list of phone numbers and want to send friend requests programmatically.
- Integrating with CRM or contact management systems to invite contacts to connect on Zalo.
- Sending friend requests as part of onboarding or customer engagement workflows.
Practical example:
You have a marketing automation workflow that collects phone numbers from a web form. Using this node, you can automatically send a friend request to each submitted phone number 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 representing the result of the friend request operation for each input item. Each object typically contains:
- A success indicator (boolean) showing if the friend request was sent successfully.
- Any response data or error details returned by the Zalo API.
- Metadata about the request such as timestamps or IDs.
If the node supports binary data output (not explicitly shown here), it would represent any media or attachments related to the friend request.
Dependencies
- Requires an active connection to the Zalo API, authenticated via an API key or token credential configured in n8n.
- The node depends on the Zalo service being available and accessible.
- No other external dependencies are indicated.
Troubleshooting
Common issues:
- Invalid phone number format: Ensure the phone number is correctly formatted as expected by Zalo.
- Authentication errors: Verify that the API key or authentication token is valid and has necessary permissions.
- Rate limiting: Sending too many friend requests in a short time may trigger rate limits; implement delays or retries.
- User not found: The phone number might not be associated with a Zalo account.
Error messages:
- Errors returned from the Zalo API will be included in the output. Check the
errorandstackfields for details. - If the node fails to authenticate, it will throw an error indicating invalid credentials.
- Network or timeout errors may occur if the Zalo API is unreachable.
Resolution tips:
- Double-check input phone numbers.
- Confirm API credentials in n8n settings.
- Add error handling in your workflow to catch and log failures.
- Respect Zalo's usage policies to avoid being blocked.
Links and References
- Zalo Official Developer Documentation
- n8n Documentation - Creating Custom Nodes
- Zalo API Rate Limits and Best Practices
Note: This summary is based solely on static analysis of the provided source code and property definitions without runtime execution or access to internal credential names.