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

Google Slides Image Updater

Google Slides Image Updater is a 7-node automation blueprint connecting Google Slides. Inspect its trigger, execution graph, branches, and implementation requirements.

Google Slides

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.

7

Nodes

6

Links

1

Run groups

Connected tools

1 integrations

  • Google Slides

Canvas controls

Fit wide systems, then zoom into any run group.

Google Slides Image Updater execution lanes1 run groups containing 7 workflow nodes and 6 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.Webhook. trigger node, webhook. 0 incoming and 1 outgoing connections.STARTWebhookTRIGGERWEBHOOK0 IN / 1 OUTCheck if all params are provided. decision node, if. 1 incoming and 2 outgoing connections.STEP 02Check if all params are p…DECISIONIF1 IN / 2 OUTRetrieve All Slide Elements. integration node, httpRequest. 1 incoming and 1 outgoing connections.STEP 03Retrieve All Slide ElementsINTEGRATIONHTTPREQUEST1 IN / 1 OUTError Missing Fields. trigger node, respondToWebhook. 1 incoming and 0 outgoing connections.STEP 03Error Missing FieldsTRIGGERRESPONDTOWEBHOOK1 IN / 0 OUTRetrieve matching Images ObjectIds. transform node, code. 1 incoming and 1 outgoing connections.STEP 04Retrieve matching Images …TRANSFORMCODE1 IN / 1 OUTReplace Images. integration node, httpRequest. 1 incoming and 1 outgoing connections.STEP 05Replace ImagesINTEGRATIONHTTPREQUEST1 IN / 1 OUTRespond to Webhook. trigger node, respondToWebhook. 1 incoming and 0 outgoing connections.OUTCOMERespond to WebhookTRIGGERRESPONDTOWEBHOOK1 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.7 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

Respond to Webhook

6 Execution Links

  1. Start

    Webhook

    Trigger

  2. Step 2

    Check if all params are provided

    Decision

  3. Step 3

    Retrieve All Slide Elements

    Integration

    Error Missing Fields

    Trigger

  4. Step 4

    Retrieve matching Images ObjectIds

    Transform

  5. Step 5

    Replace Images

    Integration

  6. Outcome

    Respond to Webhook

    Trigger

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