$cat connect/n8n.md

Automate MDflow with n8n.

npm · community node · Pro

Wire your markdown workspace into n8n — the fair-code workflow automation tool with 500+ integrations. The n8n-nodes-mdflow community node lets a workflow create, update, move, and share MDflow documents, manage folders and workspaces, and react the moment new content appears — no glue code, no bespoke API client.

The package ships two nodes:

  • MDflow — an action node with 22 operations across Documents, Folders, Workspaces, and Shares.
  • MDflow Trigger — starts a workflow when a new document, folder, or workspace appears.
Under review — available now: n8n-nodes-mdflow is published on npm and submitted for n8n's community-node verification. You don't have to wait for the listing — install it today straight from npm by its package name (see below).

The node is free and open source (MIT). It talks to MDflow through the authenticated HTTP API, which is a Pro feature — so the MDflow account you connect needs MDflow Pro.

$open n8n

The MDflow node on your canvas

n8n — MDflow node (create: document)
The MDflow node in the n8n workflow editor: an 'On form submission' trigger wired to an MDflow 'Create a document' action, with the node's 22 actions listed in the node-details panel.
Illustration — a form submission feeding an MDflow Create a document action. The panel on the right lists the node's 22 actions.
$ls nodes/

Two nodes, one workspace

The action node exposes the whole MDflow object model as ordinary n8n operations — pick a resource, then an operation, and map your workflow data onto the fields.

FieldWhat to enter
DocumentCreate · Delete · Get · Get Many · Move · Rename · Set Sharing · Update Body
FolderCreate · Delete · Get · Get Documents · Get Many · Update
WorkspaceCreate · Delete · Get Many · Update
ShareAdd · Get Many · Remove · Remove All

The MDflow Trigger node polls for new content, so a workflow can fire the instant something is created:

  • New Document — watches a folder.
  • New Folder — watches an optional workspace, or the whole account.
  • New Workspace — watches the whole account.
$why n8n

Why connect MDflow to n8n?

  • 500+ integrations, no code. Everything n8n already connects to — forms, databases, GitHub, CRMs, Slack, email, RSS, webhooks — can now read from and write to your markdown workspace.
  • Two-way, not just a sink. The node has full read and write access: pull a document's body into a workflow, transform it, and write it straight back.
  • Event-driven. The trigger node turns “a new document landed” into the start of an automation — index it, back it up, notify a channel, kick off a review.
  • A workspace your AI agents use. The MDflow node works as a tool for n8n AI Agents, so an agent can manage the same markdown your team edits on the web.
  • One account, every surface. The documents you automate here are the same ones you reach on the web, on mobile, in the VS Code extension, and over the MCP server.
$install

Install the node and connect

1

Install the community node

In n8n, open Settings → Community Nodes → Install, enter the package name, and confirm. On a fresh self-hosted instance you can also install it from the command line into your n8n data folder.

$npm package
n8n-nodes-mdflow

Follow n8n's community-nodes installation guide if you need the exact steps for your setup. The package lives on npm and its source is on GitHub.

2

Create an MDflow API credential

The node authenticates with a Personal Access Token. In n8n, add a new MDflow API credential and paste the token in.

FieldWhat to enter
Personal Access TokenCreate a token (mdf_…) at mdflow.cz/settings and paste it into the credential. Token creation and API access require MDflow Pro.
MDflow Pro required: The node reads and writes through MDflow's HTTP API, which is Pro-gated. A free token cannot be created, and API requests return Pro plan required until the account is upgraded to Pro (€4.99/month, 7-day free trial).
3

Build your first workflow

Drop the MDflow node onto the canvas, choose a resource and operation — say Document → Create — pick the target folder, map your body text, and run it. Reach for the MDflow Trigger node instead when you want the workflow to start from new MDflow content.

$use cases

What you can build

  • Capture forms as markdown. An n8n form or a webhook submission becomes a formatted document in the right folder — the exact flow shown above.
  • Build a knowledge base on a schedule. Pull from GitHub issues, a database, RSS, or a CRM, render the result as markdown, and create or update documents so your workspace stays an up-to-date, agent-readable source of truth.
  • Publish and announce automatically. Create a document, use Set Sharing to publish it at a link, then post that link to Slack, Discord, or email in the same run.
  • React to new content. Let MDflow Trigger fire on a new document to back it up, index it elsewhere, or notify a reviewer.
  • Send scheduled digests. A cron trigger gathers the day's data, writes a markdown report into MDflow, and shares the rendered page — a standing daily brief with no manual step.
$ai agents

Give n8n AI Agents a workspace

MDflow is built for people and AI agents, and n8n is where the two meet. There are two ways to put your markdown in front of an agent:

  • As an AI Agent tool. Connect the MDflow node to an n8n AI Agent node's tool input and the agent can create, read, update, and share documents as part of its reasoning.
  • Over the remote MCP server. For free-form access, point n8n's MCP Client Tool node at MDflow's hosted server — https://mdflow.cz/api/mcp — and the agent gets the full MCP toolset, including mdflow_get_context retrieval ranked by folder descriptions.
Same markdown, both sides: An agent writing over MCP and a teammate editing on the web touch the same documents — folder descriptions give the agent scoped context, and every write keeps MDflow's version history.
$man notes

Notes & limits

  • Update Body replaces the whole body. To append instead, Get the document first and concatenate in an expression before the Update Body operation.
  • Size limits. Document bodies are capped at 500 KiB and folder descriptions at 5,000 characters — the same limits as everywhere else in MDflow.
  • Duplicate names are auto-suffixed. The server disambiguates duplicate document titles and folder names with a numeric suffix and returns the final name.
  • Triggers poll. The trigger node checks for new content on n8n's schedule rather than receiving a push, so expect it to fire within a polling interval, not instantly.