Skip to Workflow Atlas
ETL PipelineIntermediate

YouTube Video Insights Automation

YouTube Video Insights Automation is a 14-node automation blueprint connecting Google API. Inspect its trigger, execution graph, branches, and implementation requirements.

Interactive system map

Execution flows, separated by connected path.

Each horizontal lane is one connected flow. Solid lines show runtime execution; dashed lines show AI, model, memory, or tool dependencies.

14

Nodes

18

Links

1

Flows

Connected tools

1 integrations

  • Google API
YouTube Video Insights Automation execution lanes1 connected flows containing 14 workflow nodes and 18 visible links. Solid lines are execution links and dashed lines are support dependencies. Focus any node to inspect its immediate path.When clicking ‘Test workflow’. trigger node, manualTrigger. 0 incoming and 1 outgoing connections.When clicking ‘Test workf…TRIGGERMANUALTRIGGER0 IN / 1 OUTSet: Define Initial Variables. transform node, set. 1 incoming and 1 outgoing connections.Set: Define Initial Varia…TRANSFORMSET1 IN / 1 OUTSwitch: What kind of question do we want to ask?. decision node, switch. 1 incoming and 6 outgoing connections.Switch: What kind of ques…DECISIONSWITCH1 IN / 6 OUTSet: Transcript Prompt. transform node, set. 1 incoming and 1 outgoing connections.Set: Transcript PromptTRANSFORMSET1 IN / 1 OUTSet: Transcript with Timestamps Prompt. transform node, set. 1 incoming and 1 outgoing connections.Set: Transcript with Time…TRANSFORMSET1 IN / 1 OUTSet: Summarize Prompt. transform node, set. 1 incoming and 1 outgoing connections.Set: Summarize PromptTRANSFORMSET1 IN / 1 OUTSet: Scene Prompt. transform node, set. 1 incoming and 1 outgoing connections.Set: Scene PromptTRANSFORMSET1 IN / 1 OUTSet: Scene Clips. transform node, set. 1 incoming and 1 outgoing connections.Set: Scene ClipsTRANSFORMSET1 IN / 1 OUTSet: Fallback. transform node, set. 1 incoming and 1 outgoing connections.Set: FallbackTRANSFORMSET1 IN / 1 OUTSet: Merged Values. transform node, set. 6 incoming and 1 outgoing connections.Set: Merged ValuesTRANSFORMSET6 IN / 1 OUTHTTP Request to Google. integration node, httpRequest. 1 incoming and 2 outgoing connections.HTTP Request to GoogleINTEGRATIONHTTPREQUEST1 IN / 2 OUTCode: Merge data from prior nodes with HTTP Output. transform node, code. 1 incoming and 1 outgoing connections.Code: Merge data from pri…TRANSFORMCODE1 IN / 1 OUTIf: Was an error detected?. decision node, if. 1 incoming and 0 outgoing connections.If: Was an error detected?DECISIONIF1 IN / 0 OUTSet Fields: Define Outcome. transform node, set. 1 incoming and 0 outgoing connections.Set Fields: Define OutcomeTRANSFORMSET1 IN / 0 OUT

Signal inspector

Focus, hover, or select a node to illuminate its real path.

Execution linkSupport dependencytriggeraidecisiontransformintegration
Scroll horizontally to follow every connected flow.14 connected nodesEnter or click to lock · Escape to clear

Execution breakdown

Follow each connected flow from start to outcome.

The readable view below uses the same graph relationships as the interactive map. Each row is a connected flow; columns advance only when an actual link connects the nodes.

01

Connected Flow

When clicking ‘Test workflow’

18 Execution Links
  1. Start

    When clicking ‘Test workflow’

    Trigger

  2. Step 2

    Set: Define Initial Variables

    Transform

  3. Step 3

    Switch: What kind of question do we want to ask?

    Decision

  4. Step 4

    Set: Transcript Prompt

    Transform

    Set: Transcript with Timestamps Prompt

    Transform

    Set: Summarize Prompt

    Transform

    Set: Scene Prompt

    Transform

    Set: Scene Clips

    Transform

    Set: Fallback

    Transform

  5. Step 5

    Set: Merged Values

    Transform

  6. Step 6

    HTTP Request to Google

    Integration

  7. Step 7

    Code: Merge data from prior nodes with HTTP Output

    Transform

    If: Was an error detected?

    Decision

  8. Outcome

    Set Fields: Define Outcome

    Transform

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.