Leadspicker NodeInstall

Overview

This node integrates with the Leadspicker API to interact with LinkedIn profile data and other related resources. Specifically, for the Linkedin resource with the Get Profile operation, it scrapes and returns detailed information about a LinkedIn personal or company profile based on the provided LinkedIn URL.

Common scenarios where this node is beneficial include:

• Enriching contact or lead data by fetching up-to-date LinkedIn profile details.
• Automating data collection for sales, marketing, or recruitment workflows.
• Integrating LinkedIn profile insights into CRM or outreach systems.

Practical example:

• Given a LinkedIn profile URL of a potential client or candidate, the node fetches structured profile details such as name, position, company, and other public information, which can then be used downstream in an automation workflow.

Properties

Output

The node outputs JSON data containing the scraped LinkedIn profile details returned by the Leadspicker API. This typically includes structured information about the profile such as name, job title, company, location, and possibly other public profile attributes.

No binary data output is indicated for this operation.

Dependencies

• Requires an active connection to the Leadspicker API via an API key credential configured in n8n.
• The node makes HTTP POST requests to Leadspicker endpoints to fetch LinkedIn profile data.
• No additional external services or environment variables are explicitly required beyond the API authentication.

Troubleshooting

• Common issues:

  • Invalid or malformed LinkedIn URLs may cause the API request to fail or return incomplete data.
  • Network connectivity problems or invalid API credentials will result in errors when calling the Leadspicker API.
  • Rate limits imposed by the Leadspicker API could cause temporary failures.

• Error messages:

  • "The operation "getProfile" is not supported for Linkedin resource." — indicates a misconfiguration or unsupported operation; ensure the operation name matches exactly.
  • API errors returned from Leadspicker (e.g., authentication failure, invalid URL) will be surfaced as error messages; verify credentials and input parameters.

• Resolution tips:

  • Double-check the LinkedIn URL format before running the node.
  • Confirm that the API key credential is valid and has necessary permissions.
  • Enable "Continue On Fail" in the node settings to handle individual item errors gracefully during batch processing.

Links and References

• Leadspicker API Documentation (for detailed API endpoint info)
• LinkedIn Profile URL Format Guidelines