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 enables searching within LinkedIn data via the Unipile API. It is designed to perform search queries against LinkedIn accounts, returning relevant results based on specified criteria. This can be useful for automating LinkedIn data retrieval such as finding profiles, posts, or other LinkedIn-related information programmatically.
Typical use cases include:
- Automating lead generation by searching LinkedIn accounts with specific parameters.
- Integrating LinkedIn search results into workflows for CRM enrichment.
- Extracting LinkedIn data for analytics or reporting purposes.
Properties
| Name | Meaning |
|---|---|
| Account ID | The identifier of the LinkedIn account to search within. |
| Body (JSON) | A JSON object containing the search query details and parameters sent in the request body. |
| Additional Fields | Optional extra parameters: • Cursor: Pagination cursor to fetch subsequent pages. • Limit: Maximum number of results to return (minimum 1, default 50). |
Output
The node outputs a JSON object containing the search results returned from the Unipile API's LinkedIn search endpoint. The structure typically includes an array of matched items according to the search criteria, along with metadata such as pagination cursors if applicable.
If binary data were involved, it would represent associated files or media, but this node focuses on JSON search results only.
Dependencies
- Requires an active connection to the Unipile API service.
- Needs an API authentication token configured in n8n credentials to authorize requests.
- The base URL for the API is dynamically set from the credential configuration.
Troubleshooting
- Invalid Account ID: Ensure the provided Account ID exists and is accessible with your API credentials.
- Malformed JSON in Body: The "Body (JSON)" property must contain valid JSON; otherwise, the request will fail.
- Pagination Issues: Using an incorrect or expired cursor may result in empty or repeated results.
- API Authentication Errors: Verify that the API key/token is correctly configured and has sufficient permissions.
- Rate Limits: Excessive requests might trigger rate limiting; consider adding delays or reducing the limit parameter.
Links and References
- Unipile API Documentation (for detailed API usage)
- LinkedIn Developer Documentation (for understanding LinkedIn data structures)