Actions14
- AutoCPH Actions
- Linkedin Actions
- Person Actions
- Project Actions
- Reply Actions
Overview
This node integrates with the Leadspicker API to manage and manipulate data related to people, projects, replies, company profiles, and LinkedIn activities. Specifically, for the Person resource with the Create Person operation, it allows users to create a new person record within a specified project by providing detailed personal, company, social profile, and custom field information.
Common scenarios where this node is beneficial include:
- Adding new contacts or leads into a CRM or marketing system automatically.
- Enriching project databases with detailed person profiles including job titles, company info, and social links.
- Automating lead generation workflows by programmatically creating person entries based on external data sources.
Practical example:
- A marketing automation workflow that collects lead details from a form and uses this node to create a new person in a specific project, including their email, position, and company details.
Properties
| Name | Meaning |
|---|---|
| Project ID | The numeric ID of the project where the new person will be created. |
| Person Details | Collection of personal information about the person: |
| - Country: Country of the person | |
| - Email: Email address of the person | |
| - First Name: Person's first name | |
| - Last Name: Person's last name | |
| - Position: Job title or position of the person | |
| Company Details | Collection of company-related information: |
| - Company Name: Name of the company where the person works | |
| - Company Website: URL of the company's website | |
| - Company LinkedIn: LinkedIn URL of the company | |
| Social Profiles | Collection of social profile URLs: |
| - LinkedIn: Personal LinkedIn profile URL | |
| - Sales Navigator: LinkedIn Sales Navigator URL | |
| Custom Fields | Multiple custom key-value pairs allowing additional arbitrary fields to be added to the person. |
Output
The node outputs JSON data representing the newly created person object as returned by the Leadspicker API. This typically includes all submitted fields along with any assigned IDs or metadata generated by the API.
If the API supports binary data (not indicated here), it would be summarized accordingly, but for this operation, output is purely JSON.
Dependencies
- Requires an active connection to the Leadspicker API via an API key credential configured in n8n.
- The node depends on the
leadspickerApiRequesthelper function to make authenticated HTTP requests to the Leadspicker endpoints. - No other external services are explicitly required for this operation.
Troubleshooting
- Missing or invalid Project ID: The operation requires a valid numeric project ID. Ensure the project exists and the ID is correct.
- Invalid or incomplete person details: Required fields like email or names should be properly formatted; otherwise, the API may reject the request.
- API authentication errors: Verify that the API key credential is correctly set up and has sufficient permissions.
- Network or API downtime: Temporary connectivity issues can cause failures; retry or check API status.
- Error messages from API: The node throws errors if the operation is unsupported or parameters are invalid. Review error messages carefully and adjust input parameters accordingly.