Zendesk Salesforce Integration: Options, Setup and Limits (2026 Guide)

What a Zendesk Salesforce integration should do

The split is common: the support team answers tickets in Zendesk, the sales and account teams live in Salesforce. Without a link, agents don’t know a customer is mid-renewal, and account managers walk into a QBR without knowing about three open escalations.

A useful integration does four jobs:

• Context for agents. On a ticket, the agent sees the customer’s account, owner, plan or open opportunity from Salesforce.
• Context for sales. On an account, contact or opportunity, the rep sees open and recent tickets.
• One customer list. Accounts and contacts created in Salesforce appear in Zendesk as organizations and users, so tickets attach to the right company.
• Reporting. Ticket data lands in Salesforce, so you can report on support load per account, segment or renewal date.

It is not a full mirror of both systems. Every field you sync is a field that can conflict, leak or break. Start with what someone will actually look at.

What Zendesk’s official Salesforce integration includes

Zendesk builds and maintains the integration itself. You connect your Salesforce org in Zendesk Admin Center (Apps and integrations, then Integrations, then Salesforce) and switch on the parts you need. According to Zendesk’s help center, as of October 2026 there are four:

Requirements

• Zendesk plan: Suite Team, Growth, Professional, Enterprise or Enterprise Plus, or Support Team, Professional or Enterprise.
• Salesforce edition: Performance, Unlimited, Enterprise or Developer, or another edition with API rights, such as Professional with the API add-on.
• People: the person who connects must be an admin in both Zendesk and Salesforce. An API-only Salesforce user can’t be used, and if the connecting admin is later downgraded, the integration stops until another admin reconnects it.
• Salesforce settings: session settings must not lock sessions to an IP address. Data sync also needs the API and the Streaming API enabled, with read access to Streaming Channels and PushTopics. The ticket view Lightning component needs My Domain.

What it doesn’t do

Most frustration with the official integration comes from expecting a two-way sync. Zendesk’s documentation is clear about the limits:

• No two-way record sync. Changes to a Zendesk user or organization don’t go back to Salesforce. Edits to a synced case don’t go back to the ticket.
• No case-to-ticket flow. A case created in Salesforce doesn’t become a Zendesk ticket.
• Ticket sync gaps. Attachments don’t sync, closed tickets don’t sync, and comments aren’t written to a case field (you read them through ticket view). Several field types can’t be mapped, including multi-select fields.
• Limited objects. Data sync covers accounts, contacts and leads in near real time. Opportunities and other Salesforce objects can be shown live in the sidebar app. Since September 2026, Zendesk Suite Growth and higher can also schedule a one-way sync of Salesforce objects into Zendesk custom objects, which runs a full sync once a day (or on demand), so it suits reference data rather than fast-changing records.
• One org. Data sync and ticket sync connect one Salesforce org to one Zendesk account. Several orgs are supported only for the sidebar app and ticket view.
• No undo. Zendesk warns that data synced from Salesforce into Zendesk can’t be reversed, so test in a sandbox first.

Your options compared

Four routes, from cheapest to biggest change:

Connector apps for this pair are listed on the Zendesk Marketplace and on AppExchange (now AgentExchange). Check each listing for supported plans and objects before you trial one.

Which option fits you?

Five questions. The result points to the route most teams in your situation pick.

How the data flows

The design that holds up: Salesforce is the system of record for customers (accounts, contacts, leads, opportunities). Zendesk is the system of record for tickets. Each side gets a read-only copy or a live view of the other’s data.

Object and field mapping: what goes where

Start with this minimum set. Add a field only when someone can name the decision they will make with it.

Two rules save most of the pain. First, keep Zendesk tickets on their own case record type and out of any Service Cloud processes, so assignment rules, escalations and case emails never fire on synced tickets. Second, decide the matching key up front. Account names drift (“Acme Inc.” vs “Acme, Inc”), so a unique account field or external ID is safer than the default name match.

How to set it up, step by step

This is the order that avoids rework with Zendesk’s official integration. Zendesk’s help center has the exact screens; menu labels change, so follow it for the clicks.

1. Write down who needs whatWhich Salesforce fields agents need on a ticket, which ticket data reps need on an account, and which reports need tickets in Salesforce. This becomes your mapping, and it often shows you don’t need ticket sync at all.
2. Prepare sandboxesA Salesforce sandbox and a Zendesk sandbox. Zendesk lets you choose Production or Sandbox when you add the connection. Data sync can’t be undone, so never test it against production first.
3. Pick the connecting adminThe connection runs as the Salesforce admin who sets it up, and synced cases are owned by that user. An API-only user is not allowed, so use a dedicated admin account the team controls rather than a person’s own login, and check your Salesforce session settings aren’t locked to an IP address.
4. Connect the orgIn Zendesk Admin Center, open Apps and integrations, then Integrations, then Salesforce, add a connection and sign in to Salesforce with the admin account.
5. Turn on the sidebar appChoose the Salesforce objects and keep to about five fields per object (Zendesk warns that more can slow lookups or time out), and set the matching fields between the ticket and the Salesforce record.
6. Install ticket viewInstall the managed package for all users, turn on ticket view, set the matching criteria, allow the profiles that may see tickets (System Administrator must be included), and add the component to Account, Contact, Lead and Opportunity pages.
7. Configure data syncEnable the Streaming API permissions, then set up Accounts to Organizations and Contacts or Leads to Users: filters (up to three ALL and three ANY conditions), one matching criterion, and field mappings. Map Name to Name for organizations.
8. Configure ticket sync, if you need itCreate a case record type for Zendesk tickets (optional in Zendesk’s setup, but it keeps synced tickets apart), install the ticket sync package, enter the record type ID, and map fields. Every required case field and every drop-down value must have a match. Zendesk then creates a webhook and a trigger; don’t rename or delete them.
9. Test real scenariosNew account and contact, a contact matching an existing Zendesk user, duplicate account names, a renamed account, a ticket with a new drop-down value, a closed ticket, a ticket with an attachment. Check what landed and what failed.
10. Pilot, then switch on productionRun one team for a week or two, fix the mapping, then repeat the configuration on production and brief both teams on what they will and won’t see.

Built by Gilzor

Results we’ve shipped

70+products launched

98%delivered on time

85%clients come back

Aviation33%faster baggage weigh-inWeb and Mobile application for Airlines→Healthcare+30%lab test ordersMedical Lab Web and Native Mobile Applications→Retail · Startup700+stores aggregatedMobile application for Grocery shops→

Talk to the people who build it. Tell us about your project and get a free estimate of scope, timeline and cost.

See how we’d approach yours →

Pitfalls and how to fix them

When to go beyond the official integration

A connector app or iPaaS makes sense when you need two-way ticket and case sync with comments, for example because a Salesforce team (customer success, field service or an internal escalation desk) works cases that started as Zendesk tickets. Dedicated sync tools such as Exalate or Unito sell that pattern; general platforms such as Workato, MuleSoft or Zapier fit one-way triggers like “create a Zendesk ticket when an opportunity closes with an onboarding product.” If you run MuleSoft already, our Salesforce MuleSoft integration guide covers that route.

Custom work starts to pay off when:

• You run several Salesforce orgs or Zendesk accounts and need routing between them.
• Data must be filtered, enriched or approved on the way, with rules you can audit.
• You need custom objects (subscriptions, assets, entitlements) synced into Zendesk in real time or with business rules; Zendesk’s own scheduled custom object sync runs only daily.
• Per-user or per-record connector pricing grows faster than a one-time build.

A typical custom build is a small middleware service: Zendesk webhooks and the Zendesk REST API on one side, Salesforce Platform Events or Change Data Capture and the REST API on the other, and a link table of ticket and case IDs. It needs idempotency so retries don’t create duplicates, a queue for rate limits, and alerts. Zendesk’s Support API limits depend on the plan: as of October 2026, from 200 requests a minute on Team to 700 on Enterprise, and 2,500 with the High Volume API add-on or on Suite Enterprise Plus. On the Salesforce side, use a dedicated integration user; Salesforce includes a limited number of Salesforce Integration user licenses in supported editions.

These figures come from our API integration cost guide, which explains what moves a project to the low or high end. For the wider picture, see the Salesforce integration guide.

When teams move support to Service Cloud instead

Some teams conclude the integration is the wrong problem. Moving support into Salesforce Service Cloud removes the sync, at the cost of a real migration. It tends to make sense when:

• Support processes depend on Salesforce data every day: contracts, entitlements, assets, renewals.
• You already run other Salesforce clouds and want one customer timeline and one reporting layer.
• The integration has grown into custom code, several connectors and a part-time owner.

It rarely pays off when support is happy in Zendesk and only needs context. The migration covers ticket history, macros, triggers, routing, help center content and agent training, so price it against a better integration first. If engineering escalations are part of the picture, our Jira Salesforce integration guide covers that link, and teams comparing service desks can read the ServiceNow Salesforce integration guide.

Go-live checklist

Tick what is already true. It shows how ready your integration is for real customers.

FAQ

Where Gilzor fits

Gilzor builds and maintains Salesforce integrations from Poland and Cyprus. Our engineers can map the data flow with your support and sales leads, configure Zendesk’s integration or a connector, or build a custom integration on the Zendesk and Salesforce APIs, and support it after launch. See our Salesforce integration services for how that work is scoped.