10,000 requests an hour per user, and nothing to install inside Outreach.
- Moves: Contacts, Companies
- Needs: A Reverse Contact API key and Outreach API access through an OAuth app
Eight integrations, and every one of them starts with an Outreach contract. Five then want something further: a paid add-on, a licence on every seat, or an edition of the other tool you do not have yet.
Bi-directional CRM sync as a core product feature.
Outreach is the only tool in this directory whose price you cannot look up. There is no free tier and no public rate card, so the seats are quoted and the integration is quoted with them. That changes how you read every page here: the question is never whether the connection exists, it is what the connection is bundled with and who has to approve the spend.
What the contract buys is a CRM sync treated as part of the product rather than a bolt-on. Mapping is per object and per field in both directions, sequence activity writes back as CRM activities, and there are governance controls over which side wins a conflict. That is why these pages spend longer on mapping than on connecting, and why the Salesforce and HubSpot pairs are the two worth reading before you buy.
The failure shape to expect is silence: a HubSpot contact that does not exist produces no sync and no error, enrolment skips prospects quietly, Apollo pushes thirteen fields and sends nothing back, and Slack channel alerting is supported for some notification types and not others. None of these throws anything you would see in a dashboard, so the recurring advice on these pages is to check a record by hand on day one rather than to trust a green tick.
Outreach sits in the engagement layer, with 5 other tools in this directory. Counted across the whole directory it reaches 8 of the other 22 tools, and the integration matrix shows that row against every other.
Start with how the integration is built, because a native app and a webhook you maintain are the same feature with completely different owners.
Whichever of these you connect, the integration moves the record. We fill it.
Start for free10,000 requests an hour per user, and nothing to install inside Outreach.
Contacts both ways, email one way, and HubSpot rather than Outreach owns it.
Per-object, per-field control in both directions, and Essentials cannot run it at all.
Four actions, and the one that matters adds an enriched row to a sequence.
Connected once for the whole instance, then every notification is personal.
One Outreach account per Apollo workspace, so connect an admin or nobody sees the sequences.
Five instant triggers, and the one you want most is the one that polls.
Two tiles on Advanced Plus, and the LinkedIn steps are tasks a human does.
4 things that decide whether a Outreach integration will work for you, in the order they usually bite.
Five of the eight integrations here sit behind a paid add-on or a per-seat licence on one side: the HubSpot and Salesforce syncs, the Apollo push, the Slack app and the LinkedIn tile. The connection is rarely the thing you are buying. Get the quote for the add-on and the seat count together, because neither vendor lists it and the number is the decision.
Outreach allows 10,000 requests an hour and meters them per user rather than per organisation, which is unusual in this directory and is good news: a bulk job run as its own user does not starve your reps. Outreach reserves the right to change it. Kaia is metered separately at 3 calls a second and 6,000 a day, and that one is at org level.
The Salesforce sync moves data from the moment it is switched on and resolves conflicts per field, with no history pass. Saving the HubSpot sync restarts the initial pass, which is the opposite trap: a settings change you expected to be free re-runs the whole thing. Decide your switch-on date deliberately and write it down, because it becomes the start of the record.
Clay feeds prospects into a sequence rather than syncing them, so pushing the same table twice enrols the same person twice unless you check first. Apollo skips silently during enrolment. Both pages say the same thing in different words: the push is the easy half, and the guard against double-touching somebody is yours to build.
Each one covers what syncs in which direction, the tier it needs, the limits that bite, when not to use it, and the questions people ask before they start.
10,000 requests an hour per user, and nothing to install inside Outreach.
One way, in → 02Contacts both ways, email one way, and HubSpot rather than Outreach owns it.
Two-way sync → 03Per-object, per-field control in both directions, and Essentials cannot run it at all.
Two-way sync → 04Four actions, and the one that matters adds an enriched row to a sequence.
One way, out → 05Connected once for the whole instance, then every notification is personal.
Events only → 06One Outreach account per Apollo workspace, so connect an admin or nobody sees the sequences.
One way, out → 07Five instant triggers, and the one you want most is the one that polls.
Two-way sync → 08Two tiles on Advanced Plus, and the LinkedIn steps are tasks a human does.
One way, out →The hub most sales stacks are actually built around.
See the 17 integrations →The widest integration surface, gated by edition.
See the 12 integrations →A CRM with a data model you write yourself.
See the 3 integrations →People and company data for every tool in this directory.
See the 22 integrations →Deep native CRM integrations, sold by tier.
See the 3 integrations →An integration moves a record from one system to another. It does not make the record worth moving. Reverse Contact is the layer underneath: one API that resolves an email, a domain or a profile URL into a verified people and company record, with a confidence score instead of a guess.
Free trial, no card required, and 500 credits to start.
The questions that come up before anyone opens a setup guide.
Yes. The Outreach REST API is documented at developers.outreach.io, authentication is OAuth 2.0, and the allowance is 10,000 requests an hour metered per user rather than per org. Bulk endpoints and Kaia have their own rules. You create the OAuth application yourself, so an Outreach API key is really a client id, a secret and a set of scopes, and the Clay integration is the one place here where you cannot refuse any of the twelve scopes it asks for.
Five of the eight: the HubSpot and Salesforce CRM syncs, the Apollo push, the Slack app and the LinkedIn tile, which additionally needs Sales Navigator Advanced Plus on every seat. The two that do not are the ones you build yourself, through the API or an orchestrator, where you pay for throughput instead. Nothing here is included in the way a free marketplace app is included.
The HubSpot and Salesforce ones are native on the Outreach side and listed on those vendors' marketplaces, which is where you install them from. Everything else in this directory reaches Outreach through its API, either directly or through Clay, n8n or Zapier. If you are looking for an Outreach marketplace listing for a tool that is not a CRM, the honest answer is usually that the integration is an API build somebody has already done for you.
Usually because the record on the other side does not exist or does not match. A HubSpot contact that is missing produces no sync and no error message, enrolment skips prospects quietly, and user mapping has to be right before a Slack notification can be addressed to anybody. All three are silent by design rather than by accident, which is why the pages here tell you to verify one record manually rather than watch for a failure that will not arrive.
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.