Zoho CRM automations

On Zoho CRM's Standard edition, the daily credit cap is 100,000 regardless of how many user licenses you have — and all active automations across every platform share that pool. Zapier has explicitly warned that lower-plan orgs can support roughly only two concurrent Zaps triggering off Zoho before hitting limits. If you run Zapier alongside Make or Pipedream workflows simultaneously, you'll exhaust the shared credit quota faster than any single platform's dashboard will show you, leading to silent workflow failures mid-day.

Access tokens expire after exactly one hour, and you can only generate 10 new tokens per refresh token within any 10-minute window. A bulk sync job that stalls or processes slowly — common when hitting the sub-concurrency cap of 10 on bulk insert/update calls — can cause the automation platform to request a new token mid-job and trigger the 'Access Denied' throttle error. This affects n8n self-hosted setups particularly, since token refresh is managed locally, but it can also silently stall Make scenarios and Pipedream workflows if the retry logic doesn't account for Zoho's token generation limits.

Zoho's webhook retry behavior is minimal: if the first notification fails, there is one automatic retry after 15 minutes, with no further retries and no email alert. At high record volumes, a temporary outage or slow response from your receiving endpoint (on Zapier, Make, Power Automate, or Pipedream) will produce a gap in your downstream data with no built-in dead-letter queue on Zoho's side. Combined with the 10-field payload cap per webhook, high-volume pipelines that depend on webhook freshness — like lead routing or deal stage syncing — need explicit reconciliation logic to catch missed events.