A native app with nine operations, and a miss that costs nothing.
- Moves: Contacts, Companies
- Needs: A Zapier plan with enough tasks, and a Reverse Contact API key
Six integrations, and no plan upgrade needed on the other side of any of them. You pay in tasks instead, charged per step rather than per Zap, and several of these apps cannot start a Zap at all.
The connector of last resort, and often first resort.
Zapier is the connector of last resort and, often, of first resort. When a pair in this directory has no native integration, Zapier usually has both sides: HubSpot alone reaches more than 8,000 apps through it, and the Zapier app has 173,000 installs on the HubSpot marketplace. Nothing else here has that reach, which is why all six of these pairs are metered rather than gated by a tier on the other vendor's side.
You pay for the reach in tasks, and the unit is the part teams get wrong. A task is charged per step rather than per Zap, so a five-step Zap over a thousand rows is five thousand tasks. That makes the per-record loop the expensive shape and a batch the cheap one. Latency is a line item too: how quickly a Zap runs is a function of the plan you bought, which is a strange thing to discover after designing something time-sensitive around it.
The constraint nobody expects is the trigger. The Reverse Contact app has no triggers at all, the LinkedIn app has none either, which rules out most of what people want from it, and in Slack a message posted by a bot cannot start a Zap. So the shape that works here is Zapier in the middle of a chain that something else begins: a form, a CRM workflow, a schedule. Design it the other way round and you will get a long way before finding out.
Zapier sits in the orchestration layer, with 3 other tools in this directory. Counted across the whole directory it reaches 6 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 freeA native app with nine operations, and a miss that costs nothing.
The widest surface on this site, metered by the minute your plan polls at.
Five access tokens per org, and the sixth app silently revokes the first.
One message a second per channel, and a bot message cannot start a Zap.
Five instant triggers, and the one you want most is the one that polls.
No triggers at all, so nothing on LinkedIn can ever start a Zap.
4 things that decide whether a Zapier integration will work for you, in the order they usually bite.
The meter runs per step, so the number to estimate is rows multiplied by steps rather than how many Zaps you have built. A filter that drops nine rows in ten still costs a task on all ten. Before committing to a per-record design, price the same job as a batch, or in an orchestrator that does not bill you by the action, because this is the one decision that separates a sustainable Zap from a surprising invoice.
Two of the six apps here cannot start a Zap, and in Slack a bot message cannot either, so for most of this hub Zapier is the middle of your chain rather than the beginning. Outreach is the exception and the one to copy: five of its six triggers fire instantly, which is why it can open a chain as well as close one. Confirm the trigger exists on the app you need it from as the first thing you do rather than the last.
The HubSpot and Salesforce pages record the same finding: how fast a Zap fires depends on the Zapier plan you are on. If anything downstream is time-sensitive, a speed-to-lead alert most of all, that is a pricing question rather than a configuration one. Read it before you promise a response time to anybody.
Zapier holds one connection per HubSpot account, and Salesforce allows only five access tokens across every third-party app, a ceiling you can reach without noticing because everything else you have connected is spending from it. Count what is already connected on the other vendor's side before adding another, and expect admin work before the first Zap runs.
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.
A native app with nine operations, and a miss that costs nothing.
One way, in → 02The widest surface on this site, metered by the minute your plan polls at.
Two-way sync → 03Five access tokens per org, and the sixth app silently revokes the first.
Two-way sync → 04One message a second per channel, and a bot message cannot start a Zap.
Events only → 05Five instant triggers, and the one you want most is the one that polls.
Two-way sync → 06No triggers at all, so nothing on LinkedIn can ever start a Zap.
One way, in →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.
On the other vendor's side, no: all six pairs here are metered rather than gated, and the HubSpot one explicitly needs no HubSpot upgrade. On Zapier's side you need a plan with enough tasks, and the Salesforce integration needs a paid one. The free plan carries a monthly task allowance, and paid plans are priced by task volume on zapier.com/pricing.
Throughput is set by your plan rather than published as a request ceiling, so the limits that actually stop a Zap belong to the app at the other end. The ones recorded here: Slack accepts one message a second per channel and makes no promises above that, HubSpot's daily cap is shared across every app on the account while its burst limit is not, and LinkedIn's limits apply and are not published at all.
No. The native Reverse Contact app has actions and no triggers, so it enriches a record a Zap already holds rather than starting one when a profile changes. The pattern that works is a trigger from your CRM or a schedule, then the enrichment as a step, then the write back. The live endpoints do not fit a Zap at all, because they return a task id to poll and a Zap has nowhere to wait.
You map per step, choosing which field from the previous step fills which field in the next, which is flexible and is also where the quiet errors live. The documented one on these pages is dates: a HubSpot date property rounds down to UTC midnight, so a timestamp that was right in your timezone can land a day early. Check one record end to end after any mapping change rather than trusting the preview.
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.