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

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.

13

Nodes

14

Links

1

Run groups

Connected tools

2 integrations

  • Gmail
  • Obsidian

Canvas controls

Fit wide systems, then zoom into any run group.

Obsidian Email Automation with Attachments execution lanes1 run groups containing 13 workflow nodes and 14 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 OUTCheck if attachments exist. decision node, if. 1 incoming and 2 outgoing connections.STEP 02Check if attachments existDECISIONIF1 IN / 2 OUTSeparate attachment data. transform node, splitOut. 1 incoming and 1 outgoing connections.STEP 03Separate attachment dataTRANSFORMSPLITOUT1 IN / 1 OUTCheck if it is a test. decision node, if. 1 incoming and 2 outgoing connections.STEP 03Check if it is a testDECISIONIF1 IN / 2 OUTFix Base64 string. transform node, set. 1 incoming and 1 outgoing connections.STEP 04Fix Base64 stringTRANSFORMSET1 IN / 1 OUTTest Succesfull. trigger node, respondToWebhook. 1 incoming and 0 outgoing connections.STEP 04Test SuccesfullTRIGGERRESPONDTOWEBHOOK1 IN / 0 OUTEmail Without Attachments. Gmail node, gmail. 1 incoming and 1 outgoing connections.STEP 04Email Without AttachmentsGMAILGMAIL1 IN / 1 OUTProcess Each Attachment. integration node, splitInBatches. 2 incoming and 2 outgoing connections.STEP 05Process Each AttachmentINTEGRATIONSPLITINBATCHES2 IN / 2 OUTPrepare Attachments for Email. transform node, aggregate. 1 incoming and 1 outgoing connections.STEP 06Prepare Attachments for E…TRANSFORMAGGREGATE1 IN / 1 OUTConvert Attachment to File. integration node, convertToFile. 1 incoming and 1 outgoing connections.STEP 07Convert Attachment to FileINTEGRATIONCONVERTTOFILE1 IN / 1 OUTEmail With Attachments. Gmail node, gmail. 1 incoming and 1 outgoing connections.STEP 08Email With AttachmentsGMAILGMAIL1 IN / 1 OUTGet date. integration node, dateTime. 2 incoming and 1 outgoing connections.STEP 09Get dateINTEGRATIONDATETIME2 IN / 1 OUTRespond to Obsidian. trigger node, respondToWebhook. 1 incoming and 0 outgoing connections.OUTCOMERespond to ObsidianTRIGGERRESPONDTOWEBHOOK1 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.13 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

14 Execution Links

  1. Start

    Webhook

    Trigger

  2. Step 2

    Check if attachments exist

    Decision

  3. Step 3

    Separate attachment data

    Transform

    Check if it is a test

    Decision

  4. Step 4

    Fix Base64 string

    Transform

    Test Succesfull

    Trigger

    Email Without Attachments

    Integration

  5. Step 5

    Process Each Attachment

    Integration

  6. Step 6

    Prepare Attachments for Email

    Transform

  7. Step 7

    Convert Attachment to File

    Integration

  8. Step 8

    Email With Attachments

    Integration

  9. Step 9

    Get date

    Integration

  10. Outcome

    Respond to Obsidian

    Trigger

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