One rate limit for the whole team, so your integration competes with the others.
A Reverse Contact API key, and Salesloft API access through an API key or an OAuth app
Contacts, Companies, one way, in.
Salesloft enriches the same way Outreach does and meters it completely differently, and the metering is the page. Six hundred cost a minute for the entire team means an enrichment sweep is not a private decision: it spends the same budget as the CRM sync, the dialler and the conversation intelligence tool. The build itself is ordinary, a webhook on cadence membership, a lookup, a PATCH back. The planning is working out what is already spending the budget before you add to it.
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 person_created, or cadence_membership_created to catch someone as they enter a cadence. |
| The enrichment | One way, out | POST /v2/enrich/persons with the person's email. 2 credits on a match, nothing for a freshness check. |
| Write-back | One way, in | PATCH the Salesloft person with title, company and seniority. Each call draws from the team cost budget. |
| Anything back to Reverse Contact | One way, out | Nothing. This is a read layer, and your middle step decides what Salesloft is allowed to receive. |
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.
Nothing is installed inside Salesloft, so a receiver takes the webhook, calls Reverse Contact and PATCHes the answer back. Every one of those Salesloft calls costs against a budget the whole team shares, which is what makes the cost column the interesting half of this mapping.
| In Salesloft | In Reverse Contact | What to know about the match |
|---|---|---|
| A cadence membership webhook | Your receiver | Three retries 15 seconds apart and then marked failed, so accept quickly and enrich asynchronously. Answering the webhook with the enrichment result is the design that breaks during a deploy. |
| Person email address | POST /v2/enrich/persons, 2 credits | Identity, the current role, history, education, skills and location on one schema. A confident null costs nothing, because Reverse Contact charges 0 credits on every 4xx and 5xx. |
| Account domain | POST /v2/enrich/companies, 2 credits | Firmographics from a domain or a company name. Once per account rather than once per person on it, which also saves the Salesloft reads. |
| A profile URL already on the person | POST /v2/fetch/persons, 1 credit | Half the credits, and unmetered from the $249 plan rather than the $699 one. Worth routing to deliberately wherever the URL is already there. |
| Reading one person | 1 cost, by default | Every endpoint costs 1 unless documented otherwise, and Salesloft reserves the right to change any cost at any time because a cost change does not deprecate anything. |
| Reading page 101 and beyond | 3 to 30 cost, rising by page range | The one documented surcharge: 3 points for pages 101 to 150, 8 for 151 to 250, 10 for 251 to 500 and 30 past 500. This is why a backfill is a cursor poller rather than a loop. |
| Writing the enriched fields back | PATCH a person, 1 cost | Cheap per call and still part of the team budget. Collapse the write into one request per person rather than one per field. |
| Anything outbound to Reverse Contact | Only what your receiver sends | This is a read layer. No person, cadence or call is sent anywhere, and there is nothing in the product to send it to. |
The rest of this directory treats an enrichment response as values to write. On a sequencer it is also a list of reasons not to send, and that half is almost never built. Each row is a documented field, and each is a person who should leave the cadence rather than receive a better-written version of the same email.
| In the response | Why it is a reason not to send |
|---|---|
| isInRemembrance | The person has died. No amount of personalisation makes the email acceptable, and it is the one outbound failure that cannot be apologised for afterwards |
| currentPosition.companyName disagrees with the account | They have changed job, so the cadence written for the old role is about to reach the new one. Re-qualify rather than refresh |
| isOpenToWork | They are looking to leave. A reason for a human to read the opener once, rather than an automatic stop |
| data is null, with a confidence score | Nothing matched confidently. Sending the fallback text is a decision, and on a cold list it is usually the wrong one |
| metadata.updatedAt, from long ago | Stale rather than wrong, which is the one case where a 2-credit live refresh earns its money |
| followersCount and hasVerificationBadge | Not suppression at all. Listed because they are the 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 eight 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 two rows in the middle are the ones to design around. Every call you make is weighted, the weights can change under you, and the only honest way to know what a sweep costs is to read x-ratelimit-endpoint-cost from a live response. A build that assumes last quarter's costs is a build that will one day spend the team's whole minute on page 600 of something.
Salesloft is the only sequencer here that charges more for reading later pages, and the surcharge is steep enough to change the architecture rather than the schedule. The column below asks whether a hundred requests fit inside one minute, measured against the documented budget of 600 cost a minute for the whole team. Pick one on each side and the grid marks the answer.
Pick one on each side.
| How you read the records | A hundred requests fit inside one minute | Room left for the rest of the team | The route Salesloft recommends |
|---|---|---|---|
| Pages 1 to 100, at 1 point each | Yes | Yes | Partly |
| Pages 101 to 150, at 3 points | Yes | Partly | No |
| Pages 151 to 250, at 8 points | No | No | No |
| Pages 251 to 500, at 10 points | No | No | No |
| Page 501 and beyond, at 30 points | No | No | No |
| A cursor poller on updated_at | Yes | Yes | Yes |
Counted off that grid, of eighteen pairings: six give you yes, two give you partly, ten give you no. Three rows reading the same answer is the point rather than an accident: past page 150 the surcharge stops being a tax and becomes a wall. Salesloft says it has found that most customers succeed with a cursor poller on updated_at and publishes a guide for building one, which is unusually direct advice from a vendor about not using its own pagination.
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.
Salesloft: your own integrations list, and a conversation
The rate limit is 600 cost a minute at team level, and Salesloft states plainly that one integration can affect another's limit. So the budget you are designing against is already partly spent by the CRM sync, the dialler and anything else connected. This is the step with no screen and it is the one that decides the design.
Your own process
Steps render from the record at send time, so enriching somebody already in a cadence improves later emails and cannot touch the one that has gone. Enrich, then add to the cadence. This is irreversible in the only way that matters: the recipient already read it.
Salesloft: API keys or an OAuth app
API keys are for your own team only; anything distributed has to be an OAuth application. The client credentials flow for a private app has to be enabled by an admin and then runs with that admin's permissions, which is a question about accountability rather than about tokens.
Salesloft: the updated_at field
Page numbers above 100 cost extra and the surcharge rises steeply. Salesloft recommends a cursor poller on updated_at instead and publishes a guide for it. Taking this decision before you write the loop saves rewriting the loop.
Your receiver
A failing webhook gets three retries 15 seconds apart and is then marked failed. Fifteen seconds is not long enough to ride out a deploy, so the receiver has to accept the call immediately and do the enrichment asynchronously rather than answering with the result.
POST /v2/fetch/persons/check
The free check says whether a profile is cached and when it was last updated, so a sweep spends 2 credits only where it has to. On a shared rate limit this matters twice: fewer Reverse Contact credits, and fewer Salesloft calls to re-read records you were never going to refresh.
Your receiver
The response carries more reasons not to send than reasons to send: a current employer that disagrees with the account, an isInRemembrance flag, a confident null. Each is a person who should leave the cadence rather than get a better version of the same email.
Every Salesloft API response
x-ratelimit-endpoint-cost reports what the request just cost and x-ratelimit-remaining-minute reports what is left. Each endpoint costs 1 by default and Salesloft can change a cost at any time, on the grounds that a cost change deprecates nothing, so the headers are the only reliable figure.
The first and the fourth steps are the ones that make this build survive contact with a busy team, and neither is about enrichment. That is the pattern on every pair in this directory where a shared budget is involved: the integration is easy and the arithmetic is the work. Outreach meters per user instead, which removes this whole conversation.
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/salesloft-reverse-contact/SKILL.md https://www.reversecontact.com/integrations-hub/skills/salesloft-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.
WhyThe limit is 600 cost a minute at team level rather than per integration, and Salesloft states that one integration can affect another's limit. A test team has nothing else running on it.
Read x-ratelimit-remaining-minute at a busy hour and design against that figure. A team with many integrations can ask Salesloft to adjust the limit, which is a conversation rather than a setting.
WhyPage numbers above 100 carry an additional cost: 3 points for pages 101 to 150, 8 for 151 to 250, 10 for 251 to 500 and 30 past 500.
Rewrite it as a cursor poller on updated_at, which Salesloft recommends and documents. The cost stays at the default of 1 however far back the history goes.
WhyEach endpoint has a default cost of 1 and Salesloft can change the cost of an existing endpoint at any time, on the stated grounds that the functionality is not deprecated by a cost change.
Read x-ratelimit-endpoint-cost from live responses rather than holding a table of costs. The header is there precisely because the numbers move.
WhyA failing webhook gets three retries 15 seconds apart and is then marked failed, which gives the receiver about 45 seconds in total.
Accept the webhook immediately, queue the work, and enrich asynchronously. A receiver that answers with the enrichment result cannot survive a restart.
WhyThe client credentials flow has to be enabled by an admin and runs with that admin's permissions, so it inherits their account rather than standing on its own.
Use a service account that will outlast an individual, and document whose permissions the integration is actually running with. This is a governance answer rather than a technical one.
WhyThe enrichment wrote a new title and nothing compared the returned current employer against the account the person sits under.
Compare currentPosition.companyName with the account and route disagreements out of the cadence. Three lines in the receiver, and the highest-value check on this page.
WhyBelow 2 Reverse Contact credits the free Check endpoints are paused too and answer 402 NO_CREDITS, because the fetch a check precedes can itself cost 2.
Branch on quotas.workspace.credits.left, which rides on every response. GET /v2/usage keeps answering whatever the balance, so a balance check never fails for the same reason.
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 receiver. It is ordinary version-controlled code on this route, which is the one consolation of there being no app to install.
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 2020 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.
Breeze enrichment is worth it at the 1000 credits/month tier because then it continues to auto enrich your contacts/companies without using additional credits after the first time. If 1000/mo is way too much for you, you might be better off using a third party.
r/hubspot·March 2025·2 points
About a different platform's native enrichment and it is the same arithmetic wherever it is asked: a bundled credit tier is worth it above a volume and not below one. The figures here are that platform's rather than anything on this page, and the structure is what transfers, because this route has the same shape with the threshold in a different place.
You can purchase breeze credits. I find it's good for company data but has barely any contact data at all. Worth it tho for the buyer intent feature which the credits open up
r/hubspot·March 2025·6 points
One person's experience of one product rather than a measurement, and the split it describes is common enough to plan around: firmographics are easier than people. On this pair the two are separate endpoints at the same price, so measuring them separately on your own list is the only way to know which half you are actually buying.
A good reminder of why all applications should be vetted for security controls and data storage policies. I'm interested to see how the breached information will be used going forward. I bet we can expect some interesting e-mails in the next few days regarding our accounts.
r/cybersecurity·September 2025·32 points
From a thread about a Salesloft breach that reached several named security vendors. It is the reason the setup above puts the auth decision on governance grounds rather than convenience: an API key is for your own team, a distributed integration has to be an OAuth app, and the client credentials flow runs with the permissions of whichever admin enabled it.
sequential. one after the other. Find a look-a-like company, then find this profile of person at that companu, then enrich the data (email, phone number), then look for news on that persons profile, then use AI to write personalize copy based on that news, then put that person into a hubspot or outreach or salesloft or smartlead or la growth machine campaign.
r/sales·September 2024·23 points
Salesloft appears at the end of that sentence, as the destination, which is exactly where it sits on this page. Every step before it is an enrichment or a judgement, and the thing worth noticing is that the cadence is the last step rather than the first: the ordering this page insists on is how everybody describes the job when they are not configuring it.
It is a glorified excel table with integrations to a lot of other martech companies and openAI allowing for a waterfall type workflow into outreach tooling. A modern growth hacker can do the same thing with GSheets, Webhooks, and OpenAI.
r/sales·September 2024·53 points
Dismissive and substantially correct, and on this pair the sting is in the second sentence. Anybody can build the receiver; what they cannot do is give it a private rate limit, because the 600 cost a minute belongs to the whole team and Salesloft says plainly that one integration can affect another's.
Nobody discusses this pair by name, so the search was for the job: enriching a cadence before it sends, and paying for the credentials that make it possible. Two of the five are about the economics of buying enrichment from the platform you already own, and one is about what happens when a sales tool holding your tokens is breached, which is the question the governance step in the setup exists to answer.
Three of the five are about money and one is about a breach, which is an unusual distribution and a fair reflection of this pair: the code is a receiver and a PATCH, and everything difficult about it is shared with people who are not in the room. The grid above is the specific version of that, because a cursor poller is the only reading strategy that leaves the rest of the team a budget.
The fact that decides this build is not in the API reference under the endpoint you plan to call. It is in the rate limit page, in one sentence: the limit applies at team level and not at integration level, and another integration can affect yours. Every other sequencer in this directory meters per user, per key or per workspace. Salesloft meters the organisation, which turns a technical decision into a political one, because the enrichment you add is spending a budget somebody else is already relying on.
The practical consequence is a design rather than a warning. Trigger on cadence_membership_created rather than sweeping, so you spend one lookup per person who is actually about to be contacted. Use a cursor on updated_at rather than paging, because past page 100 a request costs three times what it did and past page 500 it costs thirty. Accept the webhook fast and enrich asynchronously, because four attempts fifteen seconds apart is not a retry policy that survives a deploy.
Against the alternative, the trade is clear. Outreach meters per user at 10,000 an hour, so the same work needs no coordination at all. If the sequencer is fed from a CRM, the cheapest answer is to not enrich at this layer: fill the record at the Salesforce end and let the sync carry it, which spends no Salesloft budget whatsoever. Where a middle layer is wanted anyway, the native app on Zapier connects both sides without code.
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 Salesloft, 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.
Not as an app, and nothing inside Salesloft calls an external API, so this is a webhook on cadence membership, a receiver that enriches, and a PATCH back through the API. The build is ordinary and the planning is not, because the rate limit is 600 cost a minute for the whole team: your sweep spends the same budget as the CRM sync and the dialler.
Six hundred cost a minute, applied at team level rather than per integration. Each endpoint costs 1 by default and Salesloft can change a cost at any time without deprecating anything. Deep pagination costs more: 3 points past page 100, 8 past 150, 10 past 250 and 30 past 500.
Because the budget is shared with every other integration already connected. Salesloft states plainly that another integration can affect your rate limit. An enrichment sweep that would be unremarkable on its own can throttle the CRM sync that was there first, and nobody will attribute the slowdown to the thing that was added last.
If you are a customer, yes. If you are building something to distribute, no: Salesloft says API keys are exclusively for customers and that partner applications submitted using API keys will not be approved. Private internal apps can use the OAuth client credentials flow, which an admin enables and which assumes that admin's permissions.
Thirty-seven event types, including person_created, person_updated and cadence_membership_created. That last one is the useful trigger for this build, because it fires exactly when somebody is about to be sequenced. A failing webhook is retried three more times, 15 seconds apart, then marked failed.
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.