Actions7
- Enrichment Actions
- Linkedin Actions
Overview
This node integrates with the Piloterr API to retrieve detailed information about employees of a specified LinkedIn company. It is particularly useful for workflows that require enrichment of company data, talent sourcing, HR analytics, or competitive research by programmatically accessing employee-related information from LinkedIn company profiles.
Practical examples:
- Automating the collection of employee lists for a given company for recruitment purposes.
- Enriching CRM records with up-to-date employee information from LinkedIn.
- Gathering insights on company workforce composition for market analysis.
Properties
| Name | Type | Meaning |
|---|---|---|
| Query | String | The LinkedIn company to look up. Accepts formats such as tesla-motors, a numeric company ID like 1337, or a full URL like linkedin.com/company/tesla-motors. This field is required. |
Output
The node outputs a JSON object (or array of objects) containing employee information for the specified LinkedIn company. The exact structure depends on the response from the Piloterr API endpoint /v2/linkedin/company/employee_info. Typical fields may include employee names, positions, profile URLs, and other publicly available LinkedIn data.
Note:
- No binary data is output; all results are in JSON format.
- If an error occurs and "Continue On Fail" is enabled, the output will contain an
errorfield with the error message and an emptyjsonobject.
Dependencies
- External Service: Requires access to the Piloterr API.
- API Key: You must configure valid Piloterr API credentials (
piloterrApi) in n8n. - n8n Configuration: Ensure the node has network access to
https://piloterr.com/api.
Troubleshooting
Common Issues:
- Invalid or missing API key: Results in authentication errors. Make sure your Piloterr API credentials are correctly set up in n8n.
- Incorrect Query Format: Supplying an invalid company identifier may result in no data or an error. Use the correct format as described in the property.
- API Rate Limits: Excessive requests may trigger rate limiting by Piloterr. Monitor your usage and handle rate limit errors appropriately.
Error Handling:
- If "Continue On Fail" is enabled, errors for individual items will be included in the output under the
errorfield. - Common error messages may include:
"Invalid API key": Check your credentials."Company not found": Verify the query value."Rate limit exceeded": Wait before retrying or contact Piloterr support.