n8n node - TEST

Hello community,

Right now evaluating SiYuan. First impression is good !

Also, the availability of the n8n is a huge bonus, ... I built a quick workflow to backup some specific content of Notion to SiYuan, ... Still some bugs in the node, mainly in the way the node outputs are created, ... but this it looks promising.

Also, just wondering if the SiYuan database features will be implemented in the n8n node ? This is required for my project to move away from Notion.

Thanks for the feedback !

image.png

    Related articles

    4 Reply

    Welcome to here!

    Here we can learn from each other how to use SiYuan, give feedback and suggestions, and build SiYuan together.

    Signup About
    Please input reply content ...
    • hsteph
      PRO Author

      Yes, this is the node I'm using : https://github.com/PsycoStea/SiYuan-n8n-nodes

      A lot of outstanding features ! The developer has been super reactive to update it (look at the closed section)

    • MiscReply
    • ACai

      I remember a community member developed an n8n node for SiYuan.

      Of course, you can also use SiYuan's Web API directly.

      For a local-first and open-source note-taking app, you can leverage AI to find the API for any existing feature you want, even if it hasn't been officially documented as a stable API — but you need to be mindful of edge cases.

      1 Reply
      1 Operate
      ACai updated this reply at 2026-05-26 21:50:05
    • hsteph
      PRO Author

      Just sharing an idea here, ... not sure it's realistic

      What about using the solution as a simple database via a very simplified n8n node ?

      This is the idea. Enable Siyuan to be used as a simple key-value storage in a n8n context. All the structure is set already, it's just another view/organisation of what already exists.

      A Notebook is a Database
      A Document is a Table
      A Sub-Document is a Record (and we don't need more levels)

      In terms of n8n node, what we need in a v0 version to test the idea :

      • READ /database/table/record => you get the value (the equivalent of Document/GetId by Path + Get Content)
      • WRITE /database/table/record/value => you write the $value (the equivalent of Document/Create)

      In a v1, we can add options like

      • CREATE TABLE => the equivalent of Document/Create (with an empty sub-content)
      • LIST TABLES => the equivalent of List in Notebooks
      • LIST RECORDS => the equivalent of Get Document tree
      • SELECT FROM => ...

      What about this idea ?