Projects

The Projects module manages project records, boards, board columns, and project tasks for work that needs more structure than a simple follow-up task.

What it does

Use Projects when a workspace needs structured execution:

Create project containers for client work, product work, marketing work, operations, or implementation plans.
Create boards and columns for status-based work tracking.
Create project tasks linked to boards, columns, owners, due dates, source records, or customer context.
Connect project work to CRM deals, Support tickets, CMS campaigns, Product records, Calendar events, Activity Log entries, and Assets.

Resource model

Resource	Purpose
`projects`	Project containers with status, owner, dates, and metadata.
`project_boards`	Board views for a project.
`project_board_columns`	Ordered board columns such as backlog, active, review, or done.
`project_tasks`	Work items within a project or board.

Project tasks are separate from the core Tasks module. Use core Tasks for lightweight follow-ups and project tasks for work that belongs to a project plan or board.

REST surface

Projects REST endpoints live under /v1/projects...:

GET /v1/projects
POST /v1/projects
PATCH /v1/projects/{project_id}
GET /v1/projects/boards
POST /v1/projects/boards
PATCH /v1/projects/boards/{board_id}
GET /v1/projects/board-columns
POST /v1/projects/board-columns
PATCH /v1/projects/board-columns/{column_id}
GET /v1/projects/tasks
POST /v1/projects/tasks
PATCH /v1/projects/tasks/{project_task_id}

All routes require the Projects module to be enabled for the workspace before scope checks can succeed.

Permissions

Use projects:read to list projects, boards, columns, and project tasks. Use projects:write to create or update project records.

Recommended scoped credentials for project operations:

projects:read
projects:write
tasks:read
tasks:write
activity:write
assets:read

Add CRM, Support, CMS, Products, or Calendar scopes only when project work needs to read or update those records.

Example workflow

Prompt:

Create a client onboarding project, add a board with Backlog, In Progress, Review, and Done columns, create kickoff and asset-review project tasks, and log the project setup activity.

Expected operations:

Create the project.
Create the project board.
Create ordered board columns.
Create project tasks assigned to the right columns.
Link related CRM, Support, CMS, or Asset records when applicable.
Log the setup activity.

Audit and usage

Project writes create audit events and usage events with request IDs. Use request IDs to connect REST calls to project tasks, related CRM or Support records, assets, and Activity Log entries.

Project records are available through REST. Dedicated MCP tools are not listed in the public MCP tool registry for this module. Agent workflows can combine REST project records with MCP tools from Tasks, Activity Log, CRM, Support, CMS, Assets, and Data & Insights.