Skip to Workflow Atlas
ETL PipelineAI systemIntermediate

YouTube Video Upload & Metadata Automation

YouTube Video Upload & Metadata Automation is a 12-node automation blueprint connecting Google Drive, YouTube, OpenAI. 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.

12

Nodes

11

Links

1

Run groups

Connected tools

4 integrations

  • Google Drive
  • YouTube
  • OpenAI
  • LangChain

Canvas controls

Fit wide systems, then zoom into any run group.

YouTube Video Upload & Metadata Automation execution lanes1 run groups containing 12 workflow nodes and 11 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.New Video?. Google Drive node, googleDriveTrigger. 0 incoming and 1 outgoing connections.STARTNew Video?GOOGLE DRIVEGOOGLEDRIVETRIGGER0 IN / 1 OUTDownload New Video. Google Drive node, googleDrive. 1 incoming and 1 outgoing connections.STEP 02Download New VideoGOOGLE DRIVEGOOGLEDRIVE1 IN / 1 OUTUpload Video to Youtube. integration node, youTube. 1 incoming and 1 outgoing connections.STEP 03Upload Video to YoutubeINTEGRATIONYOUTUBE1 IN / 1 OUTApifyToken. transform node, set. 1 incoming and 1 outgoing connections.STEP 04ApifyTokenTRANSFORMSET1 IN / 1 OUTGet Transcript. integration node, httpRequest. 1 incoming and 1 outgoing connections.STEP 05Get TranscriptINTEGRATIONHTTPREQUEST1 IN / 1 OUTAdjust Transcript Format. transform node, code. 1 incoming and 1 outgoing connections.STEP 06Adjust Transcript FormatTRANSFORMCODE1 IN / 1 OUTCreate Description. OpenAI node, openAi. 1 incoming and 1 outgoing connections.STEP 07Create DescriptionOPENAIOPENAI1 IN / 1 OUTYT Tags. ai node, agent. 2 incoming and 1 outgoing connections.STEP 08YT TagsAIAGENT2 IN / 1 OUTYT Title. OpenAI node, openAi. 1 incoming and 1 outgoing connections.STEP 09YT TitleOPENAIOPENAI1 IN / 1 OUTUpdate Video's Metadata. integration node, youTube. 1 incoming and 1 outgoing connections.STEP 10Update Video's MetadataINTEGRATIONYOUTUBE1 IN / 1 OUTDelete File from Upload Folder (Optional). Google Drive node, googleDrive. 1 incoming and 0 outgoing connections.OUTCOMEDelete File from Upload F…GOOGLE DRIVEGOOGLEDRIVE1 IN / 0 OUT2.5FlashPrev. Google AI node, lmChatGoogleGemini. 0 incoming and 1 outgoing connections.DEPENDENCY · DEPTH 12.5FlashPrevGOOGLE 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.12 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

New Video?

10 Execution Links1 Support Dependency
  1. Start

    New Video?

    Trigger

  2. Step 2

    Download New Video

    Integration

  3. Step 3

    Upload Video to Youtube

    Integration

  4. Step 4

    ApifyToken

    Transform

  5. Step 5

    Get Transcript

    Integration

  6. Step 6

    Adjust Transcript Format

    Transform

  7. Step 7

    Create Description

    AI reasoning

  8. Step 8

    YT Tags

    AI reasoning

  9. Step 9

    YT Title

    AI reasoning

  10. Step 10

    Update Video's Metadata

    Integration

  11. Outcome

    Delete File from Upload Folder (Optional)

    Integration

Attached dependencies

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

1 node
  • 2.5FlashPrev

    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.