Zoho CRM and Reverse Contact

Featured

A scripting language inside the CRM, and an edition gate in front of it.

What you have to buy first

A Reverse Contact API key, and Zoho CRM Enterprise or above for the in-CRM route

What moves

Contacts, Companies, one way, in.

Zoho is the only CRM here that ships a programming language, and with Enterprise it genuinely removes the middle layer: a workflow rule fires a Deluge function, invokeUrl calls Reverse Contact, and the same function writes the fields back. Thirty seconds of execution inside automation is more headroom than HubSpot gives custom code and more than Attio gives an HTTP block. Below Enterprise the honest answer is the same as everywhere else: a workflow webhook out to Zapier, Make or a worker, and the API to write back.

What actually syncs

Object by object, with the direction each one moves in. This is the table to read before the feature list, because a capability that only moves one way is a different product from the one you think you are buying.

WhatDirectionWhat that means in practice
Trigger One way, in A workflow rule on lead or contact creation, calling a Deluge function.
The call One way, out invokeUrl POSTs to /v2/enrich/persons with the Authorization header and the record's email. 2 credits.
The response One way, in Deluge parses the JSON in the same function and maps the fields you want.
Write-back One way, in zoho.crm.updateRecord sets the fields. That integration task spends an API credit as well as the function credit.

Nothing in that table moves in both directions. Whichever system you treat as the source of record, the other one is downstream of it, and a correction made in the wrong place does not travel.

Which field lands where

On Enterprise and above the whole pair is one Deluge function: invokeUrl makes the call, the response arrives as a map, and zoho.crm.updateRecord writes the fields back. Below Enterprise the same list describes a worker somewhere else, reached by a workflow webhook.

In ZohoIn Reverse ContactWhat to know about the match
A workflow rule on Leads or Contacts Nothing yet The trigger. A workflow, blueprint or approval function gets 30 seconds of execution, which is more headroom than a HubSpot custom code action and the same as an Attio HTTP block.
invokeUrl, inside the function POST /v2/enrich/persons, 2 credits Identity, the current role, history, education, skills and location on one schema. The call itself costs nothing from either Zoho meter, because an outbound call is not a CRM API call.
invokeUrl, from a domain POST /v2/enrich/companies, 2 credits Firmographics from a domain or a company name. Run it on the account rather than once per contact attached to it.
The response, as a Deluge map success, data, error, metadata, quotas Five keys on every endpoint. metadata.updatedAt is the one worth reading before paying for a refresh, and quotas.workspace.credits.left is how the function can see its own balance.
zoho.crm.updateRecord Your own prefixed fields Costs an API credit at the Update Records rate, because Zoho includes Deluge integration tasks in API credit consumption. Insert, update and upsert take up to 100 records per call, and the maximum credit deduction for those is 10.
A scheduled function A bulk pass, with 15 minutes Where a backfill belongs, and the only category in Zoho with enough runtime to poll a live job to completion. Zoho recommends designing long-running logic here explicitly.
A workflow webhook, below Enterprise Zapier, Make or your own worker The fallback when functions are not available. The shape is then identical to the Pipedrive build: out to a worker, enrich, and back in through the API.
Anything outbound to Reverse Contact Nothing at all This is a read layer. No Zoho record or field is sent anywhere, and there is nothing in the product to send it to.

Two meters, and the quiet one is the one that runs out

A Deluge function draws on two separate pools at once, and Zoho started counting the second one deliberately, having previously had no way to identify calls made through integration tasks. An enrichment loop spends both, and the one that stops you is rarely the one you were watching.

What you runWhat it draws down
One function execution, written in DelugeOne function credit. Enterprise and Zoho One allow 20,000 free plus 500 per user licence plus add-ons, to a maximum of 400,000
The same function written in Java, Node.js or Python1 function credit per 10 seconds of execution, so the meter becomes a clock
invokeUrl, calling Reverse ContactNothing from either Zoho pool, and the org-wide Invoke URL quota is 5,000,000 requests a day
zoho.crm.updateRecord inside that functionAn API credit at the Update Records rate, because integration tasks count as API credit consumption
zoho.crm.searchRecords inside that functionAn API credit at the search rate, and it falls under the sub-concurrency limit of 10 on every edition
The API credit pool itself50,000 plus 250 to 2,000 per licence in a rolling 24 hours. Capped at 100,000 on Standard and 5,000,000 on Enterprise
Running many at onceConcurrency is 20 per org per app on Enterprise. There is no per-minute limit at all: Zoho states you may make any number of calls a minute provided concurrency holds

What does not cross

A few things are worth knowing before you plan around this mapping, because each one is a decision somebody has to own rather than a setting to find.

  • A marketplace app inside Zoho. Reverse Contact maintains apps on Clay, Zapier and Make and nothing inside any CRM, so the in-CRM route is one you write rather than one you install.
  • Functions on Standard or Professional, other than through Extensions. Zoho states that full access begins at Enterprise, CRM Plus, Ultimate and Zoho One.
  • A business email or a direct phone number. Both are separate endpoints at 3 and 20 credits, charged only when one is found, and the email finder is asynchronous as well.
  • Anything travelling back to Reverse Contact. The direction runs one way and there is nothing in the product to write to.

Every row above travels as a file: eight field mappings, seven what you run rows and four documented exclusions, each one's note, and the seven vendor documents behind them. The CSV opens in a spreadsheet, the JSON is the shape an agent wants, and the Markdown is the table to paste into a ticket.

Field map

The second row of that table is the one to read twice. Writing the function in Deluge costs one credit however long it runs; writing the same logic in Java, Node.js or Python costs one credit per ten seconds, which turns a slow enrichment into a recurring charge rather than a fixed one. For a call that answers at a published 500ms P95 the difference is academic, and for a scheduled pass over the back catalogue it is not.

Which function category has time for which job

The gate on this pair is the edition, and the thing that decides the design once you are past it is where the function is triggered from. Zoho gives a Deluge function a different execution ceiling per category, and the range is wide enough to change what is possible rather than just what is comfortable. Pick one on each side and the grid marks the answer.

Pick one on each side.

The function categoryOne cached lookup and one writeCheck freshness first, refresh only if staleA live refresh, polled to completionFifty records in one run
Button, related list, validation rule or REST API: 10 seconds Fits comfortably Fits comfortably Terminated Terminated
Workflow, blueprint or approval: 30 seconds Fits comfortably Fits comfortably Tight Tight
Schedule: 15 minutes Fits comfortably Fits comfortably Fits comfortably Fits comfortably
Fits comfortably
Inside that category's documented timeout with room to spare. Reverse Contact publishes a 500ms P95 on the cached endpoints, so a lookup and a write is nowhere near any of these ceilings, and the free freshness check adds one more call and no credits.
Tight
Possible, and close enough to the edge to be a gamble. A live job is documented as usually seconds and possibly tens of minutes, and Zoho terminates an over-running function rather than warning about it.
Terminated
Forcefully terminated. Zoho says so in those words, and recommends designing long-running logic for the Schedule category while keeping the interactive categories lightweight.

Counted off that grid, of twelve pairings: eight give you fits comfortably, two give you tight, two give you terminated. The bottom row is the finding, and it makes Zoho the only CRM in this directory that can poll a live job inside itself. Fifteen minutes is enough to start a refresh, wait for it and read the result, which neither a HubSpot custom code action at twenty seconds nor an Attio HTTP block at twenty can manage. The price is that a schedule is not a trigger, so fresh data arrives on your timetable rather than the prospect's.

How to connect Zoho to Reverse Contact

Every step below is from the two vendors' own setup documentation, in the order they document it. Two of them cost you an afternoon if taken late, so the order is the useful part rather than the clicks.

Who has to do it
Somebody with the Manage Extensibility permission on an Enterprise edition or above, plus whoever can create a Reverse Contact API key. Below Enterprise, whoever runs the worker instead.
How long it takes
Half a day for the Deluge route. Confirming the edition and the permission takes five minutes and saves most of it.
Setup checklist 0 of 8 done

Zoho: Setup, then profile Developer Permissions

Functions have full access on Enterprise, CRM Plus, Ultimate and Zoho One, and Standard and Professional can reach them only through Extensions. Separately, creating one needs the Manage Extensibility permission. An admin without that permission sees exactly what somebody on the wrong edition sees, which is nothing.

Zoho: the function category

A workflow, blueprint or approval function gets 30 seconds. A scheduled one gets 15 minutes. A button, related list, validation rule or REST API function gets 10. Zoho terminates anything that exceeds its category, so this choice is the design rather than a setting.

Zoho: Setup, Modules and Fields

Prefixed, and separate from anything a rep types into. The function writes with zoho.crm.updateRecord and will write exactly what you tell it, including an absent value, so the separation is what makes the pair safe to leave running.

Zoho: the Deluge function

invokeUrl takes the URL, the type and the parameters, with the Authorization header carrying your key. Worth knowing before you paste it: the key lives in the function source, so anybody with Manage Extensibility can read it, which is a weaker position than a Salesforce Named Credential and stronger than a key in a third-party cloud.

Zoho: the Deluge function, again

Reverse Contact returns null rather than a best guess when it is not confident, so the response map simply has no key for an unresolved field. Three lines of Deluge checking for it is the difference between an enrichment that fills gaps and one that creates them.

Zoho: Setup, API Dashboard

Every function execution is one function credit, and the Deluge integration tasks inside it that touch CRM records cost API credits as well. Zoho says so explicitly, having previously had no way to identify those calls, so an enrichment loop draws down two pools at once.

Zoho: the Deluge function

Search records invoked from a function is one of seven calls under the sub-concurrency limit, which is 10 across every edition. Fetching by id instead keeps you on the ordinary concurrency limit, which is 20 per org per app on Enterprise.

Zoho: Setup, Functions, Schedule

Fifteen minutes is generous and the 200,000 lines of execution cap is not a line count of your source: Zoho notes that loops, conditional branches and called child functions all contribute. Chunking a backfill is what keeps a scheduled pass inside both ceilings.

Steps one and two decide whether this build exists and what shape it takes, and both are answerable in ten minutes. That is the pattern across this whole set of pages: the enrichment is never the hard part, and the CRM's own rules about where code may run are. Attio reaches the same place with three blocks and no language at all.

Hand it to an agent instead

The same sequence, the sync table, the documented limits and the error list ship as one agent skill. Point Claude Code, Cursor or anything that reads a file at this pair as a skill and it has the whole pair without reading two sets of vendor docs first.

curl -o .claude/skills/zoho-reverse-contact/SKILL.md https://www.reversecontact.com/integrations-hub/skills/zoho-reverse-contact.md

What breaks, and what nobody tells you

Every limit below is documented by one of the two vendors. They are here because they change decisions, not because they are flaws.

Functions in full are Enterprise and above
Zoho states that Functions are available on Enterprise, CRM Plus, Ultimate and Zoho One with full access, and that Standard and Professional can only access them through Extensions. The in-CRM route on this page therefore starts at Enterprise, and the fallback below it is a workflow webhook to something else.
Thirty seconds inside automation, ten elsewhere
Category timeouts are 30 seconds for workflow, blueprint and approval, 10 seconds for a button, related list, validation rule or REST API call, and 15 minutes on a schedule. A function that exceeds its category is terminated. Put a bulk pass on a schedule rather than hoping a button will carry it.
Two meters, and the second one is quiet
A function execution is one function credit; the Deluge integration tasks inside it that read or write CRM records are counted as API credits as well. Zoho says so explicitly, having previously not counted them. An enrichment loop therefore draws down both pools, and the API pool is the smaller one on Standard at 100,000 a day maximum.
API limits are credits and concurrency, not calls a minute
The allowance is 50,000 credits plus 250 to 2,000 per user licence in a rolling 24 hours, capped at 100,000 on Standard and 3,000,000 on Professional, with 5,000 on the free edition. There is no per-minute limit; instead concurrency caps simultaneous calls per org per app at 5 on free rising to 20 on Enterprise.
You need the Manage Extensibility permission
Creating and managing functions requires that permission under Developer Permissions in profile settings. An admin without it sees no option to create one, which reads like an edition problem and is not.

Each of those is documented behaviour rather than a fault, so none of them is going to be fixed by a support ticket. The ones that produce a symptom you would misread are below.

The 8 failures people actually hit

Each one below is a symptom somebody reports, the documented reason behind it, and the fix. Most are configuration rather than faults, which is why they survive a support ticket.

01

There is no option to create a function anywhere

WhyTwo causes that look identical. Functions have full access on Enterprise, CRM Plus, Ultimate and Zoho One, with Standard and Professional reaching them only through Extensions. Separately, creating and managing them needs the Manage Extensibility permission under Developer Permissions.

Check the permission before the edition, because it is the cheaper of the two to fix and an admin without it sees exactly what somebody on the wrong edition sees.

02

The function was terminated partway through

WhyZoho enforces a timeout by category: 10 seconds for a button, related list, validation rule or REST API call, 30 seconds for workflow, blueprint and approval, and 15 minutes on a schedule.

Move the work to the Schedule category, which Zoho recommends for long-running logic. There is no setting to raise a category timeout, so this is a move rather than a tweak.

03

The function hit the lines of execution limit

WhyA single invocation is capped at 200,000 lines of execution, and Zoho notes this counts lines the runtime actually executes: loops, conditional branches and called child functions all contribute.

Chunk the loop rather than widening it. A scheduled pass over records in batches counts far fewer lines than one that re-reads a collection on every iteration.

04

The API credit pool emptied and nothing called the API

WhyDeluge integration tasks count as API credit consumption. Zoho changed this deliberately, having had no way to identify calls made through them, so zoho.crm.searchRecords costs the same as the Search Records API.

Open Credits by Application and Functions on the API Dashboard, which attributes consumption to the function that caused it. The X-API-CREDITS-REMAINING header appears on responses once you pass half the daily limit.

05

TOO_MANY_REQUESTS from a function making very few calls

WhyThat is the sub-concurrency limit, which is 10 across every edition and applies to seven expensive calls including search records invoked from a function, the Query API and the Composite API.

Fetch by id rather than searching from inside the function. Zoho notes that sub-concurrency does not apply to integration tasks at all, so the same work routed that way is subject only to the ordinary concurrency limit.

06

The function wrote an empty value over a real one

WhyReverse Contact returns null rather than a best guess when it is not confident, so the response map has no key at all for an unresolved field and Deluge writes the absence.

Test for the key before writing it, and keep the enrichment in prefixed fields of its own. Three lines of Deluge separate an enrichment that fills gaps from one that creates them.

07

A live refresh timed out inside the workflow function

WhyThe live endpoints answer with a webhookId rather than a record, and the workflow category allows 30 seconds against a job documented as usually seconds and possibly tens of minutes.

Move the live path to a scheduled function, where the ceiling is 15 minutes and the poll fits. Polling is free and off the rate-limit clock, so the only costs are the function credit and the waiting.

08

An endpoint that worked last week returns nothing

Why/v2/resolve was replaced by /v2/enrich and /v2/search/persons by /v2/search/people, with the old pair documented as live only until 13 October 2026.

Search your functions for both old paths and change every invokeUrl that carries one. The strings are in Deluge source, so one text search finds all of them, which is a genuine advantage of keeping this inside the CRM.

If none of those is it, the next thing to check is the thing most pairs fail on: whether the plan you are on carries the feature at all, which the grid above answers. The same symptom on another pair is often the same cause, so the directory indexes all of them by the message rather than by the integration.

When this is the right integration

Set it up when

  • An Enterprise org that wants the whole thing inside the CRM
  • Scheduled bulk enrichment, where 15 minutes of runtime is plenty
  • A team already writing Deluge for something else

Do not bother when

  • Standard or Professional, where functions need an extension
  • Nobody will maintain Deluge after the person who wrote it leaves
  • Live resolution from a workflow rule, where 30 seconds will not cover the wait

The right-hand column is the one worth being honest about, because every item in it is a reason to spend the budget somewhere else in the stack rather than a reason to configure harder.

What practitioners say about it

Searched for the problem this pair solves rather than for the pair itself, because the pair by name returns almost nothing. 14 threads from 2024 to 2026 were read in full on 11 October 2026, and the 5 below are the ones that carry a point. Each is one person's experience rather than a measurement, and the vendors' own documentation is what the rest of this page rests on.

A Zoho user asking for the thing Zoho already does

Do you have any suggestions for tools that can be directly set up and automated without using an automation tool? I understand that Zapier and Make,com offer simpler automation features, but was hoping to look into some alternatives methods that will keep overall expenses low.

r/CRM·July 2024·1 points

Asked in a thread about enriching Zoho leads automatically, and asked a second time after the first answer was a middleware tool. Nobody in the thread mentions Deluge or invokeUrl. On an Enterprise edition that is exactly the answer being asked for: the function makes the call, reads the response and writes the fields, with no third meter anywhere.

The answer people give instead is a provider plus a connector

For automated enrichment you'll prob need an API based tool that plugs right into Zoho. Bright Data works well if you need fresh web data (company info, contacts, even reviews), you can set up feeds or APIs so new leads get enriched automatically w/o manual work.

r/CRM·August 2025·2 points

A reasonable answer and it still assumes a connector rather than a function. The useful word in it is automatically, because that is the part the edition decides: below Enterprise the automation is a workflow webhook to something else, and from Enterprise up it is a Deluge function the same rule fires.

The problem is stated the same way whichever CRM is in the question

One of the biggest issues we face is outdated or incomplete company data inside our CRM. Manual updates don't scale, and basic enrichment plugins often miss key fields like company group structure or employee count. Curious if anyone here has found a reliable way to automate enrichment or sync external data into CRMs like Salesforce or Zoho?

r/CRM·July 2025·3 points

Employee count is the example given, and it is also the field most likely to arrive as a Number and be written into a text field. On this route that mapping is three lines of Deluge rather than a plugin's decision, which is the trade: more work, and no plugin deciding which of your fields it may overwrite.

Cleaning is not the same job as keeping clean

Look up data hygiene and data scrubbing. You'll need to clean the data that you have, and introduce better processes for inputting data/receiving data going forward. [...] A lot of companies are exactly where you are, unknowingly creating technical debt that is difficult and expensive to extricate themselves from years later.

r/CRM·July 2024·3 points

Two jobs, and this page has a different answer for each. The back catalogue is a scheduled function with fifteen minutes of runtime, and keeping it clean is a workflow function with thirty seconds. Confusing them is what produces a trigger that gets terminated mid-batch, which is the second entry in the failure list above.

The durable part is process rather than tooling

Data management is mostly about continuous management and getting data right, first time, and having processes in place to review / dispose. Which is not a terribly fun answer I'm afraid.

r/CRM·July 2024·2 points

Correct and incomplete, which the author half concedes. Getting it right first time is what an enrichment on creation is for; the review and dispose half is what the update date on every response supports, because a record you can date is a record you can decide to refresh or retire.

What the threads add up to

Nobody discusses this pair by name, so the search was for the job: enriching a Zoho lead automatically as it arrives. The best thread is a Zoho user asking twice for a way to do it without Zapier or Make, and getting product recommendations instead of the answer, which is that Zoho can make the call itself from Enterprise up. That gap between what the product does and what its users know it does is this page.

The first quote is the whole page in one request: somebody wanting to enrich Zoho leads without a middle layer, in a thread where nobody told them their own CRM can do it. Whether it can comes down to the edition and one permission, and what it can finish once it can comes down to which category the function runs in, which is what the grid above counts.

The longer answer

Zoho belongs in the same conversation as HubSpot rather than with the lighter CRMs, because both sell the ability to call an external API from automation as part of a higher tier. HubSpot puts the webhook and custom code actions in Data Hub, a separate purchase from Sales Hub. Zoho puts functions in Enterprise. The difference is that Zoho's gate is a tier of the product you already bought rather than a second product, and that its timeout inside automation is 30 seconds against HubSpot's 20, which matters more than it sounds when a provider is having a slow minute.

The quiet cost on this route is the double metering. A Deluge function that calls out and writes back spends a function credit and an API credit, and Zoho changed that deliberately: integration tasks used to be invisible to the API counter and now are not. On Standard, where the API ceiling is 100,000 credits a day whatever the licence count, a nightly sweep over a large database is a real constraint rather than a theoretical one.

Where the edition is not there, the shape falls back to what every other CRM in this directory does. A workflow webhook fires out, something enriches, the API writes back, and the something is usually the native app on Zapier or a Make scenario. The same fallback is what a monday CRM build has to use from the start, because monday has no in-product scripting of this kind at all. Compared with both, a Zoho function on Enterprise is the cheapest steady state and the hardest to hire for.

Checked by

Reverse Contact

We sell B2B people and company data, and we publish this directory. Every tier requirement, sync direction and limit on this page was read from a vendor's own knowledge base, developer documentation or pricing page on the date below. Nothing on it is restated from a press release or a third-party listing.

Where a vendor publishes no public figure, this page says so rather than estimating, which is why no page here prints a cost per enriched record. Reverse Contact appears in this directory as a data provider and publishes it. No other vendor pays for placement, and every link out of a listing or a citation carries nofollow, including the ones that point at Reverse Contact. The only followed links on this page are the two calls to action and the reviewer.

One fact about the publisher, stated here rather than in the page above it: Reverse Contact has no CRM marketplace app and no app inside a sequencer. Its three native apps are on Clay, Zapier and Make, and every other route is its API, its CLI or its MCP server. That is a deliberate shape for a data layer rather than a missing release, and it is what the routes on this page are describing.

Tier requirements, sync behaviour and documented limits change without notice. Confirm against your own contract before you budget. What has changed since · How we checked, and what we will not claim

Researched and written by

Eugene Suslov

Researched and wrote every page in this directory, and checked every tier requirement, sync direction and documented limit against the vendor's own knowledge base, developer documentation or pricing page.

Verified
2026-10-11
Sources
7 vendor documents
Paid placement
None

The integration moves the record. Something has to fill it.

Reverse Contact resolves an email, a domain or a profile URL into a verified people and company record, through one API with a consistent schema. It sits under Zoho, Reverse Contact and everything else in this directory, and it returns null with a confidence score rather than a guess.

Free trial, no card required, and 500 credits to start.

Zoho and Reverse Contact, asked and answered

Is there a Zoho and Reverse Contact integration?

Not as an app, and from Enterprise up Zoho does not need one: a workflow rule fires a Deluge function, invokeUrl calls the API, and the same function writes the fields back. Below Enterprise, functions are reachable only through Extensions, and the honest answer is a workflow webhook out to Zapier, Make or a worker of your own, with the API writing back in.

Can Zoho CRM call an external API by itself?

Yes, with a Deluge function and the invokeUrl task, which is the closest thing in this directory to writing the integration inside the CRM. A workflow rule fires the function, the function calls Reverse Contact, reads the response and updates the record. No middle layer and no second meter.

Which edition do I need?

Functions are fully available on Enterprise, CRM Plus, Ultimate and Zoho One. Standard and Professional can reach them only through extensions, which is a packaging exercise rather than a settings change. This is Zoho's version of the gate HubSpot puts in front of custom code, and it is the first thing to check.

How long can the function run?

Thirty seconds when it is triggered from automation, meaning a workflow, blueprint or approval. Ten seconds from a button, a related list, a validation rule or the REST API, and fifteen minutes on a schedule. A cached reverse lookup fits every category except possibly the ten-second one on a slow day.

Does the function spend API credits as well?

Yes, twice over, and it is easy to miss. A function execution costs one function credit, and the Deluge integration tasks it uses to read and write CRM records count against the separate API credit pool. So a function that enriches and updates spends from both. The outbound invokeUrl call has its own ceiling of 5,000,000 a day across the org, which nobody reaches.

Tier requirements, sync behaviour and limits read from each vendor's own documentation in September, October and November 2026. Vendors change these without notice.

Reverse Contact appears in this directory as a data provider and publishes it. Every other tool is here on merit and nobody pays for placement.

Ask an assistant