Reference · built on requestConnectorWork & ticket management

Zoho Projects

Projects, tasklists, tasks, issues, time logs, and status history from Zoho Projects portals through the Zoho Projects API v3.

Request accessPricing ↗

About

Zoho Projects is Zoho's project management product. A portal holds projects; each project holds tasklists, tasks with subtasks and dependencies, issues, milestones, time logs, comments, and custom fields. The API v3 answers under https://projectsapi.zoho.com/api/v3/portal/{portal_id}/ with page-based pagination, ISO 8601 dates, and a filter payload of criteria and a pattern. Zoho marks the earlier REST API for deprecation in favour of V3.

Through Fibric, an operator reads tasks and issues by filter, follows a task's status timeline, and proposes a status change, a comment, a time log, or a blueprint transition. Approved proposals are applied once each and logged with what changed and how to undo it.

This is a reference listing. It documents what Fibric would read from Zoho Projects and what it could propose, based on the vendor's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • Tasks across a portal or project through GET /api/v3/portal/{portal_id}/tasks and /projects/{project_id}/tasks, with page and per_page
  • Task filters as a criteria payload with field_name, criteria_condition, and value, including has_parents and parent_task for subtasks
  • Issues through GET /projects/{project_id}/issues with their resolution, linked issues, associated tasks, and status transitions
  • Tasklists, milestones, and task dependencies, including blocking and waiting tasks
  • A task's status timeline through GET /tasks/{task_id}/status-timeline, and status history at project or portal level
  • Time logs and time log reports at project and portal level, with default approvers
  • Comments and followers on tasks, issues, tasklists, and projects

Proposed actions

  • Target capability: propose a task change through PATCH /api/v3/portal/{portal_id}/projects/{project_id}/tasks/{task_id}
  • Target capability: propose a comment on a task or issue through POST .../tasks/{task_id}/comments or .../issues/{issue_id}/comments
  • Target capability: propose a blueprint transition through POST .../automation/blueprint/{blueprint_id}/transition/{transition_id}/execute after reading next-transitions
  • Target capability: propose a time log through the Add Time Log operation, or a resolution on an issue through POST .../issues/{issue_id}/resolution
  • Target capability: propose a new task or issue through POST .../projects/{project_id}/tasks or .../projects/{project_id}/issues

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Chase overdue tasks

    The operator filters tasks by status and end date, reads each task's status timeline, and proposes a comment to the owner or a date change for your approval.

    With Action Follow-up

  • Sign off time logs

    The operator reads project time logs and the default approver and proposes the entries still unapproved before the period closes.

    With Timesheet Signoff

  • Turn a ticket into an issue

    When a support ticket points at a defect, the operator proposes an issue in the right project with the ticket summary and links it to the related task.

    With Escalation Packet, Ticket Triage

  • Move a task through its blueprint

    For a task idle in one state, the operator reads next-transitions and proposes the blueprint transition to execute, with the during-actions it will trigger.

    With Work Order Aging

Requirements

  • A Zoho Projects portal and its portal_id from GET /api/v3/portals
  • An application registered in the Zoho API console with the scopes the operator needs, requested at consent
  • The base URL for the user's data center, such as projects.zoho.com, projects.zoho.eu, projects.zoho.in, or projects.zoho.com.au; Multi DC support enabled for cross-region users
  • A refresh token, since access tokens expire after the expires_in seconds returned with them
Authentication
OAuth 2.0 through an application registered in the Zoho API console, with scopes such as ZohoProjects.tasks.READ, ZohoProjects.tasks.ALL, ZohoProjects.projects.READ, and ZohoProjects.timesheets.ALL; the token response's location and api_domain pick the data center.

Limits

  • Each API endpoint allows 200 calls in a 2-minute window; exceeding it blocks that endpoint for 10 minutes with a Retry-After header
  • Pages hold 1 to 200 records, default 100; has_next_page in page_info says whether to continue
  • The V3 reference lists Webhooks under Automation but documents only blueprint and custom function endpoints, so changes are read by polling
  • The earlier REST API is marked for deprecation, and its OAuth tokens for Zoho Projects do not work on Zoho BugTracker

Access and pricing

Reference listing. Fibric builds the connector under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.

Request Zoho Projects ↗

Questions and answers

Which API version does this listing follow?
The Zoho Projects API v3 at https://projectsapi.zoho.com/api/v3. Zoho's earlier REST API page states that it will be deprecated soon and asks integrations to move to V3. V3 uses page and per_page pagination, ISO 8601 dates, custom fields by api_name, and a criteria-based filter payload.
How do rate limits work?
Each API can be invoked up to 200 times within a 2-minute window, applied per endpoint. Responses carry RateLimit, RateLimit-Remaining, RateLimit-Window, and RateLimit-Window-Unit headers. Over the limit, that API is blocked for 10 minutes and a Retry-After header gives the seconds remaining. The restriction applies to that API only.
Does Zoho Projects send webhooks?
The V3 reference describes an Automation module covering Blueprints, Custom Functions, Webhooks, Workflow Rules, and Email Alerts, but documents endpoints only for blueprints and custom function execution. This listing therefore reads changes by polling tasks, issues, and status history, and executes transitions through the blueprint endpoint.
Ask about Zoho Projects

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This connector listing is developed, published, and supported by Fibric. It describes integration with Zoho Projects through published interfaces. Third-party names and logos identify the systems an integration connects to; they are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy