Five instant triggers, and the one you want most is the one that polls.
An Outreach contract, an Outreach account that can authorise the app, and a Zapier plan sized to your task volume
Contacts, Companies, Deals, Tasks, Activities, two-way sync.
The best-equipped app on the Zapier hub, and the only one here that can start a Zap on more than one kind of event. Five of its six triggers are instant, the actions cover the whole prospect lifecycle from create to sequence enrolment, and there is a beta raw API Request for anything the four named actions do not reach. The two things to design around are that the one trigger you want for closed-loop reporting is the only one that polls, and that enrolment has no idempotency: nothing stops a Zap adding the same person to the same sequence twice.
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 |
|---|---|---|
| New prospects | One way, out | New Prospect fires instantly when a prospect is created, which makes Outreach a usable starting point for a chain rather than only a destination. |
| Calls and task updates | One way, out | New Call and Updated Task both fire instantly. These are the activity events, and they are what a CRM or a warehouse wants if it is keeping its own record of what the team did. |
| Account and opportunity changes | One way, out | Updated Account and Updated Opportunity fire instantly. Note the asymmetry: there is no trigger for a new account or a new opportunity, only for updates to one. |
| Completed sequence tasks | One way, out | The one polling trigger, checked every 15 minutes on the free plan, and the only one that requires a Sequence ID up front. It watches the sequence you name rather than all of them. |
| New prospects, written back | One way, in | Create Prospect takes first and last name, email addresses, and the account, opportunity, stage, persona and owner ids. The ids are the hard part: they are Outreach ids rather than names. |
| Sequence enrolment | One way, in | Add Prospect to Sequence, usually preceded by Find Sequence to resolve the sequence by name. This is the action the pair exists for and the one with no duplicate protection. |
| Anything else | One way, in | API Request is a beta action making a raw HTTP call that carries the integration's authentication, so the whole Outreach API is reachable without building an OAuth app of your own. |
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.
The thing that decides how you wire this is which identifier each action needs, and the answer is almost always an Outreach id rather than a name. Only one action resolves a name for you, and it resolves sequences.
| In Outreach | In Zapier | What to know about the match |
|---|---|---|
| Create Prospect | A new Outreach prospect | First Name, Last Name and Email Addresses, plus Account ID, Opportunity IDs, Stage ID, Persona ID and Owner ID. Every one of those ids has to come from somewhere else in the Zap. |
| Find Sequence | A sequence, by name or id | The only search action, and the only place a human-readable name is resolved for you. Put it before any enrolment step. |
| Add Prospect to Sequence | An enrolment | Takes the prospect and the sequence. No duplicate check, so running it twice enrols twice. |
| API Request (Beta) | Any Outreach endpoint | A raw HTTP request carrying the integration's authentication. Beta, and the escape hatch when the four named actions do not cover the job. |
| New Prospect, New Call, Updated Task | A Zap, instantly | The instant triggers, carrying the Outreach record that changed. These are what let Outreach begin a chain rather than only receive one. |
| Completed Sequence Task | A Zap, within 15 minutes | Polling rather than instant, and scoped to one Sequence ID. The free plan checks every 15 minutes. |
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: six field mappings and four documented exclusions, each one's note, and the three 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.
Read this table as a shopping list for the steps before the one you actually want. Enrolling a prospect looks like one action and is realistically three: resolve the sequence, check for the duplicate, then enrol, with the meter running on each.
Not an editions grid, because no plan on either side decides whether this pair works: Outreach needs a contract and Zapier needs enough tasks. The question that changes a build is which events are instant and which are not, and the answer is uneven in a way the app listing does not make obvious. Pick one on each side and the grid marks the answer.
Pick one on each side.
| Outreach event | Starts a Zap instantly | Polls for changes | Needs a Sequence ID first |
|---|---|---|---|
| New Prospect | Yes | No | No |
| New Call | Yes | No | No |
| Updated Account | Yes | No | No |
| Updated Opportunity | Yes | No | No |
| Updated Task | Yes | No | No |
| Completed Sequence Task | No | Yes | Yes |
Counted off that grid, of eighteen pairings: seven give you yes, eleven give you no. Five rows read identically and the sixth is the whole point. Completed Sequence Task is the event most teams want, because it is the one that closes the loop on whether the sequence did anything, and it is the only one that is neither instant nor global: it polls, and it watches a single sequence you have to name when you build the Zap.
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.
Outreach: users
The rate limit is 10,000 requests an hour metered per user, so the account you authenticate with determines whose budget a bulk run spends. A dedicated service user is the right answer and it is much easier to do now than to change once Zaps depend on it.
Zapier: the Outreach app
Add the Outreach app and authenticate as that user. Outreach uses OAuth 2.0, so this is a browser consent rather than a key you paste, and the person completing it needs an Outreach account with the rights to authorise an application.
Zapier: trigger
New Prospect, New Call, Updated Account, Updated Opportunity and Updated Task are all instant. Completed Sequence Task polls, every 15 minutes on the free plan, and asks for a Sequence ID. Choose deliberately: the polling one is often the one people want and it behaves differently from the rest.
Zapier: Find Sequence
Find Sequence takes a sequence name or an id and returns the sequence. Put it in front of the enrolment step so the Zap keeps working when somebody rebuilds a sequence, which changes the id and does not change the name.
Zapier: a filter
Add Prospect to Sequence has no idempotency of its own. Put a filter or a lookup before it so a prospect already in the sequence is not added again. This is the step the integration cannot do for you and the one that stops somebody getting two first emails.
Zapier: API Request (Beta)
The beta API Request action makes a raw HTTP call carrying the integration's authentication, so the rest of the Outreach API is available without building your own OAuth app. It is beta, so treat it as the escape hatch rather than the foundation.
Nothing is installed inside Outreach, so removing this is a Zapier action and an authorisation to revoke. What persists is every prospect the Zaps created and every enrolment they made, which is the usual asymmetry: the connection is reversible and the records are not.
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-zapier/SKILL.md https://www.reversecontact.com/integrations-hub/skills/outreach-zapier.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.
WhyAdd Prospect to Sequence was run twice. The action has no duplicate protection and reports success both times.
Put a filter or a lookup in front of the enrolment step and make the Zap stop when the prospect is already enrolled. Nothing in the integration will do this, so it is a design step rather than a setting.
WhyThe Sequence ID was hard-coded and rebuilding a sequence changes it.
Use Find Sequence to resolve the sequence by name and feed its output into the enrolment step. The name survives a rebuild and the id does not.
WhyIt is Completed Sequence Task, the only polling trigger, which Zapier checks every 15 minutes on the Free plan.
Accept the delay or redesign around an instant trigger. The other five are instant, so if the latency matters more than the specific event, one of them is usually close enough.
WhyThe action takes Account ID, Opportunity IDs, Stage ID, Persona ID and Owner ID, and none of those accepts a name.
Resolve the ids earlier in the Zap, from the record that triggered it or from a lookup. Find Sequence only resolves sequences, so everything else has to arrive already as an id.
WhyOutreach meters 10,000 requests an hour per user, and the connection authenticated as a person rather than as a service account.
Reconnect as a dedicated Outreach user so the Zaps have their own budget. This is much easier before Zaps depend on the connection than after.
WhyThe meter is per step. An enrolment is at least two steps, and a filter and a lookup make it four.
Count rows multiplied by steps rather than Zaps, and consider batching or an orchestrator billed differently if the arithmetic does not work. The Zapier hub page has the same warning for every pair on it.
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 January 2020 to July 2026 were read in full on 28 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.
The biggest issue with complex stacks isn't just the software cost, it is the maintenance overhead. Every webhook and API connection you set up is a point of failure waiting to break when a platform updates its system.
r/GrowthHacking·July 2026·1 points
The right frame for this whole pair. A Zap between Outreach and anything else is a connection somebody owns, and the integration gives you no duplicate protection and no alert when a sequence id changes underneath it. Both of those are maintenance you are signing up for rather than features you are buying.
this cost of the stack part nobody accounts for early on. seen teams add up a $79/mo tool then realize the actual monthly spend is closer to $300-400 once proxies, enrichment, and the glue tooling (zapier, clay) get counted.
r/GrowthHacking·July 2026·1 points
Specifically true here because Zapier bills per step. Enrolling one prospect is two actions before any filter, so the glue cost scales with prospects rather than with the number of Zaps, and it is the part nobody puts in the business case.
I'd probably keep it simple given your volume. If it's just you and mostly cold email, Apollo is hard to beat early on. You can find leads, run sequences, and track deals without stitching a bunch of tools together.
r/gtmengineering·February 2026·2 points
A fair challenge to this page. Outreach is a quoted-per-seat product and this integration costs tasks on top, so at low volume the honest answer may be one tool that does both. The pair earns its place when the sequencer is already chosen and the rest of the stack has to reach it.
Go for something that combines the CRM and the sequencer so you aren't jumping between apps.
r/gtmengineering·March 2026·2 points
Worth reading next to the Outreach hub, which notes that Outreach treats CRM sync as part of the product with per-object mapping in both directions. If you own Outreach, the combining has largely been done, and Zapier is for everything that is neither the CRM nor the sequencer.
Industry standard is Sales Navigator + Zoominfo contacts -> Outreach/Salesloft for cadence -> Synced with Salesforce
r/sales·January 2020·3 points
The oldest quote on this page and the one that has aged best. The shape is unchanged six years later: discovery, then cadence, then the CRM as the record. Zapier's job in that chain is the arrows, and this app is well equipped for it precisely because it has triggers at both ends.
Almost nobody writes about wiring these two together, so the search was the job instead: whether to glue a sequencer to the rest of the stack at all, and what the glue costs. Finding even this much needed a fix to the tooling, because "Outreach" is an ordinary English word and searching it returned threads about cold outreach as an activity rather than about the product.
None of these describes the pair, which is the honest state of the discussion rather than a gap in the search. What they corroborate is the shape of the decision: the integration is capable, the maintenance and the per-step meter are the real costs, and at low volume one tool that does both jobs may beat two tools and the glue.
This is the pair that makes the Zapier hub's general rule wrong in a useful way. Most apps there are the middle of a chain something else starts, because they have no triggers worth using; the Reverse Contact app has none at all and the LinkedIn app has none either. Outreach has five instant ones, so it can be the beginning of a chain as well as the end. If you have been designing around Zapier being unable to start anything, this is the app where that assumption stops holding.
The enrolment path is two actions and the order matters more than it looks. Build it this way round:
The middle step is the one teams skip, and it is the reason a sequence occasionally sends the same person two first-touch emails. The integration will do that cheerfully and report success both times.
Think about which user the connection authenticates as before you build anything. Outreach meters its 10,000 requests an hour per user rather than per organisation, which is unusual and useful: a Zap running as its own service account has its own budget and cannot starve the reps. Connect it as the person who happened to build it and that person's allowance is what a bulk run spends.
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, Zapier 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, and it is better than most of the apps on this hub. The Outreach Zapier integration publishes six triggers and four actions: New Prospect, New Call, Updated Account, Updated Opportunity and Updated Task all fire instantly, Completed Sequence Task polls, and the actions are Create Prospect, Find Sequence, Add Prospect to Sequence and a beta raw API Request. Five instant triggers is unusual here. Two of the other apps on the Zapier hub have no triggers at all.
Yes, with two steps rather than one. Add Prospect to Sequence needs the sequence, and Find Sequence is the search action that resolves a sequence by name or ID first. Build it as Find Sequence then Add Prospect to Sequence, because hard-coding an id means the Zap breaks silently the day somebody rebuilds the sequence.
Not instantly, which is the one asymmetry worth planning around. Completed Sequence Task is the only polling trigger of the six, and Zapier documents checking for new data every 15 minutes on the Free plan. It also requires a Sequence ID up front, so it watches one sequence rather than all of them.
On Outreach, you need a contract, which you have if you are reading this, and an account that can authorise the app. Outreach publishes no public rate card. On Zapier you need enough tasks, and the meter runs per step rather than per Zap, so the cost of this pair is the number of steps multiplied by the prospects rather than the number of Zaps you build.
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.