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 specific User Id. It optionally supports including a personalized message with the friend request. This is useful in scenarios where you want to programmatically connect with users by their unique identifiers, such as automating outreach campaigns, onboarding new contacts, or integrating Zalo social features into your workflows.
Practical examples:
- Automatically send friend requests to new leads identified by their Zalo User Ids.
- Include a custom greeting message when sending friend requests to personalize communication.
- Use in customer support automation to connect with customers on Zalo.
Properties
| Name | Meaning |
|---|---|
| User Id | The unique identifier of the Zalo user to whom the friend request will be sent. |
| Message | Optional text 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 and any relevant metadata returned by the Zalo API. The output does not include binary data.
Dependencies
- Requires an active connection to the Zalo API with appropriate authentication (e.g., an API key or token).
- The node depends on internal methods to handle HTTP requests to Zalo's service endpoints.
- Proper configuration of credentials and permissions within n8n is necessary for successful execution.
Troubleshooting
Common issues:
- Invalid or missing User Id: Ensure the User Id provided is correct and corresponds to an existing Zalo user.
- Authentication errors: Verify that the API credentials are valid and have permission to send friend requests.
- Network or API downtime: Check connectivity and Zalo API status if requests fail unexpectedly.
Error messages:
- Errors related to missing required parameters (User Id) indicate input validation failures.
- API response errors may include rate limiting or permission denied messages; consult Zalo API documentation for resolution.
- Unexpected exceptions during execution are logged internally; reviewing node execution logs can help diagnose issues.
Links and References
Note: This summary is based solely on static analysis of the provided source code and property definitions without runtime execution or access to external resources.