Skip to Workflow Atlas
Playbook AtlasWorkflow Atlas
Workflow blueprintBrowse workflows
Event-Driven AutomationAI systemIntermediate

Obsidian Email Automation with Attachments

Obsidian Email Automation with Attachments is a 13-node automation blueprint connecting Gmail, Obsidian. Inspect its trigger, execution graph, branches, and implementation requirements.

GmailObsidian

Interactive system map

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.

13

Nodes

14

Edges

6

Zones

System stack

2 integrations

  • Gmail
  • Obsidian
Obsidian Email Automation with Attachments interactive execution graphStructural view of 13 workflow nodes and 14 visible connections. Focus any node to inspect its connected path. Parameters and credentials are intentionally excluded.Webhook. trigger node, webhook. 0 incoming and 1 outgoing connections.WebhookTRIGGERWEBHOOK0 IN / 1 OUTCheck if attachments exist. decision node, if. 1 incoming and 2 outgoing connections.Check if attachments existDECISIONIF1 IN / 2 OUTCheck if it is a test. decision node, if. 1 incoming and 2 outgoing connections.Check if it is a testDECISIONIF1 IN / 2 OUTTest Succesfull. trigger node, respondToWebhook. 1 incoming and 0 outgoing connections.Test SuccesfullTRIGGERRESPONDTOWEBHOOK1 IN / 0 OUTSeparate attachment data. transform node, splitOut. 1 incoming and 1 outgoing connections.Separate attachment dataTRANSFORMSPLITOUT1 IN / 1 OUTFix Base64 string. transform node, set. 1 incoming and 1 outgoing connections.Fix Base64 stringTRANSFORMSET1 IN / 1 OUTProcess Each Attachment. integration node, splitInBatches. 2 incoming and 2 outgoing connections.Process Each AttachmentINTEGRATIONSPLITINBATCHES2 IN / 2 OUTPrepare Attachments for Email. transform node, aggregate. 1 incoming and 1 outgoing connections.Prepare Attachments for E…TRANSFORMAGGREGATE1 IN / 1 OUTConvert Attachment to File. integration node, convertToFile. 1 incoming and 1 outgoing connections.Convert Attachment to FileINTEGRATIONCONVERTTOFILE1 IN / 1 OUTEmail With Attachments. Gmail node, gmail. 1 incoming and 1 outgoing connections.Email With AttachmentsGMAILGMAIL1 IN / 1 OUTEmail Without Attachments. Gmail node, gmail. 1 incoming and 1 outgoing connections.Email Without AttachmentsGMAILGMAIL1 IN / 1 OUTGet date. integration node, dateTime. 2 incoming and 1 outgoing connections.Get dateINTEGRATIONDATETIME2 IN / 1 OUTRespond to Obsidian. trigger node, respondToWebhook. 1 incoming and 0 outgoing connections.Respond to ObsidianTRIGGERRESPONDTOWEBHOOK1 IN / 0 OUT

Signal inspector

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

triggeraidecisiontransformintegration
Scroll horizontally to inspect every zone.13 connected nodesEnter or click to lock · Escape to clear

Structured review

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

The workflow is grouped into operational zones, then reviewed for the controls needed to adapt the pattern safely.

01

Entry signals

3 nodes

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

Respond to Obsidian

Trigger

Test Succesfull

Trigger

Webhook

Trigger

02

Data & operations

8 nodes

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

Separate attachment data

Transform

Process Each Attachment

Integration

Convert Attachment to File

Integration

Prepare Attachments for Email

Transform

Email With Attachments

Integration

Email Without Attachments

Integration

+ 2 more in system map
03

Intelligence & routing

2 nodes

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

Check if attachments exist

Decision

Check if it is a test

Decision

04

Terminal actions

0 nodes

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

No nodes observed in this zone

Adjacent systems

Keep tracing the stack.

Related workflows share tools and similar system patterns.

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