Skip to Workflow Atlas
Playbook AtlasWorkflow Atlas
Workflow blueprintBrowse workflows
Event-Driven AutomationAI systemIntermediate

YouTube Subscription Video Notifier

YouTube Subscription Video Notifier is a 12-node automation blueprint connecting YouTube API, SMTP for email. Inspect its trigger, execution graph, branches, and implementation requirements.

YouTube APISMTP for email

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.

12

Nodes

11

Links

1

Flows

Connected tools

2 integrations

  • YouTube API
  • SMTP for email
YouTube Subscription Video Notifier execution lanes1 connected flows containing 12 workflow nodes and 11 visible links. Solid lines are execution links and dashed lines are support dependencies. Focus any node to inspect its immediate path.Schedule Trigger. trigger node, scheduleTrigger. 0 incoming and 1 outgoing connections.Schedule TriggerTRIGGERSCHEDULETRIGGER0 IN / 1 OUTGet my subscriptions. integration node, httpRequest. 1 incoming and 1 outgoing connections.Get my subscriptionsINTEGRATIONHTTPREQUEST1 IN / 1 OUTCheck for errors. decision node, if. 1 incoming and 2 outgoing connections.Check for errorsDECISIONIF1 IN / 2 OUTIf the HTTP request failed, throw the error. integration node, stopAndError. 1 incoming and 0 outgoing connections.If the HTTP request faile…INTEGRATIONSTOPANDERROR1 IN / 0 OUTSplit out subscriptions to process individually. transform node, splitOut. 1 incoming and 1 outgoing connections.Split out subscriptions t…TRANSFORMSPLITOUT1 IN / 1 OUTOnly keep channels with unwatched videos. decision node, filter. 1 incoming and 1 outgoing connections.Only keep channels with u…DECISIONFILTER1 IN / 1 OUTFilter out channels. decision node, filter. 1 incoming and 1 outgoing connections.Filter out channelsDECISIONFILTER1 IN / 1 OUTGet latest 15 videos of each channel. integration node, rssFeedRead. 1 incoming and 1 outgoing connections.Get latest 15 videos of e…INTEGRATIONRSSFEEDREAD1 IN / 1 OUTKeep only videos published since last run. decision node, filter. 1 incoming and 1 outgoing connections.Keep only videos publishe…DECISIONFILTER1 IN / 1 OUTGet video details. integration node, youTube. 1 incoming and 1 outgoing connections.Get video detailsINTEGRATIONYOUTUBE1 IN / 1 OUTFilter out shorts. decision node, if. 1 incoming and 1 outgoing connections.Filter out shortsDECISIONIF1 IN / 1 OUTSend an email for each new video. integration node, emailSend. 1 incoming and 0 outgoing connections.Send an email for each ne…INTEGRATIONEMAILSEND1 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.12 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

Schedule Trigger

11 Execution Links

  1. Start

    Schedule Trigger

    Trigger

  2. Step 2

    Get my subscriptions

    Integration

  3. Step 3

    Check for errors

    Decision

  4. Step 4

    If the HTTP request failed, throw the error

    Integration

    Split out subscriptions to process individually

    Transform

  5. Step 5

    Only keep channels with unwatched videos

    Decision

  6. Step 6

    Filter out channels

    Decision

  7. Step 7

    Get latest 15 videos of each channel

    Integration

  8. Step 8

    Keep only videos published since last run

    Decision

  9. Step 9

    Get video details

    Integration

  10. Step 10

    Filter out shorts

    Decision

  11. Outcome

    Send an email for each new video

    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