Browserflow for LinkedIn icon

Browserflow for LinkedIn

Automate LinkedIn with Browserflow

Overview

This node integrates with the Browserflow API to automate various LinkedIn-related tasks. Specifically, the "Check if a Person Is a Connection" operation allows users to verify whether a given LinkedIn profile URL corresponds to a connection of the authenticated user.

Common scenarios where this node is beneficial include:

  • Automating outreach workflows by filtering LinkedIn profiles based on connection status.
  • Enriching CRM or contact databases with connection information.
  • Validating network relationships before sending messages or connection invites.

For example, a user can input a LinkedIn profile URL and quickly determine if that person is already connected, enabling conditional logic in automation workflows.

Properties

Name Meaning
LinkedIn URL The LinkedIn profile URL to check connection status. This must be a valid LinkedIn profile link.

Output

The node outputs a JSON object representing the connection status response from the Browserflow API. The exact structure depends on the API's response but typically includes fields indicating whether the specified LinkedIn profile is a connection or not.

No binary data output is produced by this operation.

Example output (simplified):

{
  "isConnection": true,
  "profileUrl": "https://www.linkedin.com/in/example-profile",
  "message": "User is a connection"
}

Dependencies

  • Requires an active API key credential for the Browserflow service.
  • The node makes HTTP POST requests to the Browserflow API endpoint https://app.browserflow.io/api/linkedin-check-connection-status.
  • Proper configuration of the API key credential within n8n is necessary for authentication.

Troubleshooting

  • Common issues:

    • Invalid or missing LinkedIn profile URL input will cause the API request to fail.
    • Expired or incorrect API key credentials will result in authentication errors.
    • Network connectivity problems may prevent reaching the Browserflow API.
  • Error messages:

    • Errors include HTTP status codes and descriptive messages returned by the API.
    • Example: "An error with status 401 occurred" indicates unauthorized access due to invalid API key.
    • To resolve, verify the API key credential and ensure it has proper permissions.
    • For 400-level errors, check the LinkedIn URL format and required parameters.

Links and References

Discussion