← All N8N workflows
AI & researchBright DataEmail SendFilterFormForm Trigger

LinkedIn Profile Finder via Form using Bright Data & GPT-4o-mini

Configured with Bright Data, Email Send, Filter, Form, and additional nodes. Review the connections and setup before adapting this template.

Workflow preview
TransformExtract Body and Titlefrom WebsiteHtmlTriggerWhen User CompletesFormForm TriggerIntegrationGet LinkedIn Entry onGoogleBright DataAI & modelsParse Google ResultsOpen AiIntegrationForm Not FoundFormRoutingGet only MatchingProfilesFilterTransformLimit to 1 ProfileLimitTransformExtract Parsed ResultsSplit OutRoutingLinkedIn Profile isFound?IfTransformEdit Url LinkedInEdit FieldsTransformEdit Company SearchEdit FieldsTransformExtract Body and Titlefrom Website1HtmlIntegrationGet Company on GoogleBright DataAI & modelsParse Google Resultsfor CompanyOpen AiTransformSplit OutSplit OutAI & modelsCreate a Followup forCompany and PersonOpen AiTransformMergeMergeMessagingSend EmailEmail SendIntegrationForm Email SentForm

Node categories in this workflow

  • Transform
  • Trigger
  • Integration
  • AI & models
  • Routing
  • Messaging

Icons describe general node roles, inferred from node types. Inspect the parameters for the configured action.

Drag to pan; use + and − to zoom. Reconstructed from the exported node positions; nothing runs here. Dashed lines represent non-main connections. Full node names and notes appear below.

How it works

The exported workflow contains the following configured nodes. Their connections are shown above; inspect the JSON for the complete logic, expressions, and external actions.

Workflow node names, types, and operations
NodeCategoryTypeOperation
Extract Body and Title from WebsiteTransformHtmlextractHtmlContent
When User Completes FormTriggerForm TriggerSee node parameters
Get LinkedIn Entry on GoogleIntegrationBright DataSee node parameters
Parse Google ResultsAI & modelsOpen AiSee node parameters
Form Not FoundIntegrationFormcompletion
Get only Matching ProfilesRoutingFilterSee node parameters
Limit to 1 ProfileTransformLimitSee node parameters
Extract Parsed ResultsTransformSplit OutSee node parameters
LinkedIn Profile is Found?RoutingIfSee node parameters
Edit Url LinkedInTransformEdit FieldsSee node parameters
Edit Company SearchTransformEdit FieldsSee node parameters
Extract Body and Title from Website1TransformHtmlextractHtmlContent
Get Company on GoogleIntegrationBright DataSee node parameters
Parse Google Results for CompanyAI & modelsOpen AiSee node parameters
Split OutTransformSplit OutSee node parameters
Create a Followup for Company and PersonAI & modelsOpen AiSee node parameters
MergeTransformMergeSee node parameters
Send EmailMessagingEmail SendSee node parameters
Form Email SentIntegrationFormcompletion

Setup

  1. Download the JSON and import it into an isolated n8n instance. Leave the workflow inactive.
  2. Connect your own credentials through n8n’s credential store. Replace REPLACE_WITH_* values with your resource identifiers.
  3. Inspect API destinations, Code nodes, database queries, file paths, and outbound actions.
  4. Run with synthetic data and harmless destinations. Enable triggers only after checking the actual outputs.

Requirements

An n8n instance with the listed node types and compatible versions. Service-connected workflows may require accounts, credentials, or paid APIs.

Credential types declared in the source

  • brightdataApi
  • openAiApi
  • smtp

Workflow notes

LinkedIn Profile Finder via Form using Bright Data & GPT-4o-mini

LinkedIn Profile Finder via Form using Bright Data & GPT-4o-mini

Purpose and structure

This folder contains the LinkedIn Profile Finder via Form using Bright Data & GPT-4o-mini workflow. Its executable nodes use brightData, emailSend, filter, form, formTrigger, html, if, limit, merge, openAi, set, splitOut. The table and connection map below are derived from the JSON, not an inferred guarantee of behavior.

Setup

Import inactive. Configure your own credentials and replace REPLACE_WITH_* values. Review external destinations and Code nodes before running.

Entry points

When User Completes Form

Verification

Sanitized source candidate; not runtime-tested. This overview is generated from node metadata. Read the folder README for the connection map, credential types, and license.

Attribution

https://github.com/Zie619/n8n-workflows/blob/94007c1445d9258a7da116646b79473e7c7c3282/workflows/Splitout/1937_Splitout_Limit_Automation_Triggered.json MIT; preserve source notices.

More in AI & research