Skip to Workflow Atlas
ETL PipelineAI systemIntermediate

LinkedIn Data Processing Automation

LinkedIn Data Processing Automation is a 18-node automation blueprint connecting Bright Data MCP, Google Gemini, n8n LangChain. Inspect its trigger, execution graph, branches, and implementation requirements.

Interactive system map

Follow the runtime. Inspect what supports it.

Solid horizontal paths show main-channel execution. Violet dependencies sit beneath the exact step they configure or empower.

18

Nodes

18

Links

1

Run groups

Connected tools

3 integrations

  • Bright Data MCP
  • Google AI
  • LangChain

Canvas controls

Fit wide systems, then zoom into any run group.

LinkedIn Data Processing Automation execution lanes1 run groups containing 18 workflow nodes and 18 visible links. Solid horizontal lines are main-channel runtime links. Violet dashed lines connect typed dependencies beneath the runtime step they support. Focus any node to inspect its immediate path.When clicking ‘Test workflow’. trigger node, manualTrigger. 0 incoming and 2 outgoing connections.STARTWhen clicking ‘Test workf…TRIGGERMANUALTRIGGER0 IN / 2 OUTList all available tools for Bright Data. integration node, mcpClient. 1 incoming and 1 outgoing connections.STEP 02List all available tools …INTEGRATIONMCPCLIENT1 IN / 1 OUTList all tools for Bright Data. integration node, mcpClient. 1 incoming and 1 outgoing connections.STEP 02List all tools for Bright…INTEGRATIONMCPCLIENT1 IN / 1 OUTSet the URLs. transform node, set. 1 incoming and 1 outgoing connections.STEP 03Set the URLsTRANSFORMSET1 IN / 1 OUTSet the LinkedIn Company URL. transform node, set. 1 incoming and 1 outgoing connections.STEP 03Set the LinkedIn Company …TRANSFORMSET1 IN / 1 OUTBright Data MCP Client For LinkedIn Person. integration node, mcpClient. 1 incoming and 2 outgoing connections.STEP 04Bright Data MCP Client Fo…INTEGRATIONMCPCLIENT1 IN / 2 OUTBright Data MCP Client For LinkedIn Company. integration node, mcpClient. 1 incoming and 2 outgoing connections.STEP 04Bright Data MCP Client Fo…INTEGRATIONMCPCLIENT1 IN / 2 OUTCreate a binary data for LinkedIn person info extract. transform node, function. 1 incoming and 1 outgoing connections.STEP 05Create a binary data for …TRANSFORMFUNCTION1 IN / 1 OUTWebhook for LinkedIn Person Web Scraper. integration node, httpRequest. 1 incoming and 0 outgoing connections.STEP 05Webhook for LinkedIn Pers…INTEGRATIONHTTPREQUEST1 IN / 0 OUTCode. transform node, code. 1 incoming and 1 outgoing connections.STEP 05CodeTRANSFORMCODE1 IN / 1 OUTLinkedIn Data Extractor. ai node, informationExtractor. 2 incoming and 1 outgoing connections.STEP 05LinkedIn Data ExtractorAIINFORMATIONEXTRACTOR2 IN / 1 OUTWrite the LinkedIn person info to disk. integration node, readWriteFile. 1 incoming and 0 outgoing connections.STEP 06Write the LinkedIn person…INTEGRATIONREADWRITEFILE1 IN / 0 OUTMerge. decision node, merge. 2 incoming and 1 outgoing connections.STEP 06MergeDECISIONMERGE2 IN / 1 OUTAggregate. transform node, aggregate. 1 incoming and 2 outgoing connections.STEP 07AggregateTRANSFORMAGGREGATE1 IN / 2 OUTCreate a binary data for LinkedIn company info extract. transform node, function. 1 incoming and 1 outgoing connections.STEP 08Create a binary data for …TRANSFORMFUNCTION1 IN / 1 OUTWebhook for LinkedIn Company Web Scraper. integration node, httpRequest. 1 incoming and 0 outgoing connections.STEP 08Webhook for LinkedIn Comp…INTEGRATIONHTTPREQUEST1 IN / 0 OUTWrite the LinkedIn company info to disk. integration node, readWriteFile. 1 incoming and 0 outgoing connections.OUTCOMEWrite the LinkedIn compan…INTEGRATIONREADWRITEFILE1 IN / 0 OUTGoogle Gemini Chat Model. Google AI node, lmChatGoogleGemini. 0 incoming and 1 outgoing connections.DEPENDENCY · DEPTH 1Google Gemini Chat ModelGOOGLE AILMCHATGOOGLEGEMINI0 IN / 1 OUT

Signal inspector

Focus, hover, or select a step to isolate its runtime and support links.

Main-channel runtimeTyped dependencytriggeraidecisiontransformintegration
Scroll horizontally to follow every connected flow.18 connected nodesEnter or click to lock · Escape to clear

Runtime breakdown

Read the execution spine before its dependencies.

Each run group separates main-channel steps from the models, tools, retrievers, and data services that support them. Start and outcome labels apply only to runtime nodes.

01

Run Group

When clicking ‘Test workflow’

17 Execution Links1 Support Dependency
  1. Start

    When clicking ‘Test workflow’

    Trigger

  2. Step 2

    List all available tools for Bright Data

    Integration

    List all tools for Bright Data

    Integration

  3. Step 3

    Set the URLs

    Transform

    Set the LinkedIn Company URL

    Transform

  4. Step 4

    Bright Data MCP Client For LinkedIn Person

    Integration

    Bright Data MCP Client For LinkedIn Company

    Integration

  5. Step 5

    Create a binary data for LinkedIn person info extract

    Transform

    Webhook for LinkedIn Person Web Scraper

    Integration

    Code

    Transform

    LinkedIn Data Extractor

    AI reasoning

  6. Step 6

    Write the LinkedIn person info to disk

    Integration

    Merge

    Decision

  7. Step 7

    Aggregate

    Transform

  8. Step 8

    Create a binary data for LinkedIn company info extract

    Transform

    Webhook for LinkedIn Company Web Scraper

    Integration

  9. Outcome

    Write the LinkedIn company info to disk

    Integration

Attached dependencies

These nodes support the runtime above; they are not additional starts or outcomes.

1 node
  • Google Gemini Chat Model

    AI reasoning dependency

Turn the map into a plan

Adapt this blueprint to your company.

Bring the system shape into a workspace, then define the production controls, data boundaries, owners, and delivery sequence around your context.