Skip to Workflow Atlas
Playbook AtlasWorkflow Atlas
Index held / follow enabledBrowse archive
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

Live system map / verified archive

The entire automation, wired and inspectable.

Brand marks identify the operational stack. Focus or select any node to isolate its real incoming and outgoing connections.

6

Nodes

6

Edges

5

Zones

System stack

2 integrations

  • Gmail
  • Slack
Gmail to Slack Expense Notifier interactive execution graphStructural view of 6 workflow nodes and 6 visible connections. Focus any node to inspect its connected path. Parameters and credentials are intentionally excluded.Receive certain keyword Gmail Trigger. Gmail node, gmailTrigger. 0 incoming and 1 outgoing connections.Receive certain keyword G…GMAILGMAILTRIGGER0 IN / 1 OUTClick to Test Flow. trigger node, manualTrigger. 0 incoming and 1 outgoing connections.Click to Test FlowTRIGGERMANUALTRIGGER0 IN / 1 OUTGet emails from Gmail with certain subject. Gmail node, gmail. 1 incoming and 1 outgoing connections.Get emails from Gmail wit…GMAILGMAIL1 IN / 1 OUTLoop Over Items. integration node, splitInBatches. 3 incoming and 1 outgoing connections.Loop Over ItemsINTEGRATIONSPLITINBATCHES3 IN / 1 OUTExtract Price, Shop, Date, TIme. transform node, set. 1 incoming and 1 outgoing connections.Extract Price, Shop, Date…TRANSFORMSET1 IN / 1 OUTSend to Slack with Block. Slack node, slack. 1 incoming and 1 outgoing connections.Send to Slack with BlockSLACKSLACK1 IN / 1 OUT

Signal inspector

Focus, hover, or select a node to illuminate its real path.

triggeraidecisiontransformintegration
Scroll horizontally to inspect every zone.verified structural metadata · graph 82e938f9b7d74a7bEnter or click to lock · Escape to clear

Structured review

Read the workflow as a system, not a node dump.

The archived graph is grouped into operational zones, then checked against the controls needed to adapt the pattern safely. Every count below is derived from the normalized record.

01

Entry signals

2 nodes

Events, schedules, and unconnected roots that can start an execution.

Click to Test Flow

Trigger

Receive certain keyword Gmail Trigger

Trigger

02

Data & operations

4 nodes

Transformations and external-system actions that move the work forward.

Loop Over Items

Integration

Get emails from Gmail with certain subject

Integration

Extract Price, Shop, Date, TIme

Transform

Send to Slack with Block

Integration

03

Intelligence & routing

0 nodes

Model calls and control points that interpret, branch, or govern the run.

No nodes observed in this zone
04

Terminal actions

0 nodes

Nodes with no visible outgoing edge: the workflow’s observable outcomes.

No nodes observed in this zone

Provenance boundary

Inspectable does not mean redistributable.

This page publishes structural metadata extracted from a local workflow archive. Parameters, credential references, code bodies, and downloadable JSON are excluded. The route can enter indexing only after a graph match and quality gate; source licensing remains a separate promotion gate.

Graph match
exact
Quality score
14 / 14
Raw download
Held
Crawler state
Follow

Adjacent systems

Keep tracing the stack.

Related records are ranked by shared integrations and graph quality.

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