Skip to Workflow Atlas
Playbook AtlasWorkflow Atlas
Workflow blueprintBrowse workflows
Event-Driven AutomationIntermediate

YouTube Description Updater

YouTube Description Updater is a 6-node automation blueprint connecting YouTube API. Inspect its trigger, execution graph, branches, and implementation requirements.

YouTube API

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.

6

Nodes

5

Links

1

Run groups

Connected tools

1 integrations

  • YouTube API

Canvas controls

Fit wide systems, then zoom into any run group.

YouTube Description Updater execution lanes1 run groups containing 6 workflow nodes and 5 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.Trigger Workflow. trigger node, manualTrigger. 0 incoming and 1 outgoing connections.STARTTrigger WorkflowTRIGGERMANUALTRIGGER0 IN / 1 OUTConfig. transform node, set. 1 incoming and 1 outgoing connections.STEP 02ConfigTRANSFORMSET1 IN / 1 OUTList all videos. integration node, youTube. 1 incoming and 1 outgoing connections.STEP 03List all videosINTEGRATIONYOUTUBE1 IN / 1 OUTGenerate Description. transform node, set. 1 incoming and 1 outgoing connections.STEP 04Generate DescriptionTRANSFORMSET1 IN / 1 OUTCheck if has changed. decision node, if. 1 incoming and 1 outgoing connections.STEP 05Check if has changedDECISIONIF1 IN / 1 OUTUpdate Description. integration node, youTube. 1 incoming and 0 outgoing connections.OUTCOMEUpdate DescriptionINTEGRATIONYOUTUBE1 IN / 0 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.6 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

Trigger Workflow

5 Execution Links

  1. Start

    Trigger Workflow

    Trigger

  2. Step 2

    Config

    Transform

  3. Step 3

    List all videos

    Integration

  4. Step 4

    Generate Description

    Transform

  5. Step 5

    Check if has changed

    Decision

  6. Outcome

    Update Description

    Integration

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.

Create a build planReturn to the atlas