Linked API icon

Linked API

Control your LinkedIn accounts and retrieve real-time data.

Actions27

Overview

The node provides an interface to send LinkedIn connection requests programmatically via the Linked API service. It allows users to specify a target LinkedIn profile URL and optionally include a personalized note or email address required by some recipients. This node is useful for automating networking outreach, lead generation, or recruitment workflows where sending connection requests at scale with customized messages is beneficial.

Practical examples:

  • Automatically send connection requests to new leads collected from a CRM.
  • Personalize connection invites with notes when reaching out to potential collaborators.
  • Include an email address if the recipient requires it for connection approval.

Properties

Name Meaning
Webhook URL URL where the response will be sent via webhook after the request is processed.
Person URL Public or hashed LinkedIn profile URL of the person to whom the connection request is sent.
Connection Note Optional personalized message included with the connection request.
Email Address Optional email address required by some people to accept connection requests.

Output

The node outputs JSON data representing the result of the connection request operation. This typically includes status information about whether the request was successfully sent or any errors encountered. The output is delivered asynchronously via the specified webhook URL.

No binary data output is involved in this operation.

Dependencies

  • Requires an active API key credential for the Linked API service.
  • Needs a valid webhook URL configured to receive asynchronous responses.
  • The node sends POST requests to https://api.linkedapi.io/automation/execute with appropriate payloads.

Troubleshooting

  • Invalid Person URL: If the provided LinkedIn URL is malformed or inaccessible, the request may fail. Verify the URL format and accessibility.
  • Missing Webhook URL: The webhook URL is mandatory; omitting it will cause the node to error out.
  • Email Required but Missing: Some recipients require an email address to accept connection requests. If omitted when needed, the request might be rejected.
  • API Authentication Errors: Ensure the API key credential is valid and has necessary permissions.
  • Webhook Delivery Failures: If the webhook endpoint is down or misconfigured, the node will not receive confirmation of request processing.

Links and References

Discussion