Skip to content

Connect n8n to Folio

To connect n8n to Folio, create a Bearer Auth credential with a personal token, then add the MCP Client Tool node to an AI Agent node. Set the endpoint to your Folio's /mcp address, the transport to HTTP Streamable and authentication to Bearer. The agent answers from your wiki with the page link, or a workflow writes rows and pages.

Sign-in: Token

Updated

Two workflows

Ask:

Ask the wiki: a message arrives, an AI Agent node with the MCP Client Tool searches and reads Folio, and replies with the answer and a link. Event to row: a release or an alert arrives, and a workflow adds a row to the Incident log table.

The reply carries a link to the page. The table shows the new row at once, and Git history shows the write with the token owner's name.

Connect

What you need

  • n8n 1.104 or newer. Streamable HTTP in the MCP nodes arrived in 1.104 and is the default from 1.114.
  • A Folio token. For a workflow that only answers questions, use read. For one that writes, create the token under a separate Folio user with the editor role in one space.
  • n8n must be able to reach Folio. n8n Cloud reaches only a public address. A self-hosted n8n can reach Folio on the same network.

Steps

  1. Step 1: In n8n create a credential of type Bearer Auth. Paste the Folio token. A Header Auth credential with the name Authorization and the value Bearer folio_pat_... works too.

  2. Step 2: For an AI agent: add the MCP Client Tool node to the Tool input of an AI Agent node. Set the endpoint to your Folio address, the server transport to HTTP Streamable and authentication to Bearer, with your credential.

    Endpoint
    https://your-folio.example.com/mcp
  3. Step 3: Under Tools to Include choose Selected and pick only what the agent needs: search_pages and read_page for answers, plus folio_table_insert if it should log a row. With All, the agent sees every tool, including the ones that write.

  4. Step 4: For a plain workflow step, use the MCP Client node instead. It lists the server's tools and runs the one you pick. A scheduled digest, for example, calls folio_table_query and sends the rows to Slack or email.

  5. Step 5: To start from a ready-made workflow, import github-issue-to-table-row.json or weekly-summary-page.json from the Folio repository (workflow menu, Import from file). Then pick your Bearer credential in the Folio nodes and set your Folio address.

  6. Step 6: Before an agent writes to a table, make it call folio_table_schema. Column ids and the options of select and status columns are not guessable from names.

Try it against the demo

The demo does not issue personal tokens, so n8n cannot connect to it. Run your own Folio, which takes a few minutes with Docker, or try the demo from Claude or ChatGPT.

What the agent can do

Folio exposes 49 tools over MCP. Full reference.

Reading (23)
Reading (23)What it does
list_spacesSpaces you can see, with your role in each
list_treeThe page tree of a space
list_templatesThe page templates of a space
search_pagesFull-text search across the pages you can open, with filters
read_pageA page as Markdown, with its metadata; a form's fields, a canvas's outline, a base's YAML
resolve_folio_urlA Folio link to the page it points at
get_backlinksPages that link to a page
page_historyThe Git commits that touched a page
page_at_shaA page as it was at a given commit
get_page_metadataA page's headings, block ids, tags, properties and links
list_unresolved_linksLinks in a space that point at nothing
list_orphansPages in a space that nothing links to
get_graphThe link graph of a space, or the neighbourhood of one page
list_tagsThe tag tree of a space with page counts
list_propertiesThe property keys in use, with their types and sample values
query_baseThe rows of an Obsidian base view
folio_table_listData tables in a space
folio_table_schemaA table's real columns, types and options
folio_table_queryTable rows with filter, sort and search
searchThe same search under the name ChatGPT deep research looks for
fetchA page by the id that search returned, as Markdown
check_page_writing_rulesThe space's writing rules and a page's text, so the agent can check the page against them; nothing is changed
list_commentsThe inline comment threads of a page, with the text each is attached to and its status
Writing (26)
Writing (26)What it does
create_pageA new document with text, or a table with columns
update_pageReplace the text of a page; merges with live editing
create_page_from_templateA new page copied from a template, with date, author and title filled in
save_page_as_templateCopy an existing page into the templates of its space
create_templateA new page template in the space's templates folder
publish_artifactAn interactive HTML page, such as a Claude artifact, published as a page
create_boardA whiteboard from a short description of boxes and arrows
update_boardReplace a whiteboard's scene
board_opsAlign, distribute, move or auto-layout board elements
convert_canvas_to_boardAn editable whiteboard made from an Obsidian canvas
create_formA form with its fields, and the table its answers go to
update_formChange a form's fields; the paired table follows
folio_table_createA table with an explicit schema
folio_table_add_columnA new column
folio_table_update_columnRename a column or change its type or options
folio_table_delete_columnA column and its values
folio_table_save_viewA saved view with its filter, sort and hidden columns
folio_table_delete_viewA saved view
folio_table_insertNew rows
folio_table_updateCells, by row id or by filter
folio_table_deleteRows, by id
rename_tagRename a tag across a space, in one commit
set_page_propertiesA page's properties, for any kind of page
save_baseCreate an Obsidian base or replace its YAML
add_commentA new inline comment thread on a passage of a page
reply_commentA reply in an existing comment thread
  • Reading needs the read scope. Writing needs write. With read only, every tool that changes something refuses to run.
  • All 49 tools carry read-only or destructive annotations, so a client can ask before it writes.
  • An agent cannot manage access rights, invite people, or rename and delete spaces. Those actions exist only in the browser.
  • A write reaches the page file at once. The Git commit follows after about 90 seconds of quiet, so page history can lag behind an edit.
  • The direction is n8n to Folio. Folio has no webhooks or outgoing events yet, so an edit in Folio cannot start a workflow. To react to changes, poll on a schedule: query a table or search pages.

Security

  • A personal access token carries the rights of the person who created it, narrowed by its scope. Give an agent its own Folio user with the editor role in the spaces it needs, and create the token there. Do not hand an agent an administrator's token.
  • Use a read token when the agent only answers questions.
  • The token is shown once. Keep it in an environment variable or the client's secret store, not in a file that goes to Git. Delete it under API tokens when you stop using it.
  • Administrative routes are cookie-only: no token reaches them with any scope.
  • Page content is data, not instructions. Folio's tool descriptions say so, but the real protection is rights. An agent that also has a shell and write access can be misled by a page someone else wrote, so give it the narrowest token that does the job.

Limits and honest notes

  • Field labels can differ slightly between n8n versions.
  • Folio has no webhooks or outgoing events.

Read more

Frequently asked questions

How do I connect n8n to an MCP server like Folio?

Create a Bearer Auth credential with the token, add the MCP Client Tool node to an AI Agent node, and set the endpoint to your /mcp address, the transport to HTTP Streamable and authentication to Bearer. You need n8n 1.104 or newer.

Which Folio tools should an n8n agent get?

Under Tools to Include choose Selected. search_pages and read_page are enough for answers; add folio_table_insert if it should log a row. With All, the agent sees every tool, including the ones that write.

Can an edit in Folio start an n8n workflow?

No. Folio has no webhooks or outgoing events yet. The direction is n8n to Folio; to react to changes, poll on a schedule by querying a table or searching pages.