Five access tokens per org, and the sixth app silently revokes the first.
A paid Zapier plan, a Salesforce edition with API access, and an admin to approve the app
Contacts, Companies, Deals, Custom objects, two-way sync.
Of the three Zapier pairs in this directory, this is the one where the glue costs more than the endpoint. Salesforce is a premium Zapier app, so a paid Zapier plan is mandatory, and the Salesforce side needs My Domain configured, an admin to approve Zapier as an External Client App and an edition that genuinely carries API access. Get through that and you have the same broad surface the other Zapier pairs offer, against the strictest org in the directory. The limit that will find you is not throughput: it is the five access tokens Salesforce allows across every third-party app you own.
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 |
|---|---|---|
| Leads, contacts and accounts | Both ways | Create, update, find and find-or-create in either direction, subject to the connecting user's object and field permissions. |
| Opportunities | Both ways | Created and updated from outside, and usable as a trigger when a field changes. |
| Custom objects and fields | Both ways | Supported, though newly created ones can take time to appear in Zapier's dropdowns. Reloading the field list is the documented workaround. |
| Record updates as triggers | One way, out | The Updated Field on Record trigger returns the most recently updated record. Its test records do not filter by the object you selected, which makes testing misleading rather than broken. |
| Marketing Cloud | Event only | Not supported. Marketing Cloud accounts cannot be connected on this integration at all. |
Three of those five rows move in both directions. The one that does not is Record updates as triggers, and those are the rows that decide how you design around this rather than the ones in the brochure.
Zapier reaches standard and custom objects in both directions. The things worth knowing are about timing and about test data, both of which mislead during setup.
| In Salesforce | In Zapier | What to know about the match |
|---|---|---|
| Leads, contacts, accounts, opportunities | Create, update, find or find-or-create | In either direction, with custom objects and fields supported. |
| A new or updated record | A polling trigger | Every Salesforce trigger polls except one, so latency is your Zapier plan rather than Salesforce's speed. |
| A Salesforce outbound message | An instant trigger | The only instant path on this pair. It is configured in Salesforce, not in Zapier. |
| A field changing | Updated Field on Record, with old and new values | Field History Tracking gives you both values. Useful, and it is also the trigger whose test data ignores your selected object. |
| A newly created custom field or object | The Zap editor dropdown, eventually | Zapier documents delays before new Salesforce fields and objects appear. |
Three 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: five field mappings and three 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.
That last row is the one that wastes an afternoon: a Zap built and tested against supplied or mismatched test data looks correct and does something else entirely on the first real record.
Both sides gate this and they gate different things. Zapier decides whether the integration exists at all and how fast it polls; Salesforce decides whether your edition has the API to be polled. Pick one on each side and the grid marks the answer.
Pick one on each side.
| Zapier plan | Essentials | Professional | Enterprise or above |
|---|---|---|---|
| Free or Starter | Premium app, not included | Premium app, not included | Premium app, not included |
| Professional | The vendors disagree | Two-minute polling | Two-minute polling |
| Team or Enterprise | The vendors disagree | One-minute polling and static IP | One-minute polling and static IP |
Counted off that grid, of nine pairings: three give you premium app, not included, two give you the vendors disagree, two give you two-minute polling, two give you one-minute polling and static IP. Neither column buys you an instant trigger: the only instant path is a Salesforce outbound message, which is configured on the Salesforce side and is free.
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.
Salesforce: connected apps, third-party access
Salesforce allows five access tokens per account across every third-party application, and when a sixth is generated the oldest is revoked automatically and without notification. Zapier is about to take one. Knowing which five you already have is the difference between a clean install and silently logging out another integration.
Salesforce Setup: My Domain
Zapier requires My Domain configured and states that custom domains are not supported. This is org-level work with its own change window in most companies.
Salesforce Setup
Connected apps can no longer be created in Setup, so if your organisation requires a custom app a Salesforce administrator follows Zapier's administrator prerequisites to create one. In a locked-down org this is the step that takes a fortnight.
Salesforce: profile and field-level security
Zapier is explicit that user, object and field permissions can prevent triggers and actions from working. The Zap does not fail loudly; the trigger simply never sees the record.
Zapier: Apps, Add connection
Salesforce is a premium app on Zapier, so there is no free path at all. Authenticate, grant access, and pick sandbox only if your account actually has one.
Zapier: Professional, Team or Enterprise
Zapier offers a static IP on those plans, which is what makes this work against an org that enforces IP allowlisting. On a Free or Starter Zapier plan that option does not exist and neither does the integration.
The Zap editor
Every Salesforce trigger Zapier lists polls, except New Outbound Message, which is instant. If you need immediacy, the path is a Salesforce outbound message rather than a faster Zapier plan.
Five of those seven happen in Salesforce, which is the honest shape of this pair: Zapier is the easy half and the org is the project.
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/salesforce-zapier/SKILL.md https://www.reversecontact.com/integrations-hub/skills/salesforce-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.
WhyZapier names this one precisely: you have exceeded the connected app access limit. Salesforce allows five access tokens per account across all third-party apps and revokes the oldest without notification.
Audit third-party connected apps in Salesforce and remove what is unused. Adding another tool will revoke another token, so this returns until somebody prunes.
WhySandbox was selected and the account does not support a sandbox environment. Zapier quotes this exact message for that case.
Connect to production instead. The credentials are not the problem.
WhyUser, object or field permissions on the connecting user. Zapier documents these as able to prevent triggers and actions from working.
Check field-level security as well as object permissions, and test as the connecting user rather than as an admin.
WhyZapier documents a delay before newly created Salesforce fields and objects appear in its dropdowns.
Refresh the fields from the trigger step, and wait before rebuilding anything.
WhyTest data. If the org has no live data Zapier supplies its own, and the Updated Field on Record trigger returns the most recently updated record without filtering on the object you chose.
Test against a real record of the right object before turning the Zap on.
WhyThe Salesforce integration does not support Marketing Cloud accounts.
There is no setting. Marketing Cloud needs its own route entirely.
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 this pair by name, in the words a person would use. 14 threads from 2023 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.
Zapier is a godsend for a lot of smaller organizations who have modest resources and needs. If you are transferring 10,000 rows a month from one system to another, it is amazing. If you are a big firm that moves around millions of r
r/salesforce·August 2024·18 points
The cleanest framing in the set, and it maps onto the API limits above: Salesforce meters concurrent requests in a 20-second window and total requests in 24 hours, so a Zap moving millions of rows is competing with every other integration in the org for the same allocation.
LOTS of people use Zapier and yes LOTS with Salesforce. No it is not a cheap service and been around for many years. It is solid. I am a Salesforce consultant, ISV and customer and I have used for years.
r/salesforce·August 2024·38 points
The most upvoted answer to an admin asking whether to approve it. Worth noting the one caveat embedded in it, which is cost rather than reliability, and which is real: Salesforce is a premium app and the Zapier plan is part of the integration budget.
I have been tasked at looking at Zapier and feasibility from the Salesforce side
r/salesforce·August 2024·26 points
If that is your task, the five-token limit is the thing to put in the memo. It is the one Salesforce-side consequence of approving Zapier that affects integrations nobody mentioned in the meeting.
This is one of those speak now or forever hold your piece kind of things and I do not have a ton of time to really research it
r/salesforce·August 2024·7 points
Quoted because it is the most common condition under which this decision gets made. The short version for that memo: safe, metered, premium-tier on Zapier, and it costs you one of five Salesforce connected-app tokens.
I was playing around with the OpenAI/Salesforce integration on Zapier the other day and was blown away by the ease to set it up
r/salesforce·February 2023·95 points
The highest-scoring Salesforce and Zapier thread in the set is not about moving records between systems. It is about putting something Salesforce does not have in front of a record, which is the honest case for an orchestrator over a native connector.
The thread that matters is an admin being asked to approve Zapier and asking the subreddit whether it is safe. The answers are strikingly consistent from consultants, ISVs and customers: it is solid, widely used, and the right tool below a certain volume. Nobody defends it at scale, and nobody attacks it below that, which is a more useful verdict than either side alone.
Taken together the threads argue for approving it with one condition attached, and the condition is the token count rather than anything about reliability.
This is the clearest case in the directory of an integration whose real price is on the side nobody checks. The Salesforce licence is already bought and the AppExchange has thousands of listings, so a team reaches for Zapier expecting the cheap option and finds a premium app that rules out the free plan entirely. That is not unreasonable of Zapier, given what a Salesforce connection costs to maintain, but it does change the comparison: against a paid Zapier plan, a flow with an API callout or an n8n instance you host yourself are genuinely competitive, and both are described on the Reverse Contact guide for exactly this reason.
The five token limit deserves more attention than it gets, because it is the only limit here that damages something other than the thing you are building. Every third-party tool authenticating against your org holds a token, Salesforce keeps five, and new ones push out old ones silently. In a mature org that is a real constraint rather than a theoretical one, and it argues for counting your authenticated integrations before adding another and for consolidating several small automations behind one connection rather than spreading them across tools.
What you get for the trouble is the breadth that makes Zapier worth having: leads, contacts, accounts, opportunities and custom objects, in both directions, wired to applications that will never publish a managed package. Keep the expectations calibrated on two points. Testing is less informative than it looks, because the Updated Field on Record trigger's test records do not filter by the object you chose, so build against a real record early. And new custom fields take time to appear in Zapier's dropdowns, which is a cache rather than a failure and is fixed by reloading the list rather than by rebuilding the Zap.
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 Salesforce, 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.
No. Salesforce is a premium app on Zapier, so it needs a paid Zapier plan: Professional, Team or Enterprise. Zapier's free plan does not include it at all, which makes this one of the few pairs in the directory where the glue is the paywall rather than the endpoint. Budget the Zapier plan as part of the integration rather than as a tool somebody already has.
One with API access, and the two vendors do not read identically on this. Zapier's help page lists Sales and Service editions including Essentials, Professional, Enterprise, Unlimited and Performance. Salesforce's own allocation table grants API calls to Enterprise, to Professional with API access enabled, to Unlimited and Performance, and to Developer Edition, and other vendors integrating over the same REST API document Essentials as having no API access even with an add-on. Confirm API access on your own org before you trust the supported-editions list.
My Domain has to be set up, and custom domains are not supported. Zapier then has to be approved as an External Client App in your org, and if your organisation requires a custom app a Salesforce administrator creates one for Zapier, because connected apps can no longer be created in Setup. The connecting user needs the appropriate user, object and field permissions. Professional, Team and Enterprise Zapier plans can also use a static IP where your org enforces IP allowlisting.
Most often because you ran out of access tokens. Salesforce allows five access tokens per account across all third-party apps, and when new ones are generated the older ones are revoked automatically. So the sixth tool somebody connects quietly logs out the first, and the error Zapier shows is a generic message about the connection no longer working. Count the integrations authenticating against your org before you add another.
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.