Browserflow for LinkedIn

Overview

This n8n node automates the retrieval of public profile data from a LinkedIn profile using Browserflow. By providing a LinkedIn profile URL, users can extract structured information about that profile for use in workflows such as lead enrichment, HR automation, or social selling. This is particularly useful for sales teams, recruiters, or anyone needing to gather LinkedIn data at scale without manual copy-pasting.

Example scenarios:

• Enriching CRM records with up-to-date LinkedIn profile details.
• Automating candidate research in recruitment pipelines.
• Building lists of prospects for outreach campaigns.

Properties

Output

The node returns the extracted data from the specified LinkedIn profile in the json output field. The exact structure depends on the data available on the profile and the Browserflow API response, but typically includes fields such as:

{
  "name": "Full Name",
  "headline": "Current Position / Headline",
  "location": "Location",
  "about": "Profile summary/about section",
  "experience": [
    {
      "title": "Job Title",
      "company": "Company Name",
      "duration": "Time Period"
    }
    // ...more experience entries
  ],
  "education": [
    {
      "school": "School Name",
      "degree": "Degree",
      "years": "Years Attended"
    }
    // ...more education entries
  ],
  // ...other available LinkedIn profile fields
}

Note: The actual fields may vary depending on the profile's visibility and the Browserflow API's capabilities.

Dependencies

• Browserflow API: Requires valid credentials for the Browserflow API (browserflowApi).
• n8n Configuration: The node must be configured with the appropriate API key in the n8n credentials for Browserflow.
• External Service: Internet access to https://app.browserflow.io/api/.

Troubleshooting

Common Issues:

• Invalid or missing LinkedIn URL: Ensure the provided URL is a valid LinkedIn profile link.
• API Authentication errors: Make sure the Browserflow API credentials are correctly set up in n8n.
• Rate limits or CAPTCHAs: Excessive requests to LinkedIn may trigger rate limiting or CAPTCHAs, which could cause incomplete or failed data extraction.
• Profile privacy settings: If the target profile is private or restricted, some fields may not be available in the output.

Error Messages & Resolutions:

• "401 Unauthorized": Check your Browserflow API credentials.
• "400 Bad Request": Verify that the LinkedIn URL is correct and properly formatted.
• "429 Too Many Requests": Wait before making more requests; consider reducing request frequency.

Links and References

• Browserflow Documentation
• LinkedIn Profile URLs - Help
• n8n Credentials Documentation