A native app with nine operations, and a miss that costs nothing.
A Zapier plan with enough tasks, and a Reverse Contact API key
Contacts, Companies, one way, in.
This is the shortest route between Reverse Contact and a CRM or a sequencer that has no app of its own, and since the native app shipped it is a connection rather than a build. Nine operations cover everything a middle step needs, the enrichment bills nothing on a miss, and the whole thing is a dropdown rather than an HTTP module with a Bearer token typed into it. What decides whether it scales is Zapier's task meter, not anything on Reverse Contact's side: a task per step per record is excellent at hundreds of records a month and poor at hundreds of thousands.
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.
| What | Direction | What that means in practice |
|---|---|---|
| Trigger | One way, in | Anything Zapier already connects to: a new CRM contact, a form submission, a new row, a schedule. |
| The enrichment step | One way, out | Enrich a Person or Enrich a Company, taking the email or domain from the trigger step. 2 credits on a match, 0 on a miss. |
| The free checks | One way, out | Check a Person Profile and Check a Company Profile cost 0 credits, so a Zap can test for cached data before spending anything. |
| Write-back | One way, in | Whatever app owns the record. Zapier's own CRM actions map the returned fields. |
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.
Nine operations, seven of them Functions that write and two Queries that search, and no triggers at all. Each maps onto one Reverse Contact endpoint, and the app states a credit cost on the ones that have one.
| In Zapier | In Reverse Contact | What to know about the match |
|---|---|---|
| Enrich a Person | enrich_person, 2 credits if found | Takes an email, or a name plus company, and returns the matched identity. Zapier's own listing states 2 credits if a profile is found and 0 if there is no match, which makes a miss free on this route and is the single most useful fact about it. |
| Enrich a Company | enrich_company, 2 credits if found | Takes a domain and returns the company profile. Same billing shape: nothing is charged when there is no match. |
| Get LinkedIn Profile | get_linkedin_profile | Takes a profile URL rather than an email, so it is the cheap route when the trigger already carries one. This is the cached lookup Reverse Contact prices at 1 credit and makes unmetered from the $249 plan up. |
| Get LinkedIn Company | get_linkedin_company | The company equivalent, from a company profile URL. Also a cached lookup rather than a reverse one. |
| Check a Person Profile | check_person, 0 credits | Says whether a person profile exists in the database from its URL or ID. Free in credits, and still one Zapier task, which is the trade this page keeps coming back to. |
| Check a Company Profile | check_company, 0 credits | The company equivalent, also stated as 0 credits on the listing. |
| Search Person and Search Company | search_person, search_company | The two Queries rather than Functions, so Zapier treats them as lookups that find an existing thing. Search is priced per profile delivered, and the free count endpoint that would let you size a query first is not one of the nine. |
| Get Workspace Usage | get_workspace_usage, 0 credits | Returns the workspace credit usage and quotas, total, used and left. The only way a Zap can read its own balance, and worth a scheduled Zap of its own rather than a step inside a working one. |
This is the part that decides whether the route survives volume, and it is not on either vendor's pricing page because it needs both. Reverse Contact bills the result and Zapier bills the attempt, so the two halves of the bill move in opposite directions as your match rate changes.
| What happens | What each side charges for it |
|---|---|
| Enrich a Person, and a profile is found | 2 Reverse Contact credits, and one Zapier task |
| Enrich a Person, and nothing matches | No credits at all, and one Zapier task |
| Check a Person Profile, either way | No credits, and one Zapier task |
| A filter step that stops the Zap | No credits, and one Zapier task, which is what it saves the steps behind it |
| The polling Zapier does to spot the trigger | Nothing on either side. Polls consume no tasks, only successful steps do |
| A three-step Zap over 40,000 records | 120,000 tasks, and credits only for the rows that matched |
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.
Every row above travels as a file: eight field mappings, six what happens rows and four documented exclusions, each one's note, and the six 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.
The nine operations are a generous surface for a middle step and the gap worth planning around is the absent tenth: there is no trigger, so this app is always a passenger. What fires the Zap is the app that owns the record, which is also the app whose own rate limits and polling interval decide how quickly an enrichment actually happens.
The Zapier app does not price itself and Reverse Contact does. Which of the nine actions your Zap calls is what decides which plan stops metering it, and the distance between the cheapest and the dearest answer is $450 a month. Pick one on each side and the grid marks the answer.
Pick one on each side.
| Reverse Contact plan | Check a Person or Company Profile | Get LinkedIn Profile or Company | Search Person or Company | Enrich a Person or a Company |
|---|---|---|---|---|
| Credits, from $100 | Always free | 1 credit a call | 1 credit a call | 2 credits a call |
| Go, $249 a month | Always free | Unlimited | 1 credit a call | 2 credits a call |
| Plus, $449 a month | Always free | Unlimited | Unlimited | 2 credits a call |
| Max, $699 a month | Always free | Unlimited | Unlimited | Unlimited |
| Platform, quoted | Always free | Unlimited | Unlimited | Unlimited |
Counted off that grid, of twenty pairings: five give you always free, nine give you unlimited, three give you 1 credit a call, three give you 2 credits a call. Read the top right against the bottom left and the shape of the decision appears. Enrich a Person is the action nearly every Zap here uses, because a CRM trigger carries an email rather than a profile URL, and it is the one column still metered at $449. A Zap that happens to hold a profile URL already is unmetered at $249. None of that touches Zapier's own meter, which is counted per step rather than per record and is the half of the bill that grows with volume.
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.
A pencil, not a screen
Zapier charges a task for each step that runs, so a Zap that triggers, enriches and updates spends three tasks on every record whether or not the lookup matched. Multiply by records a month and compare it with an hour of engineering. This is the decision that cannot be undone later without rebuilding, and it is the one nobody takes first.
The app that owns the record
Point the update step at properties nothing else writes to, prefixed so a rep never types into one. A Zap that writes a title into the field somebody maintains by hand will keep doing it quietly, and the damage is only visible once somebody notices their own entry has gone.
Reverse Contact: Workspace, API Keys
Keys are made in Workspace then API Keys, and a per-key rate limit can cap one integration below the workspace maximum. Give the Zap its own key with its own cap, so a runaway Zap cannot starve everything else on the workspace minute limit.
Zapier: the action step, Choose account
The app authenticates against your own workspace, so the credits are yours rather than the platform's. That is the opposite of the Clay app, which runs on Clay credits by default, and it is why this route needs a Reverse Contact account and that one does not.
Zapier: the nine operations
Enrich a Person takes an email or a name plus company. Get LinkedIn Profile takes a profile URL. Search Person takes criteria. Which one you can use is decided by the trigger, not by preference, and it also decides which Reverse Contact plan makes the Zap unmetered.
Zapier: Filter by Zapier
A filter step costs a task and stops the ones behind it from running at all. On a trigger that fires on every record update rather than on creation, that filter is the difference between enriching new contacts and re-enriching the whole database every time somebody edits a note.
Zapier: Check a Person Profile
Check a Person Profile costs 0 credits and tells you whether a profile is cached and how fresh it is. It still costs a Zapier task. So checking first saves credits and spends tasks, and which way that trade goes depends on your match rate rather than on best practice.
Zapier: Test step
Run the Zap once on a record you know the answer for, then open the enrichment step output. A miss comes back without a profile rather than as an error, so a Zap that maps the output blindly writes an empty field and reports success.
The two steps that look like overhead, the filter and the key, are the two that stop this route becoming expensive. Everything else is a dropdown, which is the point of a native app and the reason this is the shortest route in the directory to a tool with no connector of its own.
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/zapier-reverse-contact/SKILL.md https://www.reversecontact.com/integrations-hub/skills/zapier-reverse-contact.md
Every limit below is documented by one of the two vendors. They are here because they change decisions, not because they are flaws.
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.
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.
WhyA lookup that matches nobody is not an error. Reverse Contact returns null rather than a best guess, and the Zapier step completes normally with no profile attached.
Put a Filter by Zapier step between the enrichment and the update, testing that the field you are about to write actually exists. One extra task per record buys you a CRM that is never written an empty value.
WhyZapier charges a task for every step that runs, not per Zap and not per record, so step count multiplies the bill.
Count steps, then move the filter as early as the trigger allows: a filter that fires first stops every step behind it. Polls themselves consume no tasks, so the trigger is not what is costing you.
WhyThe trigger is firing on any record change rather than on creation, which is a property of the CRM app's trigger rather than of this one.
Switch to a creation trigger where the app has one, or filter on the enrichment field being empty. On a 2-credit action an unconditional re-run is a standing monthly cost rather than a one-off.
WhyWhen a Reverse Contact workspace drops below 2 credits the free Check endpoints are paused too and answer 402 NO_CREDITS, because the fetch a check precedes can itself cost 2.
Run Get Workspace Usage on a schedule rather than waiting for the failure. It costs nothing, and GET /v2/usage keeps answering when the checks do not.
WhyReverse Contact applies a minute limit per workspace, and a per-key limit if one was set. A second Zap, a Clay table or somebody in the dashboard shares that same workspace minute.
Give each integration its own key with its own cap, which the API key management guide documents, and read quotas.minuteRateLimit on any response to see limit, used, left and the next reset.
WhyThe live endpoints are asynchronous by design: they reply with a webhookId and deliver the result afterwards, usually in seconds and sometimes in tens of minutes.
Use the cached actions in the Zap. Live resolution belongs in a workflow with a loop, which is n8n or a Make scenario with a repeater, and the result can be written back by a second Zap on a webhook if the Zap is where the logic lives.
WhyCredit packs are valid 3 months, and the packs run from 5K to 1M. A Zap that fires in bursts can reach the end of a quarter holding credits it paid for.
Match the pack to a quarter of real volume rather than to a discount, or move to an Unlimited plan, where the cached endpoints the plan names stop being metered at all.
WhySearch is priced per profile delivered rather than per request, and the free count endpoint that would size the query first is not one of the nine operations.
Narrow the criteria before the Zap goes live, and test the same query outside Zapier where the count endpoint is reachable. A search is the one operation here whose cost is not knowable from the step configuration.
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.
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.
Searched for the problem this pair solves rather than for the pair itself, because the pair by name returns almost nothing. 14 threads from 2022 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.
Zapier is a godsend for a lot of smaller organizations who have modest resources and needs. If you're transferring 10,000 rows a month from one system to another, it's amazing. If you're a big firm that moves around millions of records, it's got some issues.
r/salesforce·August 2024·18 points
The single most useful sentence in the set, from a thread full of Salesforce consultants being asked to approve Zapier. The figures are this person's judgement rather than a published limit, and the shape is right: count the steps in your Zap, multiply by records a month, and the answer is usually obvious in one direction or the other.
i ran a lead enrichment flow, which is basically where a form submission comes in, AI node pulls company info, classifies the lead by fit, then drafts a personalized outreach email. the optimization that actually moved the needle for me: i added a filter before the AI node so only leads from companies over 20 employees even hit the classification step. killed about 60% of my AI calls overnight. but honestly the thing that burned me before i figured all this out, the email drafting node was running on every lead including the ones the classifier marked as low fit. was paying for it for like two weeks before i noticed. no alert, no log that made sense, just a bill that was higher than it should've been.
r/zapier·April 2026·2 points
This is the enrichment Zap on this page, described by somebody who built it and then read the invoice. Two things transfer directly: a filter placed before the expensive step rather than after it, and the fact that nothing warns you. A Zap that runs a step it should have skipped reports success every time.
There's a lot of optimization can be done while designing the workflow in Zapier itself to that the cost doesn't explode. However, if you are confortable with technical nature of n8n, it will cost you lesser than Zapier because n8n doesn't charge per step, they charge per workflow execution. But I always recommend Zapier for its ease of use over any other tool except when cost is really a constraint.
r/zapier·April 2026·2 points
A fair summary of the choice, typos and all, and it names the mechanism rather than a preference. Per step against per execution is exactly why the three-step enrichment Zap costs three tasks a record and the same logic in a workflow engine costs one run.
That $130 jump is exactly why I stopped building AI-heavy workflows in Zapier. When every AI call is a 'task,' your overhead scales faster than your revenue. I solve this by migrating high-frequency AI loops to a Logic Gate architecture in Make.com. You aren't billed per 'task' the same way; you're billed on data operations
r/zapier·April 2026·3 points
Read the self-promotion in the rest of that comment with the scepticism it deserves, and the first two sentences stand on their own. Overhead scaling faster than revenue is the honest failure mode of a per-step meter, and it is the reason this page does the arithmetic before the build rather than after.
Zapier is close to a household name in data automation circles, though there are lots of services similar to it, like Jitterbit. If you're basically being asked to give a stamp of approval, Zapier is safe and has enough market share that the risk is minimal. I haven't used it but I've been exposed to it across our portfolio and it's being used in a ton of places to do all kinds of integrations. I would have the product owner make absolutely sure it does everything your org needs it to before becoming reliant on it, though.
r/salesforce·August 2024·9 points
Written by somebody asked to sign off on a decision that had already been taken elsewhere, which is how this route usually arrives. The last sentence is the one to act on here: the nine operations in this app are a generous surface and there is no tenth, so check your specific call is among them before the Zap becomes load-bearing.
Nobody discusses this pair by name, so the search was for the job: moving enriched records between a form, a CRM and a sender without writing code. Almost every thread converges on the same argument, which is that Zapier is the right answer at a volume and the wrong one past it, and that the threshold is arithmetic rather than taste. The cost threads are the useful ones, because they are written by people who found the number the hard way.
None of the five is about Reverse Contact, and all five are about the meter the Zap runs on, which is the correct distribution: the enrichment step is a dropdown and the task arithmetic decides whether the route survives. The one number worth taking from the threads rather than from a vendor is the volume threshold, and the one worth taking from the Make comparison is what happens when your call is not on the list of nine.
Until September 2026 this page would have been an argument for the generic Webhooks action, which meant a URL, a Bearer token and a JSON body typed into a Zap by somebody who had read the API reference. The native app removes all of that, and it removes the most common mistake with it: a Webhooks step cannot tell you that a lookup missed, so teams routinely wrote the empty response into a CRM field. The Enrich a Person action bills nothing on a miss, which is also the signal that there was one.
The reason this page matters more than its own search volume is that it is the answer on most of the long tail. Reverse Contact maintains apps on three platforms and nothing inside any CRM or sequencer, so for Pipedrive, Salesloft, Close, Copper and everything else in that shape, "put the native Zapier app between two steps" is the honest recommendation rather than a fallback. The Pipedrive guide reaches that conclusion by a different road, because a Pipedrive automation can fire a webhook and cannot read what comes back.
Where it stops being the right answer is volume, and the threshold is arithmetic rather than judgment. Count the steps in the Zap, multiply by records a month, and compare the task price against an hour of engineering. One pass over a 40,000-row database is 120,000 tasks on a three-step Zap, which is a different conversation from 2,000 inbound leads a month. At that point the Make scenario is cheaper per operation, and a direct API call from the Salesloft side or from n8n is cheaper still.
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 Zapier, 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.
Yes, maintained by Reverse Contact. It publishes seven actions and two searches: enrich a person, enrich a company, check a person profile, check a company profile, get a LinkedIn profile, get a LinkedIn company, read your workspace usage, and search for a person or a company. There are no triggers, which is the right shape for a step that sits in the middle of a Zap rather than starting one.
Two credits when a person or a company is found and nothing when there is no match, which the app states on each action. That is the single most useful thing about this route: on a list with a 70% hit rate you pay for the 70% rather than for the attempt, which is the opposite of how a Clay action bills. On top of that you pay Zapier one task per step that runs.
Yes, for this route. The Zapier app authenticates against your own workspace, so the credits are yours. The Clay app is the one that runs on the platform's own credits and needs no account at all, which makes it the better place to measure your match rate before you buy anything.
Not well. Live resolution returns a task to poll rather than a record, and a Zap has no natural loop to poll it with. Use the cached actions in a Zap and put live resolution in n8n, where a Wait node and a loop are ordinary.
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.