✅ 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 |
Follow the general Zoho OAuth setup guide to create your OAuth application. When selecting scopes, make sure to include the People-specific scopes listed in the Common Scopes section below.
Zoho 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 |
Follow the general Zoho OAuth setup guide to create your OAuth application. When selecting scopes, make sure to include the People-specific scopes listed in the Common Scopes section below.
Zoho 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.