Actions22
- 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 social or messaging platform context (specifically Zalo, as indicated by the property description). The node allows users to cancel or retract a previously sent friend request to another user identified by their User ID.
Common scenarios where this node is beneficial include:
- Automatically managing friend requests in workflows, such as retracting requests after a certain time if not accepted.
- Cleaning up pending friend requests in bulk.
- Integrating with other automation processes that require undoing friend requests based on specific conditions.
Practical example:
- A workflow sends friend requests to multiple users and later decides to undo some of them based on responses or other criteria. This node can be used to programmatically undo those requests by specifying the target User 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, but typically it would include:
- A success indicator or status.
- Possibly error messages if the undo operation failed.
- Any relevant metadata returned from the API call.
No binary data output is indicated or handled by this node.
Dependencies
- Requires an API key credential or authentication token configured in n8n to access the Zalo API.
- Depends on the Zalo platform's API endpoint for undoing friend requests.
- The node internally uses HTTP requests to communicate with the external service.
- No additional external libraries beyond standard n8n dependencies are required.
Troubleshooting
Common Issues
- Invalid or missing User Id: The node requires a valid User Id to identify which friend request to undo. Ensure the User Id is correctly provided.
- Authentication errors: If the API key or authentication token is invalid or expired, the node will fail to perform the operation.
- API rate limits: Excessive calls to the Zalo API may trigger rate limiting, causing failures.
- Network issues: Connectivity problems can prevent successful API communication.
Common Error Messages
- Unauthorized / Authentication failed: Check that the API credentials are correctly set up and have the necessary permissions.
- User not found or invalid User Id: Verify the User Id is correct and corresponds to a valid user.
- Operation failed due to server error: Retry after some time or check the Zalo API status.
Resolution Steps
- Double-check the User Id input.
- Verify and refresh API credentials.
- Monitor API usage to avoid hitting rate limits.
- Ensure stable network connectivity.
Links and References
- Zalo Official API Documentation (general reference for API endpoints)
- n8n documentation on Creating Custom Nodes
- n8n community forums for troubleshooting and examples.
Note: The above summary is based solely on static analysis of the provided source code and property definitions without runtime execution.