Workflow Results to Markdown Notes in Your Obsidian Vault, via Google Drive
Configured with Agent, Execute Workflow Trigger, Google Drive, OpenAI Chat Model, and additional nodes. Review the connections and setup before adapting this template.
Node categories in this workflow
- Files / media
- Trigger
- Routing
- AI & models
- Transform
Icons describe general node roles, inferred from node types. Inspect the parameters for the configured action.
Drag to pan; use + and − to zoom. Reconstructed from the exported node positions; nothing runs here. Dashed lines represent non-main connections. Full node names and notes appear below.
How it works
The exported workflow contains the following configured nodes. Their connections are shown above; inspect the JSON for the complete logic, expressions, and external actions.
| Node | Category | Type | Operation |
|---|---|---|---|
| Save Markdown file | Files / media | Google Drive | createFromText |
| Receive results from any workflow | Trigger | Execute Workflow Trigger | See node parameters |
| If the input has binary attachment | Routing | If | See node parameters |
| Write Zettlekasten note from input1 | AI & models | Agent | See node parameters |
| Structured Output Parser | Transform | Output Parser Structured | See node parameters |
| OpenAI Chat Model | AI & models | OpenAI Chat Model | See node parameters |
| Restructure JSON | Transform | Edit Fields | See node parameters |
| Structured Output Parser1 | Transform | Output Parser Structured | See node parameters |
| OpenAI Chat Model1 | AI & models | OpenAI Chat Model | See node parameters |
| Write YAML Frontmatter | AI & models | Agent | See node parameters |
| Save attachment | Files / media | Google Drive | See node parameters |
Setup
- Download the JSON and import it into an isolated n8n instance. Leave the workflow inactive.
- Connect your own credentials through n8n’s credential store. Replace
REPLACE_WITH_*values with your resource identifiers. - Inspect API destinations, Code nodes, database queries, file paths, and outbound actions.
- Run with synthetic data and harmless destinations. Enable triggers only after checking the actual outputs.
Requirements
An n8n instance with the listed node types and compatible versions. Service-connected workflows may require accounts, credentials, or paid APIs.
Credential types declared in the source
googleDriveOAuth2ApiopenAiApi
Workflow notes
Connect folder to Obsidian Vault
Connect folder to Obsidian Vault
Setup Instructions:
- Create a folder in your Google Drive that syncs with your desktop.
- Configure the Google Drive node as follows:
- Assign the newly created folder as the parent-folder.
- Specify the filename, appending .md (e.g.,
{{ $json.title }}.md). - Add Markdown content, including optional YAML Frontmatter, in the File Content field.
- Establish a Symlink between the Google Drive folder and a new folder in your Obsidian Vault.
Workflow results to Obsidian Vault
Workflow results to Obsidian Vault
This template automatically creates and updates notes in your Obsidian Vault in real-time from n8n workflow results. Markdown files and attachments saved in Google Drive instantly appear in your Obsidian Vault.
Send the output of any workflow to the Execute Workflow Trigger beow
Create Symlink
Create Symlink
Create a symlink to integrate your Google Drive Desktop folder with your Obsidian Vault, ensuring that workflow-generated notes stored in Google Drive instantly appear and update in Obsidian.
-
Open an Administrator Command Prompt: Press
Win + S, typecmd, right-click on Command Prompt, and selectRun as Administrator. -
Get Folder Paths: Identify the source path: This is the existing Google Drive folder you want to link to. Decide on the target path: This is the folder in your Obsidian Vault where the symlink will be created. Ensure the Target Path Does Not Already Exist
-
Run the mklink Command: Use the following syntax to create a directory symbolic link:
mklink /D "Target Path" "Source Path"The target path is the location in your Vault where the symlink will be created. The source path is the Google Drive folder. -
Example Command:
mklink /D "C:\Users\YourName\Vault\OtherFolder" "C:\Users\YourName\Google Drive\MyFolder"
Optional - Use AI Agents for Note Composition
Optional - Use AI Agents for Note Composition
Instead of directly using JSON parameters for the note's title, YAML frontmatter, and content, you can utilize AI agents to compose these elements. This approach involves inserting the AI-assisted workflow between the webhook and the Google Drive note, instead of the direct connection.
Workflow Results to Markdown Notes in Your Obsidian Vault, via Google Drive
Workflow Results to Markdown Notes in Your Obsidian Vault, via Google Drive
Purpose and structure
This folder contains the Workflow Results to Markdown Notes in Your Obsidian Vault, via Google Drive workflow. Its executable nodes use agent, executeWorkflowTrigger, googleDrive, if, lmChatOpenAi, outputParserStructured, set. The table and connection map below are derived from the JSON, not an inferred guarantee of behavior.
Setup
Import inactive. Configure your own credentials and replace REPLACE_WITH_* values. Review external destinations and Code nodes before running.
Entry points
Receive results from any workflow
Verification
Sanitized source candidate; not runtime-tested. This overview is generated from node metadata. Read the folder README for the connection map, credential types, and license.
Attribution
https://github.com/Zie619/n8n-workflows/blob/94007c1445d9258a7da116646b79473e7c7c3282/workflows/Executeworkflow/0947_Executeworkflow_Stickynote_Automate_Triggered.json MIT; preserve source notices.