Actions27
- Standard Actions
- Sales Navigator Actions
- Other Actions
Overview
The "Send Message in Sales Navigator" operation of the Linked API node allows users to send a direct message to a LinkedIn user via their Sales Navigator account. This is useful for automating outreach, follow-ups, or personalized communication with LinkedIn contacts identified by their public or hashed LinkedIn profile URLs.
Typical use cases include:
- Sending personalized connection requests or messages to prospects.
- Automating follow-up messages after initial contact.
- Integrating LinkedIn messaging into broader marketing or sales workflows.
For example, a sales team could automatically send a customized introduction message to new leads identified through LinkedIn Sales Navigator, streamlining their outreach process.
Properties
| Name | Meaning |
|---|---|
| Webhook URL | The URL where the response from the message sending operation will be sent via webhook. |
| Person URL | The public or hashed LinkedIn profile URL of the person to whom the message will be sent. |
| Subject | The subject line of the message, limited to 80 characters. |
| Message Text | The body text of the message, limited to 1900 characters. |
Output
The node outputs JSON data containing the result of the send message operation. This typically includes confirmation of message delivery status or any error information returned by the LinkedIn Sales Navigator API.
No binary data output is involved in this operation.
Dependencies
- Requires an active LinkedIn Sales Navigator account linked via an API key credential configured in n8n.
- Needs a valid webhook URL to receive asynchronous responses.
- The node sends requests to the external API endpoint at
https://api.linkedapi.io/automation/execute.
Troubleshooting
- Invalid Person URL: If the provided LinkedIn URL is incorrect or not accessible, the message will fail to send. Verify the URL format and ensure it corresponds to a valid LinkedIn profile.
- Message Length Limits: Exceeding the character limits for subject (80 chars) or message text (1900 chars) may cause errors. Keep inputs within these constraints.
- Webhook Issues: If the webhook URL is unreachable or misconfigured, the node might not receive the response properly. Ensure the webhook URL is publicly accessible and correctly set up in n8n.
- Authentication Failures: Missing or invalid API credentials will prevent the node from executing. Confirm that the required API authentication token is correctly configured.
- API Rate Limits: Frequent message sending might hit LinkedIn API rate limits, resulting in temporary failures. Implement retry logic or pacing as needed.