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 Send Connection Request operation under the Network resource allows users to send LinkedIn connection invitations programmatically. This is useful for automating outreach campaigns, expanding professional networks, or managing LinkedIn connections at scale without manual intervention.
Typical use cases include:
- Sending personalized LinkedIn invitations to a list of prospects.
- Automating connection requests as part of a lead generation workflow.
- Managing bulk LinkedIn networking actions within an automated pipeline.
Example: Automatically send a connection request with a custom message to a LinkedIn profile URL, optionally selecting a proxy country for the request.
Properties
| Name | Meaning |
|---|---|
| LinkedIn Profile URL (profileUrl) | The LinkedIn profile URL of the person to whom you want to send the connection request. Example: https://www.linkedin.com/in/username |
| Connection Message (connectionMessage) | A personalized message included with the connection invitation. Optional. |
| Country Code (country) | Country code used for proxy selection to route the request (e.g., FR for France, US for United States). Defaults to "FR". |
| Timeout (timeout) | Request timeout in milliseconds. Default is 30000 ms (30 seconds). |
| Retry Count (retryCount) | Number of times to retry the request on failure. Default is 3. |
Output
The node outputs JSON data containing the response from the Linkup API after attempting to send the connection request. The output includes:
- The full API response fields returned by Linkup.
- A
_debugobject with details about the request body, headers, endpoint, and raw API response for troubleshooting. - Metadata including the resource (
network), operation (sendConnectionRequest), timestamp of execution, and node version. - If an error occurs, the output JSON contains an
errorfield with the error message.
No binary data is produced by this operation.
Dependencies
- Requires an API key credential for the Linkup API to authenticate requests.
- The node uses HTTP POST requests to the Linkup API endpoint
/network/connect. - The user must configure their Linkup API credentials in n8n before using this node.
- Optionally, the country code property influences proxy routing on the Linkup side.
Troubleshooting
- Missing API Key Error: If the API key credential is not configured or invalid, the node will throw an error indicating the missing API key. Ensure your Linkup API key is set up correctly in n8n credentials.
- Invalid LinkedIn Profile URL: Providing an incorrect or malformed LinkedIn profile URL may cause the API to reject the request. Verify URLs are valid and publicly accessible.
- Timeouts: Network issues or slow responses can cause timeouts. Adjust the
Timeoutproperty if needed. - API Rate Limits or Restrictions: The Linkup API may enforce rate limits or usage restrictions. Check your Linkup account limits if requests fail repeatedly.
- Error Messages from API: The node surfaces API error messages in the output JSON's
errorfield. Review these messages for specific causes.
Links and References
- Linkup API Documentation — Official site to create an account and obtain API keys.
- LinkedIn Help Center — For understanding LinkedIn profiles and connection policies.
This summary is based solely on static analysis of the provided source code and property definitions.