Skip to Workflow Atlas
ETL PipelineAI systemIntermediate

Markdown Notes to Obsidian via Google Drive

Markdown Notes to Obsidian via Google Drive is a 11-node automation blueprint connecting OpenAI, Google Drive. Inspect its trigger, execution graph, branches, and implementation requirements.

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.

11

Nodes

9

Links

2

Run groups

Connected tools

2 integrations

  • OpenAI
  • Google Drive

Canvas controls

Fit wide systems, then zoom into any run group.

Markdown Notes to Obsidian via Google Drive execution lanes2 run groups containing 11 workflow nodes and 9 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 results from any workflow. trigger node, executeWorkflowTrigger. 0 incoming and 2 outgoing connections.STARTReceive results from any …TRIGGEREXECUTEWORKFLOWTRIGGER0 IN / 2 OUTIf the input has binary attachment. decision node, if. 1 incoming and 1 outgoing connections.STEP 02If the input has binary a…DECISIONIF1 IN / 1 OUTSave Markdown file. Google Drive node, googleDrive. 1 incoming and 0 outgoing connections.STEP 02Save Markdown fileGOOGLE DRIVEGOOGLEDRIVE1 IN / 0 OUTSave attachment. Google Drive node, googleDrive. 1 incoming and 0 outgoing connections.OUTCOMESave attachmentGOOGLE DRIVEGOOGLEDRIVE1 IN / 0 OUTWrite Zettlekasten note from input1. ai node, agent. 2 incoming and 1 outgoing connections.STARTWrite Zettlekasten note f…AIAGENT2 IN / 1 OUTWrite YAML Frontmatter. ai node, agent. 3 incoming and 1 outgoing connections.STEP 02Write YAML FrontmatterAIAGENT3 IN / 1 OUTRestructure JSON. transform node, set. 1 incoming and 0 outgoing connections.OUTCOMERestructure JSONTRANSFORMSET1 IN / 0 OUTOpenAI Chat Model. OpenAI node, lmChatOpenAi. 0 incoming and 1 outgoing connections.DEPENDENCY · DEPTH 1OpenAI Chat ModelOPENAILMCHATOPENAI0 IN / 1 OUTStructured Output Parser. ai node, outputParserStructured. 0 incoming and 1 outgoing connections.DEPENDENCY · DEPTH 1Structured Output ParserAIOUTPUTPARSERSTRUCTURED0 IN / 1 OUTOpenAI Chat Model1. OpenAI node, lmChatOpenAi. 0 incoming and 1 outgoing connections.DEPENDENCY · DEPTH 1OpenAI Chat Model1OPENAILMCHATOPENAI0 IN / 1 OUTStructured Output Parser1. ai node, outputParserStructured. 0 incoming and 1 outgoing connections.DEPENDENCY · DEPTH 1Structured Output Parser1AIOUTPUTPARSERSTRUCTURED0 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.11 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 results from any workf…

3 Execution Links
  1. Start

    Receive results from any workflow

    Trigger

  2. Step 2

    If the input has binary attachment

    Decision

    Save Markdown file

    Integration

  3. Outcome

    Save attachment

    Integration

02

Run Group

Write Zettlekasten note from i…

2 Execution Links4 Support Dependencies
  1. Start

    Write Zettlekasten note from input1

    AI reasoning

  2. Step 2

    Write YAML Frontmatter

    AI reasoning

  3. Outcome

    Restructure JSON

    Transform

Attached dependencies

These nodes support the runtime above; they are not additional starts or outcomes.

4 nodes
  • OpenAI Chat Model

    AI reasoning dependency

  • Structured Output Parser

    AI reasoning dependency

  • OpenAI Chat Model1

    AI reasoning dependency

  • Structured Output Parser1

    AI reasoning dependency

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.