---
name: salesforce-zapier-integration
description: Connect Salesforce and Zapier: what syncs, which editions carry it, the setup order, and the failures to expect. Covers contacts, companies, deals, custom objects. Use when the user wants to set up, audit or troubleshoot Salesforce and Zapier together, or asks why data is not moving between them.
---

# Salesforce and Zapier

> Generated from https://www.reversecontact.com/integrations-hub/salesforce-integrations/salesforce-zapier-integration
> Every tier requirement, sync direction and limit below was read from the vendors' own documentation on 2026-10-11.
> Vendors change these without notice. Re-check anything load-bearing before you rely on it.

**What you have to buy first:** A paid Zapier plan, a Salesforce edition with API access, and an admin to approve the app

**What moves:** contacts, companies, deals, custom objects, both ways.
**How it is built:** zapier, make or n8n, marketplace app. **Effort:** minutes.

## The short version

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.

## Which plans carry what, and how fast

Rows: Zapier plan. Columns: Salesforce edition. 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.

| 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 |

- **Premium app, not included.** Salesforce is a premium app on Zapier, so no free or Starter plan reaches it whatever your Salesforce edition.
- **The vendors disagree.** Zapier lists Essentials among the supported Sales and Service editions. Salesforce's own allocation table and other vendors integrating over the same REST API say Essentials has no API access even with an add-on. Confirm on your own org before trusting either list.
- **Two-minute polling.** The integration, polling every two minutes. Enough for most CRM automation and not enough for anything a human is waiting on.
- **One-minute polling and static IP.** Polling every minute, plus the static IP that makes this work against an org enforcing IP allowlisting.

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.

## What actually syncs

Direction is written from Salesforce's point of view: out means out of Salesforce, in means into it.

| What | Direction | What that means in practice |
|---|---|---|
| Leads, contacts and accounts | Two-way sync | Create, update, find and find-or-create in either direction, subject to the connecting user's object and field permissions. |
| Opportunities | Two-way sync | Created and updated from outside, and usable as a trigger when a field changes. |
| Custom objects and fields | Two-way sync | 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 | Events only | Not supported. Marketing Cloud accounts cannot be connected on this integration at all. |

## Which field lands where

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. |

**What does not cross:**

- Marketing Cloud. Zapier states the Salesforce integration does not support those accounts at all.
- Anything at all on a free Zapier plan. Salesforce is a premium app.
- Reliable test records. If the org has no live data Zapier supplies test data, and the Updated Field on Record trigger returns the most recently updated record regardless of the object you chose.

## Connect it, in this order

**Who has to do it:** A Salesforce administrator for the org-level work, and whoever owns the Zapier account. The two are rarely the same person and the Salesforce half comes first.
**How long:** Minutes once the org is ready. The org being ready is the project.

### 1. Count the connected apps before you add another

*Where:* 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.

### 2. Configure My Domain, and check it is not a custom domain

*Where:* 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.

### 3. Get Zapier approved as an External Client App

*Where:* 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.

### 4. Check the connecting user has the permissions the Zaps will need

*Where:* 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.

### 5. Add the connection on a paid Zapier plan

*Where:* 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.

### 6. Use a static IP if your org restricts by address

*Where:* 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.

### 7. Pick your trigger knowing only one of them is instant

*Where:* 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.

## How to check it worked

- Create a record and time the trigger. Two minutes on Zapier Professional and one on Team or Enterprise is expected, not slow.
- Have a non-admin run the Zap. Field-level security on the connecting user is the usual reason a trigger sees nothing.
- Add a custom field in Salesforce and look for it in the Zap editor. It may not appear immediately, and that is documented rather than broken.
- Count your Salesforce connected apps again afterwards, so the next person adding one knows the number.

## When it goes wrong

Each row is a symptom somebody reports, the documented reason, and the fix. Work down it before escalating to either vendor, because most of these are configuration.

| Symptom | Why it happens | What to do |
|---|---|---|
| This connection to Salesforce appears to no longer be working | Zapier 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. |
| Please check your username and password, on a connection that is correct | Sandbox 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. |
| A trigger never fires for certain records | User, 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. |
| A new custom field is missing from the Zap editor | Zapier 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. |
| The Zap worked in testing and misbehaves live | Test 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. |
| Marketing Cloud will not connect | The Salesforce integration does not support Marketing Cloud accounts. | There is no setting. Marketing Cloud needs its own route entirely. |

## What breaks, from the vendors' own docs

- **Five access tokens across every third-party app.** Salesforce permits five access tokens per account across all third-party apps, and generating new ones revokes the older ones automatically. In an org that already has a sequencer, a conversation tool, an enrichment vendor and a reporting tool authenticated, adding Zapier can log one of them out. Nothing warns you, and the symptom on the victim is a connection that reports it is no longer working.
- **The two vendors disagree on Essentials.** Zapier lists Essentials among the supported Sales and Service editions. Salesforce's own allocation table grants API calls to Professional with API access enabled, Enterprise, Unlimited, Performance and Developer Edition, and Outreach documents Essential as having no REST API access even with an add-on. Treat API access as the real requirement and verify it on your org, because the supported-editions list is not the thing that decides whether a call succeeds.
- **Admin work before any Zap.** My Domain must be configured and custom domains are not supported. Zapier has to be approved as an External Client App, and because connected apps can no longer be created in Setup, an org that requires a custom app needs an administrator to create one. None of this is difficult and all of it sits in somebody else's queue, which is why a ten minute Zap can take two weeks to go live.
- **Latency is your Zapier plan.** Polling runs every 2 minutes on Professional and every minute on Team and Enterprise, and a Zap can never poll faster than the greater of its plan minimum and the app minimum. Salesforce's own allocation is the other half of the arithmetic: 100,000 calls plus 1,000 per Salesforce licence per 24 hours on Enterprise, shared across every integration in the org, with no limit on concurrent requests shorter than 20 seconds and 25 concurrent long-running ones in production.

## The APIs, if you are building around it instead

### Salesforce

- **Base:** `https://{instance}.my.salesforce.com/services/data/v60.0`
- **Auth:** OAuth 2.0 through a connected app. **API access is an edition feature**: editions without it cannot run any of this.

| Call | Request | What it does |
|---|---|---|
| `PATCH /sobjects/Contact/{id}` | `{ "RC_Title__c": "VP Sales" }` | Update a record. Custom fields carry the __c suffix. |
| `POST /composite/sobjects` | `{ "allOrNone": false, "records": [...] }` | Batch up to 200. `allOrNone: false` so one bad row does not roll back the batch. |
| `GET /query?q=SELECT+Id,Email+FROM+Contact+WHERE+Title=null` | - | SOQL for the filtered slice. |

**Rules that will cost you time if you skip them:**

- **Validation rules, required fields, duplicate rules and Apex triggers all apply to your writes.** A completed run is not a successful write. Read the per-record errors.
- **The daily API allocation is shared across the whole org**, set by edition and licence count. A row-by-row job competes with every other integration; the symptom of exhausting it is other people's integrations failing.
- Test in a sandbox with ten records before production. The rules you will hit were written years ago by somebody who has left.
- Installing anything usually needs Modify Metadata, Download AppExchange Packages and Customize Application. That is an admin on their own schedule.

Docs: https://developer.salesforce.com/docs/apis

## Filling the record this integration moves

The integration above moves a record between two systems. Neither of them creates what is in it, so a sync that works perfectly still carries whatever gaps the record arrived with. Reverse Contact resolves an email, a domain or a profile URL into a verified people and company record through one API, and returns null with a confidence score rather than a guess.

### Reverse Contact

- **Base:** `https://api.reversecontact.com/v2`
- **Auth:** `Authorization: Bearer rc_your_api_key`. Keys are created in Workspace > API Keys.

| Call | Request | What it does |
|---|---|---|
| `POST /v2/enrich/persons` | `{ "email": "j.okafor@northwind.io" }` | Resolve a person from an email, a name plus company, or a profile URL. Cached resolution, returns in the response. |
| `POST /v2/enrich/companies` | `{ "domain": "northwind.io" }` | Resolve a company from a domain or a name. |
| `POST /v2/fetch/persons` | `{ "linkedInUrl": "..." }` | Standard profile lookup from the database. |
| `POST /v2/fetch/persons/live` | `{ "linkedInUrl": "..." }` | Live on-demand resolution. ASYNCHRONOUS: returns a webhookId to poll, not a record. |
| `POST /v2/search/people` | `{ "filters": { "currentCompanyDomain": "northwind.io" } }` | Filtered people search. 1 credit a profile delivered, and /v2/search/people/count is free. It replaced /v2/search/persons, which returns 410 Gone since 13 October 2026. |
| `POST /v2/search/organizations` | `{ "filters": { "companyDomain": "northwind.io" } }` | Filtered company search. A domain can also go straight to a company through POST /v2/enrich/companies, or through the enrich_company MCP tool since November 2026. |
| `POST /v2/contact/email` | `{ "linkedInUrl": "..." }` | Find an email. ASYNCHRONOUS: returns a taskId to poll. 3 credits for a professional address, 5 for a personal one, 8 for both, refunded when neither is found. |
| `GET /v2/webhooks/:webhookId` | - | Poll an async job until status is "succeeded". Polling is free and does not count against the rate limit. |

Response shape:

```json
{
  "success": true,
  "data": {
    "person": {
      "fullName": "Jane Okafor",
      "headline": "VP Sales at Northwind",
      "location": "London, United Kingdom",
      "linkedInUrl": "https://linkedin.com/in/...",
      "currentPosition": { "title": "VP Sales", "companyName": "Northwind", "startDate": "2023-04" },
      "emails": [], "experience": [], "education": [], "skills": []
    },
    "company": { "name": "Northwind", "domain": "northwind.io",
                 "industry": "Software Development", "employeeCount": 220 }
  },
  "error": null,
  "metadata": { "requestId": "req_...", "executionTimeMs": 480, "updatedAt": "2026-09-01T..." },
  "quotas": { "creditsConsumed": 1, "workspace": { "credits": { "total": 10000, "used": 4521, "left": 5479 } } }
}
```

**Rules that will cost you time if you skip them:**

- A miss returns **null**, not a best guess. Every response carries a confidence score, and you can raise the precision threshold on the request. Branch on it: do not treat a low-confidence answer as a match.
- Use the cached endpoints anywhere that must answer inside one HTTP request. The `/live` endpoints return a task and need polling.
- `quotas.workspace.credits.left` is on every response. Log it, or you will find out about the balance from a 402.
- Credit costs per call are published and a dollar rate per lookup is not: 2 credits for a reverse lookup from an email, 1 for a cached profile lookup, 2 for a live refresh, 3 for a business email and 20 for a direct phone number, with the last two charged only when one is found. Checks and the search count endpoint are free. Credit packs expire after 3 months. Do not hard-code a dollar cost assumption.

**MCP server:** `https://api.reversecontact.com/mcp`

- Auth: OAuth 2.1 where the client supports it, otherwise `Authorization: Bearer rc_your_api_key`.
- Tools: `enrich_person`, `enrich_person_live`, `enrich_company`, `enrich_company_live`, `search_persons`, `search_companies`, `check_usage`, `check_task`
- Streamable HTTP, JSON-RPC 2.0. The `_live` tools return a task id that `check_task` polls.

Docs: https://docs.reversecontact.com/getting-started

## Sources

- Zapier: how to get started with Salesforce on Zapier: https://help.zapier.com/hc/en-us/articles/8496020790925-How-to-get-started-with-Salesforce-on-Zapier
- Zapier: control when your Zap runs: https://help.zapier.com/hc/en-us/articles/8495924437005-Control-when-your-Zap-runs
- Salesforce developer limits and allocations quick reference (PDF): https://resources.docs.salesforce.com/latest/latest/en-us/sfdc/pdf/salesforce_app_limits_cheatsheet.pdf
- 14 practitioner threads read on 2026-10-11, summarised on the page: https://www.reversecontact.com/integrations-hub/salesforce-integrations/salesforce-zapier-integration#reddit
- This pair, with the reasoning behind each step: https://www.reversecontact.com/integrations-hub/salesforce-integrations/salesforce-zapier-integration

---

*Published by Reverse Contact, which appears in this directory as a data provider.
No other vendor pays for placement. Where a vendor publishes no public figure, this file says so
rather than estimating. Reverse Contact costs are stated in credits, which it publishes; no dollar
rate per lookup appears here, because none is published and dividing a pack price is not their number.*
