✅ Authorization
✅ Read & write data
Tools | Status |
---|---|
Pre-built integrations | 🚫 (time to contribute: <48h) |
API unification | ✅ |
2-way sync | ✅ |
Webhooks from Nango on data modifications | ✅ |
Real-time webhooks from 3rd-party API | 🚫 (time to contribute: <48h) |
Proxy requests | ✅ |
✅ Observability & data quality
Tools | Status |
---|---|
HTTP request logging | ✅ |
End-to-type type safety | ✅ |
Data runtime validation | ✅ |
OpenTelemetry export | ✅ |
Slack alerts on errors | ✅ |
Integration status API | ✅ |
✅ Customization
Tools | Status |
---|---|
Create or customize use-cases | ✅ |
Pre-configured pagination | ✅ |
Pre-configured rate-limit handling | 🚫 (time to contribute: <48h) |
Per-customer configurations | ✅ |
No pre-built integration yet (time to contribute: <48h)
Pre-Requisites | Status | Comment |
---|---|---|
Paid dev account | ✅ Not required | Free Zoho account is sufficient for development. |
Paid test account | ✅ Not required | Free Zoho account is sufficient for testing. |
Partnership | ✅ Not required | |
App review | ✅ Not required | No review process for OAuth apps. |
Security audit | ✅ Not required |
Zoho offers multiple services, each with its own API. In Nango, these are represented as separate providers:
While each Zoho service has its own specific API endpoints and scopes, the OAuth setup process is similar across all Zoho services. This guide covers the general setup process for Zoho OAuth applications.
Create a Zoho account
Access the Zoho API Console
Create a new client
https://api.nango.dev/oauth/callback
Select the appropriate scopes
Note: Each Zoho service has its own set of scopes. Refer to the specific service documentation for details on available scopes.
Obtain your OAuth credentials
After creating your client, you’ll receive:
Make sure to store these securely, especially the Client Secret, as you’ll need them when configuring your integration in Nango.
Configure your integration in Nango
When setting up your Zoho integration in Nango:
Next
Follow the Quickstart.
Each Zoho service has its own set of scopes. Here are some common scopes for popular Zoho services:
Zoho CRM
ZohoCRM.modules.ALL
- Access to all CRM modulesZohoCRM.settings.ALL
- Access to all CRM settingsZohoCRM.users.ALL
- Access to all CRM usersZoho Books
ZohoBooks.fullaccess.all
- Full access to Books dataZohoBooks.contacts.READ
- Read access to contactsZohoBooks.invoices.READ
- Read access to invoicesZoho Desk
Desk.tickets.ALL
- Access to all Desk ticketsDesk.contacts.READ
- Read access to Desk contactsDesk.search.READ
- Search functionality in DeskZoho Mail
ZohoMail.accounts.READ
- Read access to mail accountsZohoMail.messages.ALL
- Access to all mail messagesAaaServer
AaaServer.profile.READ
- Read access to user profileAaaServer.profile.UPDATE
- Update access to user profileZoho uses datacenter-specific URLs for authentication. Make sure to use the correct datacenter domain extension (com
, eu
, in
, com.cn
, com.au
) based on where your user’s account is registered.
Zoho has rate limits that vary by service. Check the specific service documentation for details.
If your application needs to access multiple Zoho services, you need to request scopes for each service during the authorization process.
For production applications, consider implementing multi-datacenter support to handle users from different regions.
✅ Authorization
✅ Read & write data
Tools | Status |
---|---|
Pre-built integrations | 🚫 (time to contribute: <48h) |
API unification | ✅ |
2-way sync | ✅ |
Webhooks from Nango on data modifications | ✅ |
Real-time webhooks from 3rd-party API | 🚫 (time to contribute: <48h) |
Proxy requests | ✅ |
✅ Observability & data quality
Tools | Status |
---|---|
HTTP request logging | ✅ |
End-to-type type safety | ✅ |
Data runtime validation | ✅ |
OpenTelemetry export | ✅ |
Slack alerts on errors | ✅ |
Integration status API | ✅ |
✅ Customization
Tools | Status |
---|---|
Create or customize use-cases | ✅ |
Pre-configured pagination | ✅ |
Pre-configured rate-limit handling | 🚫 (time to contribute: <48h) |
Per-customer configurations | ✅ |
No pre-built integration yet (time to contribute: <48h)
Pre-Requisites | Status | Comment |
---|---|---|
Paid dev account | ✅ Not required | Free Zoho account is sufficient for development. |
Paid test account | ✅ Not required | Free Zoho account is sufficient for testing. |
Partnership | ✅ Not required | |
App review | ✅ Not required | No review process for OAuth apps. |
Security audit | ✅ Not required |
Zoho offers multiple services, each with its own API. In Nango, these are represented as separate providers:
While each Zoho service has its own specific API endpoints and scopes, the OAuth setup process is similar across all Zoho services. This guide covers the general setup process for Zoho OAuth applications.
Create a Zoho account
Access the Zoho API Console
Create a new client
https://api.nango.dev/oauth/callback
Select the appropriate scopes
Note: Each Zoho service has its own set of scopes. Refer to the specific service documentation for details on available scopes.
Obtain your OAuth credentials
After creating your client, you’ll receive:
Make sure to store these securely, especially the Client Secret, as you’ll need them when configuring your integration in Nango.
Configure your integration in Nango
When setting up your Zoho integration in Nango:
Next
Follow the Quickstart.
Each Zoho service has its own set of scopes. Here are some common scopes for popular Zoho services:
Zoho CRM
ZohoCRM.modules.ALL
- Access to all CRM modulesZohoCRM.settings.ALL
- Access to all CRM settingsZohoCRM.users.ALL
- Access to all CRM usersZoho Books
ZohoBooks.fullaccess.all
- Full access to Books dataZohoBooks.contacts.READ
- Read access to contactsZohoBooks.invoices.READ
- Read access to invoicesZoho Desk
Desk.tickets.ALL
- Access to all Desk ticketsDesk.contacts.READ
- Read access to Desk contactsDesk.search.READ
- Search functionality in DeskZoho Mail
ZohoMail.accounts.READ
- Read access to mail accountsZohoMail.messages.ALL
- Access to all mail messagesAaaServer
AaaServer.profile.READ
- Read access to user profileAaaServer.profile.UPDATE
- Update access to user profileZoho uses datacenter-specific URLs for authentication. Make sure to use the correct datacenter domain extension (com
, eu
, in
, com.cn
, com.au
) based on where your user’s account is registered.
Zoho has rate limits that vary by service. Check the specific service documentation for details.
If your application needs to access multiple Zoho services, you need to request scopes for each service during the authorization process.
For production applications, consider implementing multi-datacenter support to handle users from different regions.