Projects and tasks

Factuarea now manages work as well as invoices, and the whole task module is on the v1 contract: projects with a board of columns, tasks linked to your invoices, quotes and contacts, time logged and billed, an agenda and the events to follow it all. It is 80 new endpoints under seven resources, included in every plan. Start with the Projects and tasks guide.

• Seven resources — /v1/projects (22 endpoints: projects, board columns, custom fields, the JSON export and import of tasks, the time summary and the invoice of billable hours), /v1/tasks and its subresources (45: search, board position, comments, relations, labels, links, attachments, upload links, time entries, the timer and the activity log), /v1/task-labels (5), /v1/task-timers (2), /v1/users (2), /v1/notifications (3) and /v1/agenda (1). Every endpoint is listed below.
• Nine new scopes — projects:read|write|delete, tasks:read|write|delete, users:read and notifications:read|write. projects:* and tasks:* belong to the tasks module: a key with those scopes for a company without it is rejected with scope_not_allowed_by_plan. users:read and notifications:* are cross-cutting. The projects:delete and tasks:delete scopes are API-key-only: an OAuth consent never grants them. Nine operations are irreversible and require an Idempotency-Key; see Scopes & irreversibility.
• Deleting a column that has tasks — DELETE /v1/projects/{project}/columns/{column} takes a move_to_column_id query parameter: the column of the same project that receives the tasks, in their order, in the same transaction. Without it, a column with tasks returns 409 column_has_tasks.
• A task born already linked — POST /v1/tasks accepts an entity_link with the type and the id of an invoice, quote, contact or any other linkable entity, and links it in the same transaction. If the entity does not exist or belongs to another company, the call returns 404 linked_entity_not_found and the task is not created.
• tasks_count on task labels — every label of the catalog reports how many tasks carry it, archived ones included.
• Task keys — DEV-12 resolves through POST /v1/tasks/find-by-key, and a key keeps working after the task moves to another project or its project changes key.
• Logged time is not the working-day register — a task_time_entry is time spent on a task, with its own tasks:* scopes and task_time_entry.* events. It never appears in the Time tracking register (/v1/time-entries). See Time logged on tasks.
• 21 new events — task.* (created, updated, deleted, status_changed, completed, assigned, unassigned, moved, due_soon and overdue), task_comment.*, task_time_entry.* and project.*. Completing a task emits both task.status_changed and task.completed, and the latter is a subset of the former. See Events.
• 80 new MCP tools — 22 for projects, 52 for tasks, 2 for users, 3 for notifications and 1 for the agenda, in step with the API. The catalog now has 552 tools; the delete tools are API-key-only. See the tool catalog.
• CLI — factuarea projects, tasks, task-labels, task-timers, users, notifications and agenda, with their scopes and confirmations. See the CLI guide.
• Automations — the 21 events are new triggers, and four new actions create and change tasks: create_task, change_task_status, assign_task and add_task_comment. In a portfolio (cartera) rule, only create_task is accepted among them. See Automations.
• Error codes — 46 new codes under the Tasks group, each with its cause and what to do, and 18 under Task Integrations for the flows that live in the app. See Tasks error codes.
• Availability — the tasks module is included in every plan. The task integrations with code forges and chat tools, the iCal feeds and the public board exist only in the app; the integrations need the Empresario or Enterprise plan.