Actions33
- Lead Actions
- Campaign Actions
- Inbox Actions
- LinkedIn Account Actions
- List Actions
- My Network Actions
- Stat Actions
- Webhook Actions
Overview
The node integrates with the HeyReach API to send messages within LinkedIn conversations. Specifically, the "Inbox" resource with the "Send Message" operation allows users to send a message to a specified LinkedIn conversation using a designated LinkedIn account.
This node is useful in scenarios such as automating outreach campaigns, managing LinkedIn communications at scale, or integrating LinkedIn messaging into broader workflows like CRM updates or lead nurturing.
For example, a user can automate sending personalized follow-up messages to prospects after an event or trigger messages based on external events like form submissions.
Properties
| Name | Meaning |
|---|---|
| Message | The content/body of the message to be sent. |
| Subject | The subject of the message. |
| Conversation ID | The unique identifier of the LinkedIn conversation to which the message will be sent. |
| LinkedIn Account ID | The LinkedIn account ID that will be used to send the message. |
Output
The node outputs JSON data representing the response from the HeyReach API after attempting to send the message. This typically includes details about the sent message, such as confirmation of delivery, message ID, timestamps, or any error information if the send failed.
There is no indication that this node outputs binary data.
Dependencies
- Requires an active HeyReach API key credential configured in n8n.
- The node communicates with the HeyReach API endpoint at
https://api.heyreach.io/api/n8n. - The LinkedIn account ID must correspond to a valid LinkedIn account authorized within HeyReach.
- The conversation ID must reference an existing LinkedIn conversation accessible by the specified LinkedIn account.
Troubleshooting
- Invalid Conversation ID: If the conversation ID does not exist or is inaccessible, the API may return an error indicating the conversation was not found. Verify the conversation ID is correct and belongs to the LinkedIn account used.
- Authentication Errors: Missing or invalid API credentials will cause authentication failures. Ensure the HeyReach API key is correctly set up in n8n credentials.
- Permission Issues: The LinkedIn account ID must have permission to send messages in the target conversation. Lack of permissions may result in errors.
- Empty Message or Subject: Both fields are required; leaving them empty will likely cause validation errors.
- API Rate Limits: Sending too many messages in a short time might trigger rate limiting by HeyReach or LinkedIn.
Links and References
- HeyReach API Documentation (general reference for API capabilities)
- LinkedIn Messaging Best Practices (for crafting effective messages)