Actions14
- AutoCPH Actions
- Linkedin Actions
- Person Actions
- Project Actions
- Reply Actions
Overview
This node integrates with the Leadspicker API to find and enrich contact information automatically. Specifically, for the AutoCPH resource with the By Company Name operation, it searches for persons associated with a given company name, optionally filtered by country and job functions. It can also limit the number of results returned and optionally enrich contacts with email addresses.
Typical use cases include:
- Finding key contacts at a target company for sales or recruitment outreach.
- Enriching lead lists with verified emails and job function filters.
- Automating contact discovery based on company names without needing LinkedIn URLs.
Example: You want to find up to 5 people working at "Acme Corp" headquartered in Germany, filtering for roles like "CEO" or "Head of Sales", and get their email addresses if available.
Properties
| Name | Meaning |
|---|---|
| Company Name | The exact name of the company to search contacts for. |
| Country | (Optional) The country where the company's headquarters is located, to narrow down the search. |
| Functions | Job functions to filter contacts by, e.g., CEO, Founder, Head of Sales. Multiple functions can be added. |
| Search Result Limit | Maximum number of persons to return from the search. Must be at least 1. |
| Enrich with Emails | Boolean flag indicating whether to attempt to find and include email addresses for the contacts. |
Output
The node outputs an array of JSON objects representing persons found matching the criteria. Each object typically contains contact details such as name, position, company info, and optionally email addresses if enrichment was requested.
If email enrichment is enabled, the output includes verified email addresses for the contacts when available.
No binary data output is produced by this operation.
Dependencies
- Requires an active connection to the Leadspicker API via an API key credential configured in n8n.
- No additional environment variables are needed beyond the API authentication setup.
- The node makes HTTP POST requests to the
/autocph/by-company-nameendpoint of the Leadspicker API.
Troubleshooting
- Empty Results: If no contacts are returned, verify the company name spelling and consider specifying the country to narrow the search.
- Invalid Parameters: Ensure that the "Search Result Limit" is a positive integer and required fields like "Company Name" are provided.
- API Errors: Common errors may relate to invalid or missing API credentials. Confirm your API key is correctly set up in n8n credentials.
- Email Enrichment Fails: Email enrichment depends on external data availability; if emails are not found, try disabling enrichment or adjusting filters.
- Function Filters Ignored: Make sure function names are spelled correctly and non-empty; empty or whitespace-only strings are ignored.
Links and References
- Leadspicker API Documentation (general reference for API endpoints)
- n8n Documentation - Creating Custom Nodes
- Leadspicker AutoCPH Endpoint Reference (for detailed parameter descriptions)
If you need summaries for other resources or operations, feel free to ask!