Actions12
Overview
This node manages Zalo user interactions, specifically for the "Zalo User" resource. The operation "Chấp Nhận Lời Mời Kết Bạn" (Accept Friend Request) allows you to accept incoming friend requests on behalf of a Zalo user. This is useful in automating social interactions, managing contacts, or integrating Zalo user management into workflows.
For example, you can use this node to automatically accept friend requests from certain users or as part of a larger automation that handles new connections on Zalo.
Properties
| Name | Meaning |
|---|---|
| User ID | The ID of the user whose friend request you want to accept |
Output
The output JSON contains two main fields:
status: A string indicating the result of the operation, typically"Thành công"which means "Success".response: The raw response data returned by the Zalo API after accepting the friend request. This may include details about the accepted request or confirmation status.
Example output structure:
{
"status": "Thành công",
"response": {
// API response details here
}
}
No binary data output is produced by this operation.
Dependencies
- Requires an API key credential to authenticate with the Zalo API.
- The node uses stored credentials including cookie, IMEI, and user agent strings to establish a session with Zalo.
- The external library
zca-jsis used internally to interact with the Zalo API.
Troubleshooting
- Invalid Credentials: If the node cannot create an API instance, it will throw an error indicating no API instance was found. Ensure your Zalo API credentials are valid and contain the necessary authentication tokens.
- User ID Errors: Providing an incorrect or non-existent User ID will likely cause the API call to fail. Verify the User ID before running the node.
- API Rate Limits or Restrictions: The Zalo API might impose limits or restrictions; if errors occur, check your API usage and permissions.
- Continue On Fail: If enabled, the node will continue processing other items even if one fails, returning error messages in the output JSON under the
errorfield.