Actions22
- Get Actions
- Message Actions
- Friend Actions
- Group Actions
- Tool Actions
Overview
This node operation "Accept Friend Request" for the resource "Friend" is designed to accept incoming friend requests on the Zalo platform. It allows users to programmatically confirm and establish a friendship connection with another Zalo user by specifying their User Id.
Typical use cases include automating social interactions, managing contacts in bulk, or integrating Zalo friend management into broader workflows such as CRM systems or marketing automation platforms.
For example, a business could automatically accept friend requests from customers who have interacted with their campaigns, enabling seamless communication and engagement.
Properties
| Name | Meaning |
|---|---|
| User Id | The unique identifier of the Zalo user whose friend request you want to accept. Required. |
Output
The node outputs JSON data representing the result of the friend request acceptance operation. This typically includes confirmation details such as success status, any returned metadata about the new friend connection, or error information if the operation failed.
No binary data output is indicated.
Dependencies
- Requires an active connection to the Zalo API.
- Needs appropriate API authentication credentials (e.g., an API key or token) configured in n8n to authorize requests.
- The node depends on internal SDK or HTTP request handling to communicate with Zalo's friend management endpoints.
Troubleshooting
Common Issues:
- Invalid or missing User Id: Ensure the User Id provided corresponds to a valid Zalo user who has sent a friend request.
- Authentication errors: Verify that the API credentials are correctly set up and have sufficient permissions.
- Network or API downtime: Check connectivity and Zalo service status.
Error Messages:
- Errors related to authorization failure usually indicate invalid or expired credentials.
- Errors indicating the user does not exist or no pending friend request may mean the User Id is incorrect or the request was already handled.
- Unexpected server errors should be retried later or reported to Zalo support.
Links and References
Note: The analysis is based solely on static code inspection and provided property definitions. Internal credential names and implementation details are abstracted per guidelines.