Actions27
- Standard Actions
- Sales Navigator Actions
- Other Actions
Overview
The "Withdraw Connection Request" operation in the Linked API node allows users to cancel a previously sent LinkedIn connection request. This is useful when you want to retract a pending invitation before it is accepted or declined by the recipient. Additionally, there is an option to unfollow the person when withdrawing the request, which helps manage your LinkedIn network and feed preferences simultaneously.
Practical examples:
- You sent a connection request by mistake and want to withdraw it.
- You want to clean up pending requests that have not been responded to after some time.
- You wish to unfollow a user while also withdrawing the connection request to avoid seeing their updates.
Properties
| Name | Meaning |
|---|---|
| Webhook URL | URL where the response will be sent via webhook after the operation completes. |
| Person URL | Public or hashed LinkedIn profile URL of the person whose connection request you want to withdraw. |
| Unfollow | Boolean option to decide whether to unfollow the person when withdrawing the connection request. Defaults to true. |
Output
The node outputs JSON data containing the result of the withdraw connection request operation. The exact structure depends on the API response but typically includes confirmation of the withdrawal status and any relevant metadata.
No binary data output is indicated for this operation.
Dependencies
- Requires an active API key credential for authenticating with the Linked API service.
- The node sends POST requests to
https://api.linkedapi.io/automation/executewith JSON payloads. - A valid webhook URL must be provided to receive asynchronous responses from the API.
Troubleshooting
- Invalid Person URL: If the provided LinkedIn URL is incorrect or malformed, the API may return an error. Ensure the URL is accurate and publicly accessible or properly hashed.
- Webhook URL Issues: If the webhook URL is unreachable or misconfigured, the node might fail to receive the response. Verify the webhook endpoint is correctly set up and publicly accessible.
- Authentication Errors: Missing or invalid API credentials will cause authentication failures. Confirm that the API key credential is configured correctly in n8n.
- Network or API Downtime: Temporary connectivity issues or API service downtime can cause errors. Retry after some time or check the API status.
Links and References
- LinkedIn Help - Withdraw a Connection Request
- Linked API Documentation (if available) (Assumed based on base URL)