Actions7
Overview
This n8n node automates LinkedIn actions using Browserflow. Specifically, for the "Check if a Person Is a Connection" operation, it checks whether a given LinkedIn profile URL is already a connection of the authenticated user. This is useful in workflows where you need to verify your relationship status with a LinkedIn user before taking further actions, such as sending messages or connection invites.
Practical examples:
- Before sending a message, check if the recipient is already a connection.
- Build lists of non-connections for targeted outreach.
- Automate CRM enrichment by verifying LinkedIn relationships.
Properties
| Name | Type | Meaning |
|---|---|---|
| LinkedIn URL | String | The LinkedIn profile URL to check connection status. Required. |
Output
The node returns a JSON object indicating the connection status between the authenticated user and the specified LinkedIn profile. While the exact structure depends on the API response, you can expect fields such as:
{
"isConnection": true,
"profileUrl": "https://www.linkedin.com/in/example-user/",
// ...other possible metadata
}
isConnection: Boolean indicating if the person is a connection.profileUrl: The LinkedIn profile URL checked.
Dependencies
- Browserflow API: Requires valid credentials (API key) configured in n8n under the name
browserflowApi. - External Service: Relies on Browserflow's cloud service at
https://app.browserflow.io/api/.
Troubleshooting
Common issues:
- Invalid or missing LinkedIn URL: Ensure the provided URL is correct and points to a valid LinkedIn profile.
- Authentication errors: Make sure the Browserflow API credentials are set up correctly in n8n.
- API rate limits or downtime: If the Browserflow service is unavailable or rate-limited, requests may fail.
Error messages and resolutions:
"401 Unauthorized": Check your Browserflow API credentials."400 Bad Request": Verify that the LinkedIn URL is properly formatted and not empty."Connection status could not be determined": The profile may not exist, or LinkedIn has changed its interface; try again later or contact support.