Actions7
- Enrichment Actions
- Linkedin Actions
Overview
The Piloterr node's "Linkedin: Job Search" operation allows users to search for job postings on LinkedIn using the Piloterr API. This is useful for automating job market research, aggregating job listings for specific companies or keywords, and integrating LinkedIn job data into recruitment workflows or analytics pipelines.
Practical examples:
- Automatically gather job postings for a particular company or keyword.
- Monitor new job openings in a specific sector or location.
- Feed LinkedIn job data into dashboards or applicant tracking systems.
Properties
| Name | Type | Meaning |
|---|---|---|
| Query | String | LinkedIn company identifier or URL to look up jobs for. Format: 1337 or linkedin.com/company/33246798. |
| Page | Number | Page number of results to retrieve (for pagination). |
Output
The node outputs a JSON array containing job posting information as returned by the Piloterr API for LinkedIn job searches. The exact structure depends on the API response, but typically includes fields such as job title, company, location, description, and posting date.
Example output structure:
[
{
"title": "Software Engineer",
"company": "Example Corp",
"location": "San Francisco, CA",
"description": "...",
"datePosted": "2024-06-01",
// ...other job-related fields
}
]
Note: The actual fields may vary based on the API's current implementation.
Dependencies
- External Service: Requires access to the Piloterr API.
- API Key: You must configure valid Piloterr API credentials (
piloterrApi) in n8n. - n8n Configuration: No additional environment variables are required beyond the API key setup.
Troubleshooting
Common issues:
- Invalid API Key: If your API key is missing or incorrect, you may receive authentication errors from the API.
- Incorrect Query Format: Supplying an invalid company ID or malformed LinkedIn URL may result in empty results or errors.
- Pagination Errors: Requesting a page number that does not exist will likely return an empty array.
Error messages:
"error": "Request failed with status code 401"– Check your API credentials."error": "Invalid query parameter"– Ensure the "Query" property is correctly formatted."error": "No results found"– Try adjusting your query or page number.