Actions3
Overview
This node integrates with the Growth-x platform to send a direct message to a LinkedIn receiver on behalf of a specified user. It is useful in scenarios where automated personalized outreach or communication is needed, such as sales prospecting, recruitment, or networking campaigns. For example, a sales team member can use this node to send tailored messages to potential clients identified by their LinkedIn usernames, streamlining outreach efforts without manual intervention.
Properties
| Name | Meaning |
|---|---|
| User Email | Email of the user sending the message. This selects which Growth-x user account sends the message. Options are dynamically loaded from available users. |
| Receiver Username | LinkedIn username of the receiver who will receive the message. |
| Message | The content of the message to be sent to the receiver. |
Output
The node outputs JSON data representing the response from the Growth-x API after attempting to send the message. This typically includes status information about the message delivery. The node does not output binary data.
Dependencies
- Requires an API key credential for authenticating with the Growth-x API.
- The node makes HTTP POST requests to the endpoint
/public/api/actions/send_message_to_receiveron the Growth-x API base URLhttps://api.growth-x.com. - The "User Email" property options are dynamically loaded via a GET request to
/public/api/users. - Proper configuration of the Growth-x API credentials within n8n is necessary.
Troubleshooting
- Common issues:
- Invalid or missing API credentials will cause authentication failures.
- Providing an incorrect or non-existent LinkedIn username may result in errors or failed message delivery.
- Network connectivity problems can prevent the node from reaching the Growth-x API.
- Error messages:
- Authentication errors typically indicate invalid or expired API keys; verify and update credentials.
- Validation errors may occur if required fields (user email, receiver username, message) are empty or malformed; ensure all required inputs are correctly provided.
- API rate limits or service downtime could cause temporary failures; retry after some time or check Growth-x service status.
Links and References
- Growth-x API Documentation (assumed public documentation for reference)
- LinkedIn Help Center for understanding LinkedIn usernames and profiles