Reference · built on requestConnectorCRM & sales

Zoho CRM

Leads, contacts, accounts, deals, and activities from Zoho CRM modules, with notifications when records change.

Request accessPricing ↗

About

Zoho CRM organizes customer data into modules: Leads, Contacts, Accounts, Deals, Tasks, Meetings, Calls, Quotes, Sales Orders, Invoices, and custom modules. The v8 API reaches each at {api-domain}/crm/v8/{module_api_name}, with Bulk Read jobs for large exports, a Query API that accepts SELECT syntax, and a Notification API that posts near-real-time record events to your URL.

Fibric subscribes to those notifications and reads the modules you choose. An operator proposes an update to a record or a follow-up task, and a person approves it inside the API credit and concurrency limits your edition already carries.

This is a reference listing. It documents what Fibric would read from Zoho CRM 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

  • Records from Leads, Contacts, Accounts, Deals, Tasks, Meetings, Calls, Quotes, Sales Orders, Invoices, and custom modules through GET /crm/v8/{module_api_name}
  • Records changed since a timestamp through the If-Modified-Since header, up to 200 per page
  • Bulk Read jobs that export a module to CSV asynchronously, with a callback when the job completes
  • Notification channels for {module_api_name}.create, .edit, .delete, or .all, narrowed to chosen fields
  • Module, field, layout, custom view, and related list definitions through the Metadata APIs
  • Filtered record sets through the Query API using SELECT syntax

Proposed actions

  • Target capability: propose an update to Lead, Contact, or Deal records, at most 100 records per call
  • Target capability: propose a Task or Call record against a Deal or Contact for the owner
  • Target capability: propose converting a Lead once a person approves the account and deal it will create
  • Target capability: propose adding or removing tags on records, at most 500 per call

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

What you can build

  • Reply to a web lead within the hour

    A Leads.create notification arrives at your URL. The operator reads the record and its source, drafts a first reply and a Task, and a person sends both.

    With Lead Response

  • Chase quotes before they lapse

    Quotes nearing the expiry date you track are listed with the related Deal and Contact. The operator drafts the reminder, and the owner sends it.

    With Quote Expiry

  • Find duplicate leads before they split a pipeline

    New Leads are compared with existing Leads and Contacts on email, phone, and company. The operator proposes which record to keep, and a person confirms.

    With Duplicate Lead

  • Keep the renewal calendar honest

    Deals and Accounts with a renewal date inside your horizon are pulled with their last Call and Meeting. The operator proposes the outreach and its owner.

    With Renewal Reminder

Requirements

  • A Zoho CRM edition with API credits for the read volume: Free gets 5,000 per day, paid editions start at 50,000 plus a per-user amount
  • OAuth scopes for each module read or written, plus ZohoCRM.notifications.ALL for change notifications
  • A callback URL for notifications, re-enabled at least weekly since a channel expires after at most one week
  • ZohoCRM.bulk.READ if history loads use Bulk Read jobs
Authentication
OAuth 2.0 with scopes in the form service_name.scope_name.operation_type, for example ZohoCRM.modules.leads.READ or ZohoCRM.notifications.ALL; access tokens last one hour and refresh tokens persist until revoked.

Limits

  • API credits per 24 hours: 5,000 on Free; 50,000 plus 250, 500, 1,000, or 2,000 per user on Standard, Professional, Enterprise, and Ultimate
  • Concurrent calls: 5, 10, 15, 20, or 25 by edition, with a sub-concurrency limit of 10 for calls such as Convert Lead and composite requests
  • Get Records returns at most 200 per page, 2,000 without a page_token, and 100,000 with one; tokens expire after 24 hours
  • A notification channel expires after at most one week and defaults to one hour if no expiry is given

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 CRM ↗

Questions and answers

How does the connector learn about changes in Zoho CRM?
Through the Notification API. A channel subscribes to events such as Leads.create or Deals.edit, optionally limited to specific fields, and Zoho posts to your URL. Channels expire after at most one week, so the connector renews them on a schedule.
What does a read cost against the daily API credits?
Editions get a daily credit pool: 5,000 on Free, and 50,000 plus a per-user amount on paid editions. Insert, update, and upsert cost 1 credit per 10 records. Bulk Read jobs move large exports off the per-call budget.
Which modules can the connector read?
Get Records supports Leads, Accounts, Contacts, Deals, Campaigns, Tasks, Cases, Meetings, Calls, Solutions, Products, Vendors, Price Books, Quotes, Sales Orders, Purchase Orders, Invoices, Appointments, Services, and custom modules.
Ask about Zoho CRM

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 CRM 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