Actions27
- Standard Actions
- Sales Navigator Actions
- Other Actions
Overview
The "Linked API" node enables interaction with LinkedIn accounts to control them and retrieve real-time data. Specifically, the "Retrieve Pending Requests" operation fetches pending connection requests from a LinkedIn account. This is useful for automating the management of connection requests, such as monitoring incoming requests or integrating this data into workflows for further processing or notifications.
Practical examples include:
- Automatically retrieving and logging all pending connection requests.
- Triggering follow-up actions when new connection requests are detected.
- Integrating pending request data into CRM systems or outreach tools.
Properties
| Name | Meaning |
|---|---|
| Webhook URL | The URL where the response containing the retrieved pending requests will be sent via webhook. It must be a valid endpoint capable of receiving POST requests. Example: https://n8n.your-domain.com/webhook-test/your-webhook-ID |
Output
The node outputs data via a webhook to the specified "Webhook URL". The output JSON contains the results of the "Retrieve Pending Requests" operation, which typically includes details about each pending connection request such as requester information and request metadata.
No binary data output is indicated by the source code.
Dependencies
- Requires an API key credential for authenticating with the LinkedIn automation service.
- Needs a reachable webhook URL configured in the "Webhook URL" property to receive asynchronous responses.
- The node sends a POST request to the external API endpoint
https://api.linkedapi.io/automation/executewith the operation name and webhook URL included in the request body.
Troubleshooting
Common issues:
- Invalid or unreachable webhook URL: Ensure the webhook URL is correct and publicly accessible.
- Authentication failures: Verify that the API key credential is correctly configured and has necessary permissions.
- Network connectivity problems between n8n and the LinkedIn automation API endpoint.
Error messages:
- Errors related to webhook delivery usually indicate misconfigured URLs or network issues.
- Authentication errors suggest invalid or missing API credentials.
Resolving these typically involves checking webhook URL correctness, ensuring proper credential setup, and verifying network access.
Links and References
- LinkedIn API Documentation
- n8n Webhook Documentation
- [Linked API Service (third-party) documentation if available]