---
name: zapier-reverse-contact-integration
description: Connect Zapier and Reverse Contact: what syncs, which editions carry it, the setup order, and the failures to expect. Covers contacts, companies. Use when the user wants to set up, audit or troubleshoot Zapier and Reverse Contact together, or asks why data is not moving between them.
---

# Zapier and Reverse Contact

> Generated from https://www.reversecontact.com/integrations-hub/zapier-integrations/zapier-reverse-contact-integration
> Every tier requirement, sync direction and limit below was read from the vendors' own documentation on 2026-10-11.
> Vendors change these without notice. Re-check anything load-bearing before you rely on it.

**What you have to buy first:** A Zapier plan with enough tasks, and a Reverse Contact API key

**What moves:** contacts, companies, one way, into Zapier.
**How it is built:** native, zapier, make or n8n. **Effort:** minutes.

## The short version

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.

## What each Zapier action costs on each Reverse Contact plan

Rows: Reverse Contact plan. Columns: The action your Zap uses. 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.

| 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 |

- **Always free.** The two Check operations and the search count endpoint are free on every plan, though on a free trial with no credit left the count endpoints answer 402 as well. The one catch is documented: below 2 credits the free checks are paused as well and answer 402, because the fetch a check precedes can itself cost 2.
- **Unlimited.** Unmetered on that plan. Go covers the cached lookups behind Get LinkedIn Profile, Plus adds search, and Max adds the reverse lookups behind Enrich a Person. Live refreshes, business emails and direct phone numbers stay on credits on every plan including Platform.
- **1 credit a call.** Still metered at 1 credit, per call for a cached lookup and per profile delivered for a search.
- **2 credits a call.** Still metered at 2 credits a call, charged on a match and not on a miss, which is the Zapier app's own wording on both Enrich actions.

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.

## What actually syncs

Direction is written from Zapier's point of view: out means out of Zapier, in means into it.

| 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. |

## Which field lands where

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. |

### Two meters, and they disagree about what a miss costs

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 |

**What does not cross:**

- Any trigger. The app publishes nine operations and none of them is a trigger, so Reverse Contact never starts a Zap. Something else has to fire it: a CRM record, a form, a schedule, a webhook. That is the right shape for a data layer and it does mean the Zap always has at least two other steps.
- The live endpoints. They answer with a task id and complete in the background, and a Zap has no loop to poll with. Reverse Contact documents a live result as usually seconds and possibly tens of minutes, so this is not a Delay step with a longer delay.
- A business email or a direct phone number. Those are separate endpoints at 3 and 20 credits, charged only when one is found, and neither is among the nine operations.
- The free search count endpoint. Search Person and Search Company are both here and the call that would tell you how many results a query has before you pay for them is not, so size a search outside the Zap.

## Connect it, in this order

**Who has to do it:** Anybody who can edit a Zap, plus whoever can create a Reverse Contact API key. No admin on either side.
**How long:** Fifteen minutes. Working out how many tasks a record will cost takes longer than building it.

### 1. Count the tasks per record before you build anything

*Where:* 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.

### 2. Decide where the enriched value is written

*Where:* 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.

### 3. Create a scoped Reverse Contact key for this Zap

*Where:* 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.

### 4. Add the Reverse Contact connection once

*Where:* 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.

### 5. Pick the action that matches the identifier your trigger carries

*Where:* 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.

### 6. Put a filter in front of the enrichment, not after it

*Where:* 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.

### 7. Decide whether the free check is worth its task

*Where:* 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.

### 8. Test on one record and read what came back

*Where:* 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.

## How to check it worked

- Run Enrich a Person on an address you know matches nobody. The step should succeed with no profile attached and spend no credits, and the point of doing it on purpose is to see what your mapping does with that.
- Check your credit balance before and after that miss. It should not move, because Reverse Contact charges 0 credits on a 4xx, and the Zapier task history will show a task spent anyway.
- Add Get Workspace Usage as a temporary last step and read the credits left. It costs nothing, and it is the only way a Zap can see the balance it is spending.
- Turn the Zap on, let one real record through, then open the record in the destination app rather than the Zapier history. The history reports what Zapier did and the record shows what actually landed.

## When it goes wrong

Each row is a symptom somebody reports, the documented reason, and the fix. Work down it before escalating to either vendor, because most of these are configuration.

| Symptom | Why it happens | What to do |
|---|---|---|
| The Zap reports success and the field in the CRM is empty | A 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. |
| The task count is far higher than the number of records | Zapier 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. |
| The Zap re-enriches people it already enriched | The 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. |
| Everything stopped, including the steps that were free | When 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. |
| A 429 on a Zap that was working yesterday | Reverse 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. |
| A live refresh never returns anything to map | The 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. |
| Credits expired before they were spent | Credit 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. |
| A search returns far more results than expected and costs more than expected | Search 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. |

## What breaks, from the vendors' own docs

- **A task is charged per step, not per Zap.** A three-step Zap that triggers, enriches and updates spends three tasks on every record. That arithmetic, rather than the credit cost, is what usually decides whether this route survives contact with volume. Work out tasks per record and multiply before committing to it.
- **There are no triggers in this app.** Reverse Contact does not start a Zap. It is an action and a search, so something else has to fire: a CRM record, a form, a schedule, a webhook. That is correct for a data layer and it does mean the Zap always has at least two other steps.
- **The live endpoints do not fit a Zap.** Live resolution hands back a task id and completes in the background. A Zap has no loop, so the honest options are the cached actions here, or n8n where polling is natural. Polling is free and off the rate-limit clock wherever you do it.
- **Under 2 credits the free checks stop too.** When a Reverse Contact workspace drops below 2 credits the free check endpoints return 402 rather than a result, because the fetch a check precedes can itself cost 2. A Zap built to check first and enrich second therefore fails at the check, not at the step you would expect.
- **Credit packs expire after 3 months.** Packs from 5K to 1M credits are valid 3 months, so a Zap that runs in bursts can reach the end of a quarter with credits it paid for and cannot use. Above roughly 15,000 lookups a month Reverse Contact's own pricing page points at an Unlimited plan instead.

## The APIs, if you are building around it instead

### Reverse Contact

- **Base:** `https://api.reversecontact.com/v2`
- **Auth:** `Authorization: Bearer rc_your_api_key`. Keys are created in Workspace > API Keys.

| Call | Request | What it does |
|---|---|---|
| `POST /v2/enrich/persons` | `{ "email": "j.okafor@northwind.io" }` | Resolve a person from an email, a name plus company, or a profile URL. Cached resolution, returns in the response. |
| `POST /v2/enrich/companies` | `{ "domain": "northwind.io" }` | Resolve a company from a domain or a name. |
| `POST /v2/fetch/persons` | `{ "linkedInUrl": "..." }` | Standard profile lookup from the database. |
| `POST /v2/fetch/persons/live` | `{ "linkedInUrl": "..." }` | Live on-demand resolution. ASYNCHRONOUS: returns a webhookId to poll, not a record. |
| `POST /v2/search/people` | `{ "filters": { "currentCompanyDomain": "northwind.io" } }` | Filtered people search. 1 credit a profile delivered, and /v2/search/people/count is free. It replaced /v2/search/persons, which returns 410 Gone since 13 October 2026. |
| `POST /v2/search/organizations` | `{ "filters": { "companyDomain": "northwind.io" } }` | Filtered company search. A domain can also go straight to a company through POST /v2/enrich/companies, or through the enrich_company MCP tool since November 2026. |
| `POST /v2/contact/email` | `{ "linkedInUrl": "..." }` | Find an email. ASYNCHRONOUS: returns a taskId to poll. 3 credits for a professional address, 5 for a personal one, 8 for both, refunded when neither is found. |
| `GET /v2/webhooks/:webhookId` | - | Poll an async job until status is "succeeded". Polling is free and does not count against the rate limit. |

Response shape:

```json
{
  "success": true,
  "data": {
    "person": {
      "fullName": "Jane Okafor",
      "headline": "VP Sales at Northwind",
      "location": "London, United Kingdom",
      "linkedInUrl": "https://linkedin.com/in/...",
      "currentPosition": { "title": "VP Sales", "companyName": "Northwind", "startDate": "2023-04" },
      "emails": [], "experience": [], "education": [], "skills": []
    },
    "company": { "name": "Northwind", "domain": "northwind.io",
                 "industry": "Software Development", "employeeCount": 220 }
  },
  "error": null,
  "metadata": { "requestId": "req_...", "executionTimeMs": 480, "updatedAt": "2026-09-01T..." },
  "quotas": { "creditsConsumed": 1, "workspace": { "credits": { "total": 10000, "used": 4521, "left": 5479 } } }
}
```

**Rules that will cost you time if you skip them:**

- A miss returns **null**, not a best guess. Every response carries a confidence score, and you can raise the precision threshold on the request. Branch on it: do not treat a low-confidence answer as a match.
- Use the cached endpoints anywhere that must answer inside one HTTP request. The `/live` endpoints return a task and need polling.
- `quotas.workspace.credits.left` is on every response. Log it, or you will find out about the balance from a 402.
- Credit costs per call are published and a dollar rate per lookup is not: 2 credits for a reverse lookup from an email, 1 for a cached profile lookup, 2 for a live refresh, 3 for a business email and 20 for a direct phone number, with the last two charged only when one is found. Checks and the search count endpoint are free. Credit packs expire after 3 months. Do not hard-code a dollar cost assumption.

**MCP server:** `https://api.reversecontact.com/mcp`

- Auth: OAuth 2.1 where the client supports it, otherwise `Authorization: Bearer rc_your_api_key`.
- Tools: `enrich_person`, `enrich_person_live`, `enrich_company`, `enrich_company_live`, `search_persons`, `search_companies`, `check_usage`, `check_task`
- Streamable HTTP, JSON-RPC 2.0. The `_live` tools return a task id that `check_task` polls.

Docs: https://docs.reversecontact.com/getting-started

## Sources

- Reverse Contact on Zapier: https://zapier.com/apps/reverse-contact/integrations
- Reverse Contact integrations: https://www.reversecontact.com/integrations
- Reverse Contact: credits: https://docs.reversecontact.com/guides/credits
- Reverse Contact: rate limits: https://docs.reversecontact.com/guides/rate-limits
- Reverse Contact pricing: https://www.reversecontact.com/pricing
- Reverse Contact API documentation: https://docs.reversecontact.com/getting-started
- 14 practitioner threads read on 2026-10-11, summarised on the page: https://www.reversecontact.com/integrations-hub/zapier-integrations/zapier-reverse-contact-integration#reddit
- This pair, with the reasoning behind each step: https://www.reversecontact.com/integrations-hub/zapier-integrations/zapier-reverse-contact-integration

---

*Published by Reverse Contact, which appears in this directory as a data provider.
No other vendor pays for placement. Where a vendor publishes no public figure, this file says so
rather than estimating. Reverse Contact costs are stated in credits, which it publishes; no dollar
rate per lookup appears here, because none is published and dividing a pack price is not their number.*
