Docs workflow nodes
Read and write Docs workspace pages from inside a Workflow.
Four nodes let a Workflow read and write Docs workspace pages. They appear under the Docs category in the node palette. Every operation is tenant-scoped, and writes made by a node are attributed to the system (they have no end-user context).
All node inputs are ordinary flow values — wire them from earlier nodes or set them inline.
Targeting a page
Append to Page, Get Page, and Replace Page Content act on an existing page. You identify it in one of two ways:
pageId— the page's id (for example, from aCreate Pagenode's output or a/docs/<id>URL).pageTitle— an exact title match.
If both are supplied, pageId wins. If neither resolves to an existing page, the node errors.
Create Page
Creates a new page.
| Input | Required | Description |
|---|---|---|
title | yes | The new page's title. |
contentMarkdown | no | Initial content (markdown). |
parentId | no | Id of the parent page to nest under. |
parentTitle | no | Parent by exact title (used if parentId is absent). |
icon | no | An emoji/icon for the page. |
Outputs: pageId, url (the page's /docs/:id path).
Use it to spin up a page from a Workflow — for example, create a "Meeting notes" page when a calendar event starts.
Append to Page
Appends markdown to the end of an existing page, leaving the rest untouched.
| Input | Required | Description |
|---|---|---|
pageId / pageTitle | one required | The target page (see Targeting a page). |
markdown | yes | The markdown to append. |
Output: pageId.
Use it to accumulate into a running log — append a line each time a Workflow runs.
Get Page
Reads an existing page.
| Input | Required | Description |
|---|---|---|
pageId / pageTitle | one required | The target page. |
Outputs: title, markdown (the page's content), plainText (content with formatting stripped).
Use it to pull a page's content into a flow — for example, feed a doc into an LLM node as context.
Replace Page Content
Overwrites a page's entire content with new markdown.
| Input | Required | Description |
|---|---|---|
pageId / pageTitle | one required | The target page. |
markdown | yes | The new content (replaces everything). |
Output: pageId.
Use it to keep a generated page in sync — for example, regenerate a status page on a schedule.
Notes
- Content is markdown end-to-end, so what a node writes is exactly what you see in the editor, and page links written as
[title](ezflow-doc:<id>)become clickable chips and backlinks. - Because
pageTitlematches by exact title, prefer stable, unique titles when targeting pages by title — or target bypageIdto be unambiguous.