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

Gmail to Slack Expense Notifier

Gmail to Slack Expense Notifier is a 6-node automation blueprint connecting Gmail, Slack. Inspect its trigger, execution graph, branches, and implementation requirements.

GmailSlack

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

6

Links

1

Run groups

Connected tools

2 integrations

  • Gmail
  • Slack

Canvas controls

Fit wide systems, then zoom into any run group.

Gmail to Slack Expense Notifier execution lanes1 run groups containing 6 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.Receive certain keyword Gmail Trigger. Gmail node, gmailTrigger. 0 incoming and 1 outgoing connections.STARTReceive certain keyword G…GMAILGMAILTRIGGER0 IN / 1 OUTClick to Test Flow. trigger node, manualTrigger. 0 incoming and 1 outgoing connections.STARTClick to Test FlowTRIGGERMANUALTRIGGER0 IN / 1 OUTGet emails from Gmail with certain subject. Gmail node, gmail. 1 incoming and 1 outgoing connections.STEP 02Get emails from Gmail wit…GMAILGMAIL1 IN / 1 OUTLoop Over Items. integration node, splitInBatches. 3 incoming and 1 outgoing connections.STEP 03Loop Over ItemsINTEGRATIONSPLITINBATCHES3 IN / 1 OUTExtract Price, Shop, Date, TIme. transform node, set. 1 incoming and 1 outgoing connections.STEP 04Extract Price, Shop, Date…TRANSFORMSET1 IN / 1 OUTSend to Slack with Block. Slack node, slack. 1 incoming and 1 outgoing connections.OUTCOMESend to Slack with BlockSLACKSLACK1 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.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

Receive certain keyword Gmail …

6 Execution Links

  1. Start

    Receive certain keyword Gmail Trigger

    Trigger

    Click to Test Flow

    Trigger

  2. Step 2

    Get emails from Gmail with certain subject

    Integration

  3. Step 3

    Loop Over Items

    Integration

  4. Step 4

    Extract Price, Shop, Date, TIme

    Transform

  5. Outcome

    Send to Slack with Block

    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