Skip to Workflow Atlas
ETL PipelineAI systemIntermediate

Yelp Review Analysis & Notification Workflow

Yelp Review Analysis & Notification Workflow is a 10-node automation blueprint connecting Yelp API, Bright Data, Google Gemini. 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.

10

Nodes

10

Links

1

Run groups

Connected tools

3 integrations

  • Yelp API
  • Bright Data
  • Google AI

Canvas controls

Fit wide systems, then zoom into any run group.

Yelp Review Analysis & Notification Workflow execution lanes1 run groups containing 10 workflow nodes and 10 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 1 outgoing connections.STARTWhen clicking ‘Test workf…TRIGGERMANUALTRIGGER0 IN / 1 OUTSet Yelp URL with the Bright Data Zone. transform node, set. 1 incoming and 1 outgoing connections.STEP 02Set Yelp URL with the Bri…TRANSFORMSET1 IN / 1 OUTHTTP Request to fetch the Yelp Business Reviews. integration node, httpRequest. 1 incoming and 1 outgoing connections.STEP 03HTTP Request to fetch the…INTEGRATIONHTTPREQUEST1 IN / 1 OUTStructured Data Extractor. ai node, chainLlm. 3 incoming and 2 outgoing connections.STEP 04Structured Data ExtractorAICHAINLLM3 IN / 2 OUTSummarization Chain. ai node, chainSummarization. 2 incoming and 1 outgoing connections.STEP 05Summarization ChainAICHAINSUMMARIZATION2 IN / 1 OUTMerge. decision node, merge. 2 incoming and 1 outgoing connections.STEP 06MergeDECISIONMERGE2 IN / 1 OUTWebhook Notifier for the merged response. integration node, httpRequest. 1 incoming and 0 outgoing connections.OUTCOMEWebhook Notifier for the …INTEGRATIONHTTPREQUEST1 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 OUTStructured Output Parser. ai node, outputParserStructured. 0 incoming and 1 outgoing connections.DEPENDENCY · DEPTH 1Structured Output ParserAIOUTPUTPARSERSTRUCTURED0 IN / 1 OUTGoogle Gemini Chat Model for Summarization. Google AI node, lmChatGoogleGemini. 0 incoming and 1 outgoing connections.DEPENDENCY · DEPTH 1Google Gemini Chat Model …GOOGLE 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.10 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’

7 Execution Links3 Support Dependencies
  1. Start

    When clicking ‘Test workflow’

    Trigger

  2. Step 2

    Set Yelp URL with the Bright Data Zone

    Transform

  3. Step 3

    HTTP Request to fetch the Yelp Business Reviews

    Integration

  4. Step 4

    Structured Data Extractor

    AI reasoning

  5. Step 5

    Summarization Chain

    AI reasoning

  6. Step 6

    Merge

    Decision

  7. Outcome

    Webhook Notifier for the merged response

    Integration

Attached dependencies

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

3 nodes
  • Google Gemini Chat Model for Summarization

    AI reasoning dependency

  • Google Gemini Chat Model

    AI reasoning dependency

  • Structured Output Parser

    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.