Actions36
- Authentication Actions
- Profile Actions
- Company Actions
- Network Actions
- Message Actions
- Post Actions
- Recruiter Actions
- Data Actions
Overview
This node integrates with the Linkup API to automate LinkedIn networking activities. Specifically, the Withdraw Invitation operation allows users to cancel a previously sent LinkedIn connection invitation. This is useful when you want to retract an invitation that was sent by mistake or if you no longer wish to connect with a particular user.
Practical scenarios include:
- Managing your LinkedIn outreach campaigns by withdrawing outdated or irrelevant invitations.
- Correcting errors in sent invitations without manually navigating LinkedIn.
- Automating cleanup of pending invitations as part of a broader LinkedIn automation workflow.
Properties
| Name | Meaning |
|---|---|
| Invitation ID | The unique identifier of the LinkedIn invitation you want to withdraw. |
| Country Code | The country code used for proxy selection (e.g., FR for France, US for United States). |
| Timeout | Request timeout duration in milliseconds (default 30000 ms). |
| Retry Count | Number of retry attempts on failure (default 3). |
These properties are grouped under "Linkup Parameters" and "Advanced Options" collections.
Output
The node outputs JSON data containing the API response from the Linkup service regarding the withdrawal request. The output includes:
_debug: Debug information including the request body sent, request headers, endpoint URL, and raw API response.- The main API response fields returned by Linkup after attempting to withdraw the invitation.
_meta: Metadata about the resource ("network"), operation ("withdrawInvitation"), timestamp of execution, and node version.pairedItem: Reference to the input item index for traceability.
No binary data is produced by this operation.
Dependencies
- Requires an API key credential for authenticating with the Linkup API.
- The node uses the Linkup API endpoint at
https://api.linkupapi.com/v1/network/withdraw-invitation. - Proper configuration of the API key and optional credentials like LinkedIn email and password may be necessary.
- The country code parameter helps select the appropriate proxy server for requests.
Troubleshooting
- Missing API Key Error: If the API key is not configured, the node throws an error indicating the missing key. Ensure the API key credential is set up correctly in n8n.
- Invalid Invitation ID: Providing an incorrect or non-existent invitation ID will likely result in an API error. Verify the invitation ID before use.
- Timeouts: Network issues or slow responses can cause timeouts. Adjust the "Timeout" property to a higher value if needed.
- Retries: If transient errors occur, increasing the "Retry Count" may help recover from temporary failures.
- Country Code Issues: Using an unsupported or incorrect country code might affect proxy routing and cause request failures. Use valid ISO country codes as suggested.
Links and References
- Linkup API Documentation — Official site to get API keys and learn more about available operations.
- LinkedIn Help Center — For understanding LinkedIn invitation management basics.