Projects and tasks shared by your team, your workflows, and AI agents.
Tasks lives next to your workflows in the dashboard. Projects hold tasks on a board, in a list, or on a calendar; everyone sees their own work in My Tasks. A task's history shows every change and who made it: a person, a workflow run (with a link to the run), or an AI agent. Tasks, projects, and members are free.
Invite people from Settings → Members. An invitation is for one email address and works for 7 days. Each person has a role:
A project is visible to the whole workspace or private to its project members, who can be project admins (settings and members), members (edit tasks), or viewers. A workspace can have up to 5 people besides its owner on Free and 100 on Pay As You Go.
In the Studio, choose the Kovca Tasks trigger and the event: created, updated, status changed, assigned, priority changed, due date changed, due date reached, overdue, labels changed, field changed, commented, subtask completed, completed, reopened, archived, submitted. Filter by project, the column a task moves into or out of, label, priority, or a custom field's value. The trigger's output has the task, what changed, and who changed it. Runs start a few seconds after the change. A person can also start a project's chosen workflow on a task with Run automation.
Automations never run in loops:
An automation keeps running the version it was activated on. After you publish a new version, choose Publish & update (or Update in the Automation menu) to move it; until then the Studio shows which version it runs. Publishing checks that the trigger's project and every column the workflow names exist. Deleting a project lists the automations that listen to it; they stop and show that they need attention until you choose another project or turn them off.
Kovca Tasks actions create, update, move, assign, comment on, complete, and reopen tasks; add files, subtasks, and checklist items; set custom fields; link tasks; and read a task, a search, or a project's columns. These steps use no credits; a run started by a task event pays the usual 1-credit run fee, like any automation run (see pricing). Each change shows the workflow run that made it. When a run that changed a task fails, the task shows it and the assignee is notified; the task's column doesn't change.
Turn on Show the request in Tasks in an Approval step and choose a project. When a run reaches the step, Kovca creates a task for the request (or uses an existing task you reference) and the assignee, or a project admin, can approve, reject, or request changes with a comment right in the task. The step's output adds task_key, comment, and changes_requested, and decided_via is task. Decisions made from the link, the Inbox, or the API are shown on the task too. Completing a task never approves its request. When the step sends requested changes to a coding agent, requesting changes asks the agent to revise its work instead, and the task asks for the decision again once it's done.
The MCP server has task tools: reading projects, tasks, and history with Run access; creating, updating, commenting, subtasks, links, and starting automations with Author access; and deciding approvals in tasks with Publish access (when the step allows API decisions). An agent's changes appear in history as an AI agent's and start task workflows like a person's.
Unlike workflow runs, tasks store what you write in them: titles, descriptions, comments, field values, and files. They're never sent in webhooks or kept in run records, and they're deleted with their project, workspace, or your account.