Zapier integrations

Zapier integrations, and the trigger that is missing

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.

zapier.com 6 integrations
layerOrchestration
entry$0/mo
authPer-app connections held by Zapier
automationZaps on trigger, schedule or web...
verified2026-09-18
checked Guides written 6 of 6
6integrations checked
1built natively
3sync both ways
0need a plan upgrade
The short version

What decides a Zapier integration

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.

All 6

Every Zapier integration, with what it moves

Start with how the integration is built, because a native app and a webhook you maintain are the same feature with completely different owners.

The data layer

Whichever of these you connect, the integration moves the record. We fill it.

Start for free
Showing 6 of 6
↔

Zapier and Salesforce

Two-way sync
BuiltZapier, Make or n8nMarketplace app

Five access tokens per org, and the sixth app silently revokes the first.

  • Moves: Contacts, Companies, Deals, Custom objects
  • Needs: A paid Zapier plan, a Salesforce edition with API access, and an admin to approve the app
Metered by usage · minutes Read the guide
⋅

Zapier and Slack

Events only
BuiltZapier, Make or n8nMarketplace app

One message a second per channel, and a bot message cannot start a Zap.

  • Moves: Messages
  • Needs: A Zapier plan sized to your task volume, and a free app slot on a free Slack plan
Metered by usage · minutes Read the guide
↔

Zapier and Outreach

Two-way sync
BuiltZapier, Make or n8nMarketplace app

Five instant triggers, and the one you want most is the one that polls.

  • Moves: Contacts, Companies, Deals, Tasks, Activities
  • Needs: An Outreach contract, an Outreach account that can authorise the app, and a Zapier plan sized to your task volume
Metered by usage · minutes Read the guide
←

Zapier and LinkedIn

One way, in
BuiltZapier, Make or n8nMarketplace app

No triggers at all, so nothing on LinkedIn can ever start a Zap.

  • Moves: Messages
  • Needs: A Zapier plan, a LinkedIn account, and page admin rights for company posts
Metered by usage · minutes Read the guide
Buyer's guide

How to pick, and what to check first

4 things that decide whether a Zapier integration will work for you, in the order they usually bite.

01

Count steps, not Zaps

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.

02

Check for a trigger before you design anything

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.

03

Latency is a plan feature

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.

04

Connections are scarcer than they look

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.

Written up

The Zapier integrations with a full guide

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.

Other tools

Integrations for the rest of the stack

Connecting Zapier is half the job

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.

FAQ

Zapier integrations, asked and answered

The questions that come up before anyone opens a setup guide.

Do Zapier integrations need a paid plan?

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.

What are Zapier's rate limits?

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.

Can Zapier trigger on a Reverse Contact enrichment?

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.

How does field mapping work in Zapier?

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.

Checked by

Reverse Contact

We sell B2B people and company data, and we publish this directory. Every tier requirement, sync direction and limit behind the 6 integrations on this page was read from a vendor's own knowledge base, developer documentation or pricing page on the date below. Nothing on it is restated from a press release or a third-party listing.

Where a vendor publishes no public figure, this page says so rather than estimating, which is why no page here prints a cost per enriched record. Reverse Contact appears in this directory as a data provider and publishes it. No other vendor pays for placement, and every link out of a listing or a citation carries nofollow, including the ones that point at Reverse Contact. The only followed links on this page are the two calls to action and the reviewer.

Tier requirements, sync behaviour and documented limits change without notice. Confirm against your own contract before you budget. What has changed since · How we checked, and what we will not claim

Researched and written by

Eugene Suslov

Researched and wrote every page in this directory, and checked every tier requirement, sync direction and documented limit against the vendor's own knowledge base, developer documentation or pricing page.

Verified
2026-09-18
Sources
6 vendor documents
Paid placement
None

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.

Ask an assistant