Trilium
Use flowbot trilium for capability trilium.
CLI root is trilium — do not invent flowbot trilium unless cli.md lists it as an alias.
Prefer the workflows below; load references/cli.md only when you need a flag or subcommand not covered here.
JSON fields: Note ids are strings; create requires an existing parent_note_id.
Setup
- Ensure CLI auth:
flowbot login - Set server via
FLOWBOT_SERVER_URLor--server-url; optional--profile,--debug/-d - Prefer
-o jsonwhen parsing results programmatically - Destructive commands often need
-y/--yesin non-interactive sessions — check cli.md - Token scopes:
service:trilium:read/service:trilium:write
Workflows
Create a note under a parent
When a user wants to add a new trilium note:
flowbot trilium list --limit 20- Choose parent_note_id from list/get (ask the user if unclear).
flowbot trilium create -t "<title>" -c "<content>" -p <parent_note_id>- Report back with the note ID.
Find and read a note
When a user wants to search and open trilium notes:
flowbot trilium search -q "<keywords>"flowbot trilium get <id>flowbot trilium content get <id>- Present the note content to the user.
Troubleshooting
| Error | Fix |
|---|---|
| not logged in | flowbot login |
| server URL is required | set FLOWBOT_SERVER_URL or pass --server-url |
| permission denied / 403 | token missing service scopes (service:trilium:read / service:trilium:write) |
| hung waiting for confirm | pass -y when the command supports it (see cli.md) |
| empty results | provider not configured, wrong id/name, or empty dataset |
| unknown command | use flowbot trilium, not the capability id as the CLI verb |