Help for owners
My app or website no longer syncs leads with Zoho CRM
Short answer
Zoho CRM limits API use by daily credits on a rolling 24-hour window and by simultaneous calls, and its access tokens last only an hour, so a sync needs a refresh token behind it. A sync that wastes credits, runs in parallel or loses its token stops, usually quietly. Check which of these happened.
Does this sound like your situation?
- New leads from my website are not appearing in Zoho CRM.
- The sync worked for weeks and stopped partway through a day.
- Some records arrive and others fail with a too many requests error.
- After an admin changed something in Zoho, the connection asked to sign in again.
- Edits made in Zoho do not reach my app.
Why does this happen?
The daily credit allowance ran out
Zoho CRM counts API credits over a rolling 24-hour window. Most calls cost one credit, some cost more, and inserts, updates and upserts cost one credit per ten records. The daily total depends on the edition and the number of user licenses, and integration tasks from Deluge use the same credits.
Confirmed by zoho.com
Too many calls at the same time
Zoho limits simultaneous active calls per organization and app, with higher limits for higher editions, and a smaller shared limit for heavier calls such as inserting more than 10 records, converting leads or sending mail. When that is reached Zoho returns TOO_MANY_REQUESTS.
Confirmed by zoho.com
There is no per-minute limit, so bursts still hurt
Zoho's page says there are no time-based call limits; only concurrency and the 24-hour credit limit apply. A burst of parallel jobs can therefore trip the concurrency limit even when the daily total is low.
Confirmed by zoho.com
The access token expired and could not be renewed
A Zoho access token is valid for an hour. A refresh token gets new ones and stays valid until the end-user revokes it. If the integration does not renew, or the user who authorised it was removed or revoked it, calls fail until someone authorises again.
Confirmed by zoho.com
Every record sent as its own call
A sync that sends one record per call spends ten times the credits that grouped inserts would, and runs into the concurrency limit sooner.
Confirmed by zoho.com
What can I do about it today?
- Look at the API usage in ZohoAsk a Zoho administrator to open the API usage details and note whether the credits were used up or not.
- Do not reconnect repeatedlySigning in again and again, or restarting the sync many times, burns credits and can add to the problem.
- Find out who authorised the connectionIf that person was removed from Zoho or revoked access, the sync needs a new authorisation by a user you intend to keep.
- Note the last lead that arrivedIts time and name tell your developer where the gap starts.
- Keep the missed leadsExport or save the enquiries from your website for the gap, so they can be sent again.
When should I bring someone in?
- Leads are missing from Zoho and sales has no way to follow them.
- The credits run out every day.
- Both your app and Zoho can change the same record and the data disagrees.
How do I handle it?
- Read Zoho's current limits for your editionI check the credits, concurrency and token rules in Zoho's documentation, and the usage dashboard, to see which limit applies.
- Count credits per recordFrom the logs I measure the cost of one lead, and move to grouped inserts and updates where Zoho allows.
- Queue and cap the parallel callsRecords go through a queue with a fixed number of calls at once, and it pauses on a too many requests error instead of retrying immediately.
- Own the authorisationThe connection is authorised by a role account that your business owns, and the refresh token is stored safely, with a message to you if it stops working.
The price depends on what I find, so I quote in writing after a short discovery call. Tell me what is happening and I reply within 24 hours.
What do owners ask about this?
Are leads lost when Zoho refuses a call?
The refused call did not run, so the lead is missing in Zoho. It still exists in your own system if it was stored there, and can be sent again.
Can I raise the limit?
Zoho's page says super-admins can increase credits from the API Dashboard on a pay-as-you-go basis. Check the current terms there. Spending fewer credits is usually the first step.
Why did it stop after I changed my Zoho plan?
Credit and concurrency limits depend on the edition, so a change of plan changes both the daily allowance and the number of simultaneous calls.
Sources
How was this page made?
I drafted this page with AI assistance from the official documents listed under Sources. Found a mistake? Tell me.