Sync markdown files from Google Drive to Confluence pages automatically
Ready for 3.0Ready for 3.0. This template uses no nodes that n8n 3.0 removes. No removed nodes, versions or helpers found. Static check, last run 2026-10-19.
What this workflow does
This workflow has 10 nodes and runs on Google Drive events (file created) (plus 1 other trigger). Along the way it connects Google Drive. It also calls api.atlassian.com over HTTP.
How it runs
Trigger: On Google Drive events (file created) (plus 1 other trigger).
- If: checks a condition and branches into true / false
- Download file (Google Drive): download
- Convert file to markdown string (Extract from File): extracts data from a file (text)
- Markdown: converts between Markdown and HTML
- If: checks a condition and branches into true / false
- Create Confluence Page (HTTP Request): calls api.atlassian.com (PUT)
- Get Page ID (HTTP Request): calls an HTTP API
- Update Confluence Page (HTTP Request): calls an HTTP API (PUT)
Services it uses
HTTP calls to: api.atlassian.com
Before you upgrade to n8n 3.0
Nothing in this workflow is removed in n8n 3.0, so it should import and run after the upgrade.
Nodes used (6)
- Google Drive Trigger
n8n-nodes-base.googleDriveTrigger - Google Drive
n8n-nodes-base.googleDrive - Markdown
n8n-nodes-base.markdown - If
n8n-nodes-base.if - Extract from File
n8n-nodes-base.extractFromFile - HTTP Request
n8n-nodes-base.httpRequest
From the author
How it Works Save a .md file to the folder set in the triggers. This workflow will check every hour, convert the md file to HTML, and create a confluence page for it. If the md file is updated or changed in the folder, the workflow will check for a matching…