Actions25
- Get Actions
- Message Actions
- Friend Actions
- Group Actions
- Tool Actions
Overview
This node implements the "Undo Friend Request" operation for the "Friend" resource in a Zalo integration. It allows users to cancel or retract a previously sent friend request on the Zalo platform.
Typical use cases include:
- Automatically withdrawing friend requests that have not been accepted within a certain timeframe.
- Providing users with the ability to undo accidental friend requests.
- Managing social connections programmatically by cleaning up pending requests.
For example, if you sent a friend request to a user but changed your mind, this node can be used to undo that request by specifying the target user's ID.
Properties
| Name | Meaning |
|---|---|
| User Id | The unique identifier of the Zalo user to whom the friend request was sent and should be undone. |
Output
The node outputs an array of JSON objects corresponding to each input item processed. Each object contains the result of the undo friend request operation for the specified user ID.
The exact structure of the output JSON is not explicitly detailed in the source code due to obfuscation, but it typically includes:
- A success flag indicating whether the undo operation succeeded.
- Possibly error information if the operation failed.
- Any relevant metadata returned from the Zalo API about the undo action.
No binary data output is indicated.
Dependencies
- Requires an active connection to the Zalo API, authenticated via an API key or token credential configured in n8n.
- Uses internal helper libraries for HTTP requests and response handling (not explicitly named).
- No additional external services beyond Zalo are required.
Troubleshooting
Common Issues
- Invalid User Id: If the provided User Id does not correspond to a valid Zalo user or no friend request exists, the operation may fail.
- Authentication Errors: Missing or invalid API credentials will cause authentication failures.
- Network Issues: Connectivity problems with the Zalo API endpoint can lead to timeouts or errors.
- Rate Limits: Excessive undo requests might trigger rate limiting by Zalo.
Error Messages and Resolutions
- "Unauthorized" or "Authentication Failed": Verify that the API key/token credential is correctly set up and has necessary permissions.
- "User Not Found" or similar: Confirm the User Id is correct and that a friend request was actually sent to that user.
- Timeouts or Network Errors: Check network connectivity and retry later.
- Unexpected Errors: Review the error details in the node's execution logs; ensure all required parameters are provided.
Links and References
- Zalo Official API Documentation (general reference for friend-related operations)
- n8n Documentation on Creating Custom Nodes
- n8n Community Forums for troubleshooting and examples
Note: The source code is heavily obfuscated, so the above summary is based on static analysis of the available property definitions and typical patterns for such nodes.