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

Daily Order Summary Email Workflow

Daily Order Summary Email Workflow is a 8-node automation blueprint connecting Airtable, Gmail. Inspect its trigger, execution graph, branches, and implementation requirements.

AirtableGmail

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.

8

Nodes

6

Links

2

Run groups

Connected tools

2 integrations

  • Airtable
  • Gmail

Canvas controls

Fit wide systems, then zoom into any run group.

Daily Order Summary Email Workflow execution lanes2 run groups containing 8 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 OUTSet Order Fields. transform node, set. 1 incoming and 1 outgoing connections.STEP 02Set Order FieldsTRANSFORMSET1 IN / 1 OUTStore Order. Airtable node, airtable. 1 incoming and 0 outgoing connections.OUTCOMEStore OrderAIRTABLEAIRTABLE1 IN / 0 OUTEveryday at 7PM. trigger node, scheduleTrigger. 0 incoming and 1 outgoing connections.STARTEveryday at 7PMTRIGGERSCHEDULETRIGGER0 IN / 1 OUTYesterday Date. transform node, code. 1 incoming and 1 outgoing connections.STEP 02Yesterday DateTRANSFORMCODE1 IN / 1 OUTAirtable Get Today's Orders. Airtable node, airtable. 1 incoming and 1 outgoing connections.STEP 03Airtable Get Today's OrdersAIRTABLEAIRTABLE1 IN / 1 OUTHTML. integration node, html. 1 incoming and 1 outgoing connections.STEP 04HTMLINTEGRATIONHTML1 IN / 1 OUTSend to Gmail. Gmail node, gmail. 1 incoming and 0 outgoing connections.OUTCOMESend to GmailGMAILGMAIL1 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.8 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

Webhook

2 Execution Links

  1. Start

    Webhook

    Trigger

  2. Step 2

    Set Order Fields

    Transform

  3. Outcome

    Store Order

    Integration

02

Run Group

Everyday at 7PM

4 Execution Links

  1. Start

    Everyday at 7PM

    Trigger

  2. Step 2

    Yesterday Date

    Transform

  3. Step 3

    Airtable Get Today's Orders

    Integration

  4. Step 4

    HTML

    Integration

  5. Outcome

    Send to Gmail

    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