Skip to main content

Vikunja

Integrates with self-hosted Vikunja instances for project management automation. Provides full CRUD operations for projects, tasks, labels, and task comments via the Vikunja REST API. Tasks support priority levels (1-5), due dates, descriptions, color coding, and done status. Projects support nesting via parent project IDs, identifiers, and archiving. All nodes accept either a reusable Client ID from Connect or direct credentials (API token + instance URL).

NamespaceRobomotion.Vikunja
Version1.1.0
CategoryProject Management, Productivity
Nodes18

Nodes

NodeDescription
ConnectOpens a connection to Vikunja and returns a Client ID.
DisconnectCloses a Vikunja connection.
Create TaskCreates a task in Vikunja.
Get TaskGets a task in Vikunja.
List TasksLists tasks in Vikunja.
Update TaskUpdates a task in Vikunja.
Delete TaskDeletes a task in Vikunja.
Add CommentAdds a comment in Vikunja.
List CommentsLists comments in Vikunja.
Create ProjectCreates a project in Vikunja.
Get ProjectGets a project in Vikunja.
List ProjectsLists projects in Vikunja.
Update ProjectUpdates a project in Vikunja.
Delete ProjectDeletes a project in Vikunja.
Create LabelCreates a label in Vikunja.
List LabelsLists labels in Vikunja.
Delete LabelDeletes a label in Vikunja.
ToolkitExposes this package's operations to an AI Agent as a single tool.

Connecting

This package has a Connect node. Run it once at the start of your flow; it returns a Client ID that the other nodes take as input. Pair it with Disconnect so the connection is released when the flow ends.

Credentials belong in a Vault rather than typed into the node.

AI Agent tools

17 of these nodes are exposed as tools an AI Agent can call directly: Connect, Disconnect, Create Task, Get Task, List Tasks, Update Task, Delete Task, Add Comment, List Comments, Create Project, Get Project, List Projects, Update Project, Delete Project, Create Label, List Labels, Delete Label.

About this page

Generated from the package spec that the Flow Designer itself loads, so the node list and every property below match the version above exactly.

It does not yet include worked examples or service-specific guidance — those are written by hand, and a plausible-sounding guess in a reference page is worse than an honest gap. If you build something useful with this package, the community is the place to share it.