Actions85
- Account Actions
- Calendar Actions
- Email Actions
- LinkedIn Actions
- Close Job Posting
- Create Job Posting
- Download Applicant Resume
- Edit Job Posting
- Endorse Skill
- Get Company Profile
- Get Hiring Project by ID
- Get Hiring Projects
- Get Inmail Balance
- Get Job Applicant
- Get Job Applicants
- Get Job Offer
- Get Job Postings
- Get Raw Data
- Perform Action on Member
- Publish Job Posting
- Search
- Search Parameters
- Solve Job Publishing Checkpoint
- Messaging Actions
- Post Actions
- User Actions
- Webhook Actions
Overview
This node provides a generic way to send raw JSON payloads to LinkedIn's API endpoints. It is designed for users who want to interact with LinkedIn beyond predefined operations, allowing them to specify any valid LinkedIn API request body in JSON format. This flexibility is useful for advanced use cases such as querying custom LinkedIn data, performing actions not covered by standard nodes, or testing new LinkedIn API features.
A practical example would be sending a custom search query or fetching specific user data by crafting the exact JSON payload required by LinkedIn's API.
Properties
| Name | Meaning |
|---|---|
| Body (JSON) | Raw JSON payload for the generic LinkedIn endpoint. Users input the full JSON request body here. |
Output
The node outputs the response from LinkedIn's API in the json field of the output data. The structure of this JSON depends entirely on the LinkedIn API endpoint called and the request body sent. The node does not transform or interpret the response; it simply passes it through as received.
If the LinkedIn API returns binary data (e.g., media files), the node can also output this in the binary data property, but this depends on the specific API call made via the raw JSON.
Dependencies
- Requires an API key credential for authenticating with LinkedIn's API.
- The node expects proper configuration of this credential within n8n.
- Network access to LinkedIn's API endpoints is necessary.
Troubleshooting
- Invalid JSON Payload: If the JSON entered in the "Body (JSON)" property is malformed, the node will fail. Ensure the JSON syntax is correct.
- API Authentication Errors: If the API key or authentication token is missing or invalid, LinkedIn will reject the request. Verify that the credential is correctly set up.
- LinkedIn API Errors: Since the node sends raw requests, any errors returned by LinkedIn (such as permission issues, rate limits, or invalid parameters) will be passed back. Review the LinkedIn API documentation for error codes and messages.
- Unexpected Response Structure: Because the node does not parse responses, downstream nodes must handle varying JSON structures depending on the request.