Actions17
- Get Actions
- Message Actions
- Friend Actions
- Group Actions
Overview
This n8n custom node implements the "Send Friend Request With User Id" operation for the "Friend" resource, likely targeting the Zalo social platform. The node allows users to send a friend request to another user by specifying their Zalo User ID and an optional message. This is useful in automation scenarios where you want to programmatically connect with new contacts on Zalo, such as onboarding workflows, CRM integrations, or automated networking tasks.
Example use cases:
- Automatically sending a friend request to a new lead captured from a web form.
- Integrating Zalo contact management into a broader customer engagement workflow.
- Triggering friend requests based on events in other systems (e.g., after a successful purchase).
Properties
The following input properties are supported for this operation:
| Display Name | Type | Required | Description |
|---|---|---|---|
| User Id | String | Yes | ID của Zalo User để lấy thông tin. (Zalo User ID to whom the friend request will be sent.) |
| Message | String | No | Nội dung tin nhắn. (Optional message content to include with the friend request.) |
Output
The output of this node is a JSON object for each processed item. The structure typically includes:
{
"success": true,
"data": { /* API response data */ }
}
- If the friend request is sent successfully,
successwill betrue, anddatawill contain details returned by the Zalo API. - In case of failure, the output may look like:
{
"success": false,
"error": "Error message",
"stack": "Stack trace (if available)"
}
- The node does not output binary data for this operation.
Dependencies
- External Service: Requires access to the Zalo API.
- API Key/Token: You must configure authentication credentials for the Zalo API within n8n.
- n8n Configuration: Ensure that any required environment variables or credentials for Zalo are set up in your n8n instance.
Troubleshooting
Common Issues:
- Invalid User Id: If the provided User Id does not exist or is incorrect, the API will return an error.
- Authentication Errors: Missing or invalid API credentials will cause authentication failures.
- Rate Limiting: Sending too many requests in a short period may trigger rate limits on the Zalo API.
- Network Issues: Connectivity problems between n8n and the Zalo API endpoint can result in timeouts or failed requests.
Error Messages:
"error": "Invalid User Id"– Check that the User Id is correct and exists on Zalo."error": "Authentication failed"– Verify your API credentials in n8n."error": "Rate limit exceeded"– Reduce the frequency of requests."error": "Network error"– Ensure n8n can reach the Zalo API servers.
Resolution Steps:
- Double-check all input fields, especially the User Id.
- Confirm that your Zalo API credentials are valid and active.
- Monitor API usage to avoid hitting rate limits.
- Review network/firewall settings if connectivity issues persist.