10,000 requests an hour per user, and nothing to install inside Outreach.
A Reverse Contact API key and Outreach API access through an OAuth app
Contacts, Companies, one way, in.
Outreach is the easiest sequencer in this directory to enrich against, and the reason is mundane: the rate limit is 10,000 an hour per user rather than a shared team budget, so a backfill over an existing prospect list is an ordinary thing to do rather than a negotiation. There is nothing to install, which is consistent with how Reverse Contact ships everywhere, and the real work is deciding what happens to a prospect whose lookup returned null before a cadence picks them up.
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, out | A webhook on prospect created, or a scheduled sweep over prospects missing a title. |
| The enrichment | One way, out | POST /v2/enrich/persons with the prospect email. 2 credits on a match, free for a prior freshness check. |
| Write-back | One way, in | PATCH the Outreach prospect with title, company, seniority and whatever else the schema holds. |
| Cadence entry | One way, in | Gate it on the enrichment having resolved, so an unknown prospect does not get the generic first touch. |
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.
There is nothing to map in Outreach, because there is no app: a middle layer reads the prospect, calls Reverse Contact and PATCHes the answer back. What is worth laying out is which part of the response goes where, and which part of it should stop the send instead.
| In Outreach | In Reverse Contact | What to know about the match |
|---|---|---|
| Prospect emails | POST /v2/enrich/persons, 2 credits | Identity, the current role, history, education, skills and location on one schema. A miss returns null with a confidence score and costs nothing at all, because every 4xx and 5xx is free. |
| Account domain | POST /v2/enrich/companies, 2 credits | Firmographics from a domain or a company name. Run it on the account rather than once per prospect attached to it, which is both cheaper and more consistent. |
| A profile URL already on the prospect | POST /v2/fetch/persons, 1 credit | Half the price, and unmetered from the $249 plan rather than the $699 one. Prospects sourced from a profile rather than from a form often already carry one. |
| currentPosition.title | Prospect title, in a custom field | The field most cadence openers reference, and the one most likely to be out of date on a list built six months ago. |
| currentPosition.companyName | A suppression check, not a field | Compare it with the account the prospect is filed under. A disagreement is the single most useful signal on this page: that person has moved, and the cadence written for their old job is about to reach their new one. |
| metadata.updatedAt | A custom date field | When the record was last updated. Store it, and the next sweep can skip everything refreshed recently instead of paying to re-resolve it. |
| Prospect update | PATCH /api/v2/prospects/:id | One request against a limit of 10,000 an hour per user. Write the custom fields and leave the rep-maintained ones alone. |
| Anything outbound to Reverse Contact | Only what your middle layer sends | This is a read layer. No prospect, cadence or activity is sent anywhere, and there is nothing in the product to send it to. |
Every page in this directory treats an enrichment response as a set of values to write. On a sequencer it is also a set of reasons not to send, and that is the half nobody builds. Each row below is a documented field in the response, and each one is a prospect who should leave the cadence rather than receive a better-personalised version of it.
| In the response | Why it is a reason not to send |
|---|---|
| isInRemembrance | The person has died. No amount of personalisation makes this email acceptable, and it is the one failure in outbound that cannot be apologised for |
| currentPosition.companyName disagrees with the account | They have changed job. The cadence was written for the old role and the pitch no longer applies, so this is a re-qualification rather than a refresh |
| isOpenToWork | They are looking to leave. Treat it as a reason to check the opener rather than an automatic stop, but it is a judgement a human should make once |
| data is null, with a confidence score | Nothing was confidently matched. Sending the fallback text is a choice, and on a cold list it is usually the wrong one |
| metadata.updatedAt, from a long time ago | The record is stale rather than wrong. This is the case for a 2-credit live refresh, and the only case for one |
| hasVerificationBadge and followersCount | Not suppression. Worth noting because they are the two fields teams reach for as a seniority proxy, and neither is one |
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 in the response rows and four documented exclusions, each one's note, and the nine 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.
Outreach is the easiest sequencer here to enrich against and that makes the suppression table more important rather than less, because nothing in the rate limit will stop you sending a well-personalised email to somebody who left the company a year ago. The one field to check first is the current employer, and it is checked by comparing two values rather than by reading one.
The build is nearly identical on all five: read the record, call the API, write it back. What differs is the metering, and the differences are large enough to change whether a backfill is an evening or a negotiation. Every figure below is from the vendor's own rate-limit documentation. Pick one on each side and the grid marks the answer.
Pick one on each side.
| The sequencer | The budget is yours rather than shared | A full backfill is an ordinary thing to do | No documented surcharge for deep paging | The key travels in a header, not a URL |
|---|---|---|---|---|
| Outreach: 10,000 an hour, per user | Yes | Yes | Yes | Yes |
| Salesloft: 600 cost a minute, per team | No | Partly | No | Yes |
| Smartlead Standard: 1,000 an hour, per key | Partly | No | Yes | No |
| lemlist: 20 per 2 seconds, per key | Partly | Partly | Yes | Yes |
| Instantly: 6,000 a minute, per workspace | No | Yes | Yes | Yes |
Counted off that grid, of twenty pairings: eleven give you yes, four give you partly, five give you no. The top row is why this page exists in the shape it does: on Outreach the metering is nobody else's business and a backfill is an afternoon. Salesloft meters per team instead and charges more for deep pages, which turns the identical build into a scheduling problem, and the last column is a reminder that the easiest API to call is not always the safest place to put a key.
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.
Your own process, not a settings screen
A sequencer renders the first touch from whatever the prospect record holds at send time. Enriching somebody already two steps into a cadence improves the fourth email and cannot repair the first, which is the one that decided the reply. Everything else on this page is reversible and this is not.
Outreach: custom fields on Prospect
Use custom fields rather than the ones a rep edits between calls. A sequencer is the one place in a stack where a wrong value is not merely untidy: it is sent to somebody, with your name on it, and no later correction reaches them.
Outreach: the developer portal
There is no app to install and nothing in Outreach that calls an external API, so the only way in is the API itself. Reading and writing prospects needs prospects.read and prospects.write; asking for more is a conversation with whoever approves it.
Any Outreach API response
The documented limit is 10,000 requests an hour per user, and Outreach states in as many words that it reserves the right to adjust limits at any time. Every response carries X-RateLimit-Limit, X-RateLimit-Remaining and X-RateLimit-Reset, the last aliased as Retry-After.
POST /v2/fetch/persons/check
The free check says whether a profile is cached and when it was last updated, so a sweep over an existing prospect list spends 2 credits only on the records that need it. On a list of any size this is the difference between a budget and a bill.
Your middle layer
The response carries more reasons not to send than reasons to send. A current employer that disagrees with the account on the prospect, an isInRemembrance flag, an isOpenToWork flag: each one is a prospect who should leave the cadence rather than receive a better version of it.
Outreach: PATCH /api/v2/prospects/:id
Update the record first and add to the cadence second, in that order, every time. The sequence of those two calls is the whole content of this build, and getting it the other way round is the mistake step one is about.
Your middle layer, with a limit on it
At 10,000 an hour per user you have room to be careless, which is its own hazard. A hundred-record pass tells you the real resolved rate on your own list, and that number rather than any published match rate is what decides whether the rest is worth running.
Only the first step is irreversible and it is the one with no screen attached to it. Outreach makes the mechanics easy enough that the ordering question is the entire design, which is the opposite of the Salesloft version, where the shared rate limit decides what is possible before anybody argues about ordering.
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/outreach-reverse-contact/SKILL.md https://www.reversecontact.com/integrations-hub/skills/outreach-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 sequencer renders each step from the record as it stands at send time, and the prospect was added to the cadence before the enrichment ran.
Enrich first, add to the cadence second, with no exceptions. Nothing repairs a sent email, which is why this is the one ordering decision on the page that matters.
WhyThe enrichment wrote a title and nobody compared the returned current employer with the account the prospect sits under.
Compare currentPosition.companyName against the account and route disagreements out of the cadence. This is three lines in the middle layer and it is the highest-value check on the page.
WhyOutreach rate-limits per user at 10,000 requests an hour, and bulk endpoints and Kaia apply their own rules, with Kaia at 3 calls a second and 6,000 a day at org level.
Read X-RateLimit-Remaining and honour X-RateLimit-Reset, which is aliased as Retry-After. The error body names the limit it thinks you exceeded and the time it resets, which is more than most APIs give you.
WhyOutreach states that it reserves the right to adjust API rate limits at any time to safeguard platform performance and ensure fair use.
Read X-RateLimit-Limit from a live response rather than hard-coding 10,000. A worker that discovers its own ceiling survives a change that a worker with a constant in it does not.
WhySteps already rendered and sent are gone, and a step scheduled for later picks up the current record. There is nothing to re-render.
Check the rendered preview of the next step rather than the record. If the cadence has moved past the step that used the field, the enrichment improved nothing a recipient will see.
WhyBelow 2 Reverse Contact credits the free Check endpoints are paused as well and answer 402 NO_CREDITS, because the fetch a check precedes can itself cost 2.
Watch quotas.workspace.credits.left, which rides on every response. GET /v2/usage keeps answering whatever the balance, so a scheduled balance check never fails for the reason the lookup did.
WhyA published figure is a global average over a provider's whole corpus and your list is not that corpus. Reverse Contact publishes 70%+ as an identity match rate and says to measure your own.
Run 500 of your own rows and count. That number is the one that decides the economics of this build, and nothing else is a substitute for it.
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.
Change both paths in the middle layer. On this route that is ordinary version-controlled code, which is one advantage of there being no app to configure.
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 2023 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.
Lead gen experts what's your workflow to enrich prospect data before outreach? Do you use APIs to pull company hierarchies, industry codes, contact data, or do you rely on your SDRs to research manually? We're testing a new enrichment process to boost email deliverability and personalisation but curious how others handle this efficiently.
r/LeadGeneration·July 2025·2 points
Before outreach, in the title, is the whole of this page. The two options offered are an API or an SDR doing it by hand, and that is the real comparison: there is no third option where the sequencer fills the field itself, which is why there is nothing to install inside Outreach.
I use Clay to do this. I use their formulas a lot to clean lists before enriching. Our SDRs and sales team doesn't do any manual research. We do this for them using Clay. We do similarly with our inbound leads by enriching for what our Sales team needs while also qualifying leads with the data. I update the life cycle stage of those unqualified leads which then allows my team to focus only on the best inbound leads.
r/LeadGeneration·July 2025·1 points
Two things worth copying. Cleaning the list before enriching it, so you are not paying to resolve rows that were never going to qualify, and using the enrichment to disqualify as well as to personalise. The second is the suppression table above, arrived at independently and described as a lifecycle stage rather than as a block.
We went through something similar about a year ago, trying to cut down the time our SDRs spent on manual research before first contact. Tried running everything through Apollo for a while. It covered a lot of ground but the enrichment quality was inconsistent enough that the scoring felt unreliable.
r/nocode·April 2026·1 points
The most quietly expensive failure on this whole page, because nothing errors: the fields fill, the model runs, and the scores are noise. A provider that returns null with a confidence score rather than a best guess is the thing that makes a score trustworthy, and it is worth more than coverage on a page whose output is a cadence somebody receives.
Depends if reliability matters to you. [...] And It's always a good idea to keep a human review step until you're confident everything works perfectly
r/openclaw·March 2026·6 points
Written about an agent framework rather than about an enrichment API and it transfers exactly. On a sequencer the review step is not about the enrichment being wrong, it is about the suppression rule being incomplete, and reviewing the first hundred by hand is how the rules above get written in the first place.
Use sales navigator and Airscale combo. Sales navigator has the most reliable data compared to other paltforms like : Apollo. If you can find your ICPs in sales nav through its filters that's ideal. Then just use Airscale to scrape the leads and enrich with verified emails/phone numbers.
r/LeadGeneration·August 2025·1 points
One person's comparison rather than a benchmark, and the shape is the useful part: source the list somewhere, resolve it somewhere else. A list sourced from a profile rather than from a form arrives with a profile URL on it, which is the 1-credit cached lookup instead of the 2-credit reverse one.
Nobody discusses this pair by name, so the search was for the job: enriching a prospect before a cadence touches them. The threads are about where the research happens rather than which tool does it, and they agree on the ordering this page argues for. The most useful contribution is from somebody whose enrichment quality was good enough to pass and not good enough to score on, which is the failure that looks like success.
Not one of the five is about Outreach, which is itself the finding on the easiest sequencer here to enrich against: with 10,000 requests an hour per user there is nothing to work around, so every thread is about the data and the ordering instead. The one to act on is the third, because a scoring model built on inconsistent enrichment is the failure that reports success, and the suppression table above is what catches it.
Every sequencer page in this directory makes the same argument, which is that a cadence is only as good as the row it renders from, and Outreach is where the argument is easiest to act on. The API is generous, the object model is explicit about prospects and accounts, and a backfill is not a conversation with anyone. The thing to design is not the plumbing but the branch: what a prospect with a null lookup should do, decided before the first cadence runs rather than discovered in a reply rate.
Put it beside the other half of the duopoly and the difference is the meter. Salesloft shares one budget across its whole team, 600 cost a minute whatever the headcount, so the integration you add competes with the ones already there. Outreach gives each user 10,000 an hour. Same category, same price bracket, and a bulk enrichment pass is routine on one and a planning exercise on the other.
The middle layer is the part nobody budgets for, and the cheapest version of it needs no code. The native app on Zapier has an Outreach connection on one side and a Reverse Contact enrichment on the other, and it bills nothing when a lookup misses. Where the sequence is fed from a CRM rather than from Outreach itself, enriching at the HubSpot end instead means the data is right before it ever reaches a sequencer.
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 Outreach, 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.
No. Reverse Contact maintains apps on Clay, Zapier and Make and nothing inside any sequencer, so this is a webhook out, an enrichment somewhere else, and a PATCH back to the Outreach prospect. That is three moving parts and roughly an afternoon.
Ten thousand requests an hour, applied per user rather than per org, which is unusually generous for a tool at this end of the market. Every response carries X-RateLimit-Limit, X-RateLimit-Remaining and X-RateLimit-Reset, which doubles as Retry-After. Exceeding it returns 429 with a rateLimitExceeded error naming the time to retry.
Before, every time. A prospect entering a cadence with no title and no company gets the generic version of the first touch, and nothing later in the sequence repairs the first impression. Enrich on prospect creation, and gate cadence entry on whether the enrichment resolved.
Two credits for a reverse lookup when it resolves. A freshness check beforehand is free, which is the cheap way to find out whether a profile is already cached before spending anything. Reverse Contact returns null with a confidence score rather than a guess, so an unresolved prospect is a branch in your pipeline rather than a bad row in a cadence.
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.