imperal.io
  • How it works
  • Use cases
  • Technology
  • Pricing
Login
Webbee AIWebbee Codeimperal-mcpDevelopers & SDKSecurity & Vault
Add an app · Marketplace
imperal.ioICNLI Cloud OS

One OS for everything you run. Webbee is your agent inside it, she does the work, you stay in control.

Product
  • Webbee
  • Webbee Code
  • Imperal MCP
  • Marketplace
  • Use cases
  • Pricing
  • Open panel
Resources
  • Security
  • Technology
  • Success stories
  • Blog
Developers
  • Developers
  • Docs
  • Quick start
  • SDK reference
  • Developer portal
Company
  • About
  • Contact
  • Legal
Open protocol
  • ICNLI
  • SDK on GitHub
© 2026 Imperal, Inc. · ICNLI published at icnli.org under CC BY-SA 4.0
TermsPrivacy
  1. Home
  2. /
  3. Marketplace
  4. /
  5. Vikunja Tasks Connector

Vikunja Tasks Connector Extension

⚡ Productivity·by dmitrii·v3.45.0
Pay per use10-80 tok/action
Open in panel
0 capabilities5,261 actions9 installs

About this extension

Kanban task manager connecting to your own Vikunja instance - create, assign, filter tasks and manage projects and labels.

What you get

Every capability exposed by Vikunja Tasks Connector, metered per action and guarded by the two-step safety protocol.

  • connect_vikunjawrite

    Connect a user's Vikunja instance via username + password. The password is forwarded to the backend service once, exchanged for a long-lived Personal Access Token, and discarded. Only the encrypted PAT is stored. Returns base_url + username on success.

  • connect_vikunja_with_patwrite

    Advanced connect: user pastes a pre-existing Vikunja Personal Access Token (Settings → API tokens in their Vikunja UI). The PAT is encrypted on bridge and stored at rest.

  • disconnect_vikunjadestructive

    Disconnect from the user's Vikunja: revoke the stored API token in their instance and delete the local connection record.

  • get_connection_statusread

    Check whether the user has a Vikunja connected (read-only - never echoes the API token). Returns connected: bool plus base_url and username when connected.

  • create_taskwrite

    Create a new task in a project. Pass project_name (e.g. 'webhostmost tasks') or project_id. The assignee field handles assignment internally - do NOT add a separate assign_task step. priority must be an integer: 0=none 1=low 2=medium 3=high 4=urgent 5=critical. due_date must be full ISO 8601 with time (e.g. '2026-06-15T00:00:00Z'), never a bare date.

  • update_taskwrite

    Update any fields of a task (title, description, due_date, priority, percent_done, bucket, etc.).

  • complete_taskwrite

    Mark a task as done (done=true, percent_done=1.0).

  • uncomplete_taskwrite

    Reopen a task - mark it as not done (done=false, percent_done=0). Inverse of complete_task.

  • delete_taskdestructive

    Permanently delete a task. Cannot be undone.

  • delete_tasksdestructive

    Delete multiple tasks at once. Pass task_ids (list of integers) OR task_titles (list of names). When using task_titles, optionally pass project_name to narrow the search. Use when user asks to delete 2+ tasks in one request.

  • complete_taskswrite

    Mark MULTIPLE tasks as done at once. Pass task_ids (list of integers) OR task_titles (list of names). When using task_titles, optionally pass project_name to narrow the search. Use when the user asks to complete/close 2+ tasks in one request.

  • uncomplete_taskswrite

    Reopen MULTIPLE completed tasks at once. Pass task_ids (list of integers) or task_titles (list of names). This is also the batch inverse of complete_tasks.

  • create_subtaskwrite

    Create a subtask under a parent task. Returns the new subtask's task_id.

  • list_subtasksread

    List all subtasks of a given task, including their done/pending status.

  • toggle_checklist_itemwrite

    Check or uncheck a TipTap checklist item in a task description. Use item_index (0-based) from the visible checklist order.

  • get_taskread

    Get full details of a single task by ID: title, description, done status, due date, priority, assignees, labels, and project. Use this to verify task state before updating, or when user asks about a specific task.

  • create_projectwrite

    Create a new project (kanban board). Returns project_id.

  • update_projectwrite

    Update project title, description, or color.

  • archive_projectwrite

    Archive a project (is_archived=true) - hide from active views but keep data.

  • delete_projectdestructive

    Permanently delete a project with all its tasks. Cannot be undone.

  • list_labelsread

    List all labels on this Vikunja instance. Returns label_id and title. Call this first when the user refers to a label by name - then use the returned label_id in add_label.

  • create_labelwrite

    Create a new label with title and optional hex color. Returns label_id.

  • delete_labeldestructive

    Permanently delete a label - removes it from all tasks.

  • list_projectsread

    List all active (non-archived) projects. Returns project_id and title. ALWAYS call this first when the user refers to a project by name - then use the returned project_id in list_project_buckets, filter_tasks, or create_task.

  • list_project_bucketsread

    List kanban columns (buckets) for a project - their names, IDs, and task counts. Use ONLY when the user asks WHAT BUCKETS OR COLUMNS EXIST in a project. Does NOT return task content - use get_bucket_tasks for that. Pass project_name (e.g. 'webhostmost tasks') OR project_id.

  • get_bucket_tasksread

    Get tasks from a specific kanban bucket/column. Use when the user asks WHAT TASKS ARE IN a named bucket (e.g. 'what tasks are in Backlog?', 'show me the To-Do column', 'tasks in Corporate Tasks bucket'). Do NOT use to list all buckets - use list_project_buckets for that. Pass bucket_name (resolved automatically) OR bucket_id. project_name and project_id are optional - omit to search across all projects.

  • count_tasks_per_bucketread

    Count tasks in every kanban bucket for a project - returns per-bucket totals (total, done, pending) and project-level totals. Use when the user asks 'how many tasks', 'сколько задач', 'how many tasks are in each bucket', 'total tasks in project X', 'сколько всего задач'. Pass project_name (e.g. 'WebHostMost Tasks') or project_id. Counts are exact - queried directly from the database, no pagination limits.

  • rename_bucketwrite

    Rename a kanban bucket (column) or update its WIP limit. Requires project_id and bucket_id - use list_project_buckets() first if you only know the bucket name.

  • create_bucketwrite

    Create a new kanban column (bucket) in a project. Requires project_id - use list_projects() first if you only know the project name. Optional WIP limit: 0 means no limit.

  • delete_bucketdestructive

    Delete a kanban column (bucket) from a project. Irreversible - tasks in the deleted column are moved to the project's default column, not deleted. Requires project_id and bucket_id - call list_project_buckets() first if you only know the name.

  • list_project_tasksread

    List tasks in a specific project (paginated - default 50/page, max 200). Use when the user wants to SEE task titles/details, NOT to count tasks. For counting ('how many tasks', 'сколько задач') use count_tasks_per_bucket instead - this function returns a page, not the total. Pass project_name (e.g. 'WebHostMost Tasks') or project_id.

  • get_projectread

    Get metadata for a single project - id, title, description, color, archived status. Pass project_id OR project_name (e.g. 'WebHostMost Tasks'). Use when user asks about a specific project or you need its ID from a name.

  • delete_projectsdestructive

    Permanently delete MULTIPLE projects at once, each with ALL its tasks. Pass project_ids (list of integers) OR project_names (list of names). Requires an explicit confirm=true on a second call; the first call only previews which projects would be deleted. Cannot be undone.

  • assign_taskwrite

    Assign a person to a task. Pass task_name + assignee_query directly - do NOT call find_task or get_named_bucket_tasks first. If multiple tasks share the same name, also pass bucket_name to pick the right one. The bridge resolves assignee_query (name or email) to a Vikunja user ID automatically.

  • unassign_taskwrite

    Remove a Vikunja user (by integer user ID) from a task's assignee list.

  • add_labelwrite

    Attach an existing label (by integer label_id) to a task (by integer task_id). If you only know the label name, call create_label or ask the user for the numeric label_id - Vikunja addresses labels by ID, never by name.

  • remove_labelwrite

    Detach a label (by integer label_id) from a task (by integer task_id).

  • set_due_datewrite

    Set or change due date of a task. Pass integer task_id and due_date as ISO 8601 UTC string (e.g. '2026-04-25T12:00:00Z'). Convert relative dates ('Friday', 'tomorrow') in user's timezone first.

  • set_prioritywrite

    Set task priority - integer 0 (none) to 5 (critical). Pass integer task_id.

  • move_to_projectwrite

    Move a task to another project. Pass integer task_id and integer project_id, or pass project_name (e.g. 'webhostmost tasks') to resolve automatically.

  • move_to_bucketwrite

    Move a task to another kanban bucket (column). Pass integer task_id and integer bucket_id, or pass bucket_name + project_name (e.g. 'To-Do', 'webhostmost tasks') to resolve automatically.

  • search_vikunja_usersread

    Search for Vikunja users by name or email fragment - use this before assign_task to discover who is available, or when the user asks who they can assign tasks to. Pass empty query to list all known users on the Vikunja instance.

  • list_project_membersread

    List the members of a specific project (its assignable users - owner plus user/team shares). Use this when the user asks who is on a named project, e.g. 'who is on the WebHostMost Tasks team', 'участники проекта X', 'кто работает над проектом'. Pass project_name when you only know the name; it is resolved automatically. Prefer this over search_vikunja_users when the user names a project - it is project-scoped rather than instance-wide.

  • move_tasks_to_bucketwrite

    Move MULTIPLE tasks to the same kanban bucket (column) at once. Pass task_ids (list of integers) OR task_titles (list of names), plus bucket_id OR bucket_name + project_name. Use when the user asks to move 2+ tasks to a column in one request.

  • list_my_tasksread

    List tasks with optional Vikunja filter syntax. Examples: `done = false`, `priority >= 3 && due_date < now + 7d`.

  • list_overdueread

    List all overdue tasks (done=false AND due_date in the past).

  • list_todayread

    List tasks due today (done=false AND due_date between start-of-day and end-of-day).

  • list_upcomingread

    List tasks due in the next 7 days (done=false AND due_date between now and now+7d).

  • find_taskread

    Search tasks by title substring. Returns matching tasks with their integer task_id and project_id. Call this first when the user mentions a task by name and you don't have its integer ID - never invent task_id.

  • filter_tasksread

    Filter tasks with Vikunja expression. Operators: = != > < >= <= in like. Logical: && ||. Time helpers: now, now/d, now+7d, now-3d. Fields: title, description, done, due_date, start_date, end_date, priority, project_id, percent_done.

  • add_commentwrite

    Add a comment to a task (markdown supported).

  • mention_userwrite

    Mention a user in a task comment. Vikunja auto-links '@username' and notifies. Use when user wants to notify/loop in someone.

  • list_commentsread

    List all comments on a task.

  • update_commentwrite

    Edit the text of an existing comment on a task.

  • delete_commentdestructive

    Permanently delete a comment from a task. Cannot be undone.

  • delete_commentsdestructive

    Delete MULTIPLE comments on a task at once. Pass comment_ids to delete specific ones, or omit comment_ids entirely to delete EVERY comment on the task. Pass task_id, or task_name (+ optional bucket_name to disambiguate) to resolve it by title. Use when the user asks to delete 2+ comments, or 'delete all comments on task X'.

  • add_commentswrite

    Add MULTIPLE comments to a task at once, in order. Pass task_id, or task_name (+ optional bucket_name to disambiguate) to resolve it by title. Use when the user asks to post 2+ comments in one request, e.g. a simulated work log.

  • ai_breakdown_taskwrite

    Break a task into subtasks using AI. Fetches the task title and description, generates N actionable subtask titles, then creates each as a real Vikunja subtask. Use when user says 'break this task into subtasks', 'разбей задачу', 'create a plan', or similar. Returns the list of created subtask IDs and titles.

  • upload_task_attachmentwrite

    Attach a file (photo, PDF, doc) to a task. Vikunja stores the file itself (max 20MB). Use when the user wants to attach/upload a photo or file to a task.

  • list_task_attachmentsread

    List all attachments (files/photos) on a task.

  • delete_task_attachmentdestructive

    Remove a file attachment from a task. Cannot be undone.

  • delete_task_attachmentsdestructive

    Remove SEVERAL file attachments from a task at once. Pass task_id and attachment_ids (list of integers from list_task_attachments). Use when the user wants to remove 2+ attachments in one request. Cannot be undone.

  • get_notification_statusread

    Check whether live Vikunja notifications (assigned/commented) are enabled.

  • enable_task_notificationswrite

    Turn on live notifications from your Vikunja - get notified in Imperal (bell/telegram, per your notification settings) when someone assigns you a task or comments on one. Registers a webhook on every one of your current Vikunja projects automatically - no manual setup needed. Projects created after enabling won't be covered until you disable and re-enable.

  • disable_task_notificationswrite

    Turn off live Vikunja notifications and remove the webhooks from your Vikunja projects.

Related extensions

More extensions in Productivity ready to enable in one click.

  • NotesPersonal notes with folders, tags, full-text search, and trash management for your workspace.
  • Mail ClientMulti-provider email client - Google, Microsoft, Yahoo, IMAP. Inbox, send, reply, forward, search, archive, manage emails, contacts, custom folders/labels. Gmail batchModify for instant bulk operat...
  • Article WriterAI-powered WordPress content studio: keyword research, SE Rankings tracking, AI article writing with SEO optimization, and one-click publishing to WordPress.
  • Google Drive ConnectorRead and edit Google Docs, Google Sheets, and Google Slides, and read/write plain text files, stored in the user's Google Drive. Nothing is stored on Imperal - content is fetched live and written s...

Ready to use Vikunja Tasks Connector?

Enable Vikunja Tasks Connector in your Imperal workspace in one click - 10,000 free starter credits included.

Open in panel