Skip to Workflow Atlas
Playbook AtlasWorkflow Atlas
Workflow blueprintBrowse workflows
ETL PipelineAI systemIntermediate

Automated Image Email Sender

Automated Image Email Sender is a 6-node automation blueprint connecting Gmail API. Inspect its trigger, execution graph, branches, and implementation requirements.

Gmail 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

  • Gmail

Canvas controls

Fit wide systems, then zoom into any run group.

Automated Image Email Sender 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.When clicking "Test workflow". trigger node, manualTrigger. 0 incoming and 1 outgoing connections.STARTWhen clicking "Test workf…TRIGGERMANUALTRIGGER0 IN / 1 OUTMessage settings. transform node, set. 1 incoming and 1 outgoing connections.STEP 02Message settingsTRANSFORMSET1 IN / 1 OUTGet image. integration node, httpRequest. 1 incoming and 1 outgoing connections.STEP 03Get imageINTEGRATIONHTTPREQUEST1 IN / 1 OUTConvert image to base64. integration node, extractFromFile. 1 incoming and 1 outgoing connections.STEP 04Convert image to base64INTEGRATIONEXTRACTFROMFILE1 IN / 1 OUTCompose message. transform node, set. 1 incoming and 1 outgoing connections.STEP 05Compose messageTRANSFORMSET1 IN / 1 OUTSend message. integration node, httpRequest. 1 incoming and 0 outgoing connections.OUTCOMESend messageINTEGRATIONHTTPREQUEST1 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

When clicking "Test workflow"

5 Execution Links

  1. Start

    When clicking "Test workflow"

    Trigger

  2. Step 2

    Message settings

    Transform

  3. Step 3

    Get image

    Integration

  4. Step 4

    Convert image to base64

    Integration

  5. Step 5

    Compose message

    Transform

  6. Outcome

    Send message

    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