How to Integrate Zendesk with Salesforce (Step by Step)

This guide walks through the official, Zendesk-built integration end to end: connecting the two systems over OAuth, configuring data sync, setting up ticket sync, and turning on the two "ticket view" surfaces (Salesforce data inside Zendesk, and Zendesk tickets inside Salesforce). Every step is verified against Zendesk's own documentation; Zendesk and Salesforce both revise their UI periodically, so confirm labels in your own accounts. A note on honesty up front: the Zendesk-side steps below are first-hand, but the Salesforce-side screens (the managed package, record types, ticket view) are described from the docs rather than screenshotted — Salesforce orgs differ enough that you should treat those as a map, not a pixel-perfect match.

What the integration actually does

It helps to know the shape of the thing before you start clicking. The native integration isn't one feature — it's four related pieces, and you turn on only the ones you need:

• Data sync (Salesforce → Zendesk). Salesforce accounts become Zendesk organizations, and Salesforce contacts/leads become Zendesk users, kept in step automatically. This is what gives agents account context inside the ticket.
• Ticket sync (Zendesk → Salesforce). Zendesk tickets flow into Salesforce as cases, so sales and ops can report on support activity alongside CRM data.
• The Salesforce app for Zendesk Support. A sidebar panel that shows Salesforce records (accounts, opportunities, contacts) inside the Zendesk ticket.
• Ticket view in Salesforce. A managed package that lets Salesforce users view, create, and edit Zendesk tickets from Account, Opportunity, Contact, and Lead pages.

Crucially, each sync direction is one-way. Data flows Salesforce → Zendesk; tickets flow Zendesk → Salesforce. There's no native two-way merge of the same object, which matters when you decide your system of record. (For the bigger "should these even be two products?" question, see our comparison of Zendesk vs. Salesforce Service Cloud.)

Before you start: plan, editions, and permissions

This is where most setups stall, so check it first.

Zendesk plan. Contrary to a common assumption that this is an Enterprise-only feature, the integration is broadly available. Per Zendesk's docs it works on Zendesk Suite Team, Growth, Professional, Enterprise, and Enterprise Plus, and on Support Team, Professional, and Enterprise — effectively every current paid tier, not just the top one. If you've been told you must upgrade to Enterprise purely to connect Salesforce, that's worth re-checking against your account; verify your own plan, because Zendesk does occasionally re-gate features.

Salesforce edition. Your Salesforce org needs API access. That means Performance, Unlimited, Enterprise, or Developer Edition, or another edition with API rights (for example Professional with the API add-on). Group/Essentials-tier orgs without API access generally can't run the native integration.

Permissions and account settings:

• You must be both a Zendesk Support administrator and a Salesforce administrator to set it up.
• You can't use an API-only Salesforce user to authenticate the connection.
• In Salesforce Session Settings, the option "Lock sessions to the IP address from which they originated" must be deselected — otherwise the integration disconnects whenever a session expires.
• The PKCE setting in Salesforce's OAuth and OpenID Connect settings must be disabled before you connect, and kept disabled afterward.
• For ticket sync to create case fields, the authenticating Salesforce user needs permission to modify the Salesforce Metadata API.

Sort these out before you touch the connect button and the rest goes smoothly. Skip them and you'll hit an opaque OAuth error halfway through.

Step 1 — Find the integration in Admin Center

Everything on the Zendesk side starts in the same place. In Admin Center, click Apps and integrations in the sidebar, then go to Integrations → Integrations, and click Salesforce. This is the management hub for the connection — the same area where all your Zendesk apps and integrations live.

To be straight about what you're looking at: the screenshot above is the Zendesk Apps and integrations → My Apps page, which is where installed Zendesk apps and integrations are managed. The Salesforce data sync and ticket sync configuration screens live deeper inside the Salesforce integration's own settings (the Data sync and Support app tabs), and the ticket view managed package and record-type screens live over in Salesforce — those are described from Zendesk's documentation below rather than shown here.

Step 2 — Connect and authenticate to Salesforce (OAuth)

With the prerequisites met, the connection itself is quick:

1. On the Salesforce integration page, click Add connection.
2. Choose your Salesforce instance type — Production or Sandbox. (Always rehearse in a sandbox first if you have one.)
3. Accept the Built by Zendesk Terms of Use.
4. Click Connect Salesforce. You'll be redirected to a standard Salesforce OAuth login.
5. Sign in with your Salesforce admin credentials and approve access.
6. You're returned to Admin Center, and the new connection appears in your list.
7. Click the options (⋯) menu next to the connection and choose Configure to start turning on the individual features.

Because a Salesforce admin has to authorize this, loop them in early if you don't hold both roles yourself. The OAuth token is tied to that user, which is why the API-only-user and IP-lock rules above matter — get them wrong and the token silently dies.

Step 3 — Configure data sync (Salesforce → Zendesk)

This is the piece that gives agents CRM context. Data sync is one-way, Salesforce → Zendesk, and Salesforce is treated as the source of truth for mapped fields.

What syncs:

• Salesforce accounts → Zendesk organizations
• Salesforce contacts and leads → Zendesk users

To set it up, open the Data sync tab of the Salesforce integration and configure each object pair:

1. Enable the relevant Salesforce API and streaming permissions (data sync relies on Salesforce's streaming API to catch changes).
2. Configure Accounts → Organizations: set the field mapping (the defaults map Account Name → Organization Name), add sync filters, and pick a matching criterion.
3. Configure Contacts/Leads → Users the same way (default Email → Email).
4. Save.

Three things to get right in the mapping:

• Sync filters decide which records qualify, using AND/OR conditions — but you're limited to three conditions per category, a Salesforce constraint, so keep filters tight. A common pattern is syncing only accounts of a certain type or region rather than the whole CRM.
• Matching criteria decide whether a sync creates a new record or updates an existing one by comparing a field (e.g. email). Only one matching criterion per sync type is supported, so choose a genuinely unique field.
• Field-type limits: some Salesforce field types can't be mapped, including long text areas and lookup fields. Also note a quirk — for Tags, Email, and Phone, Salesforce values are appended on sync rather than overwriting.

The payoff: once an account syncs, an agent opening any ticket from that customer sees the matching Zendesk organization populated with Salesforce-sourced details — no alt-tabbing into the CRM.

Step 4 — Set up ticket sync (Zendesk → Salesforce)

Ticket sync runs the other direction: Zendesk tickets → Salesforce cases, also one-way. It's how sales and operations report on support volume inside Salesforce. This is the most involved piece because part of it happens in Salesforce.

The sequence:

1. Confirm the connection from Step 2 is live.
2. In Salesforce, create a Case Record Type dedicated to synced tickets — Zendesk recommends naming it something like "Zendesk Ticket Sync" so synced cases stay separate from your other case processes.
3. Find the Record Type ID. In Salesforce, go to Setup → Object Manager → Case → Record Types, open the record type, and copy the ID from the URL.
4. Install the ticket sync package from the Salesforce integration in Admin Center. On install, Zendesk creates and maps most standard ticket fields to their Salesforce case equivalents automatically.
5. Enter the Record Type ID in the ticket sync configuration and finish the field mappings.
6. Set up and activate triggers in Zendesk Support so tickets actually fire across on create/update.

Watch-outs that trip people up:

• The package can only create case fields if the authenticated user has Metadata API modify permission (see prerequisites).
• Closed tickets don't sync — only open/active tickets transfer, so don't expect historical closed tickets to backfill.
• Don't map multi-select fields — it causes sync errors. Unsupported Zendesk field types for mapping also include multi-line text, credit card, regex, and lookup relationship fields.
• All required Salesforce case fields must be mapped, or the sync fails outright.

This is exactly why the docs (and we) push you to test in a Salesforce sandbox before pointing it at production. A bad record-type or a required-field gap fails quietly until you go looking.

Step 5 — Show Salesforce data inside Zendesk (the Support app)

Data sync populates organizations and users, but the Salesforce app for Zendesk Support goes further: it shows live Salesforce objects and fields in a sidebar panel on the open ticket, so an agent sees the account, contact, or opportunity record right there.

To enable it:

1. In the Salesforce integration, open the Support app tab.
2. Turn the app on for agents.
3. Configure what appears — choose which Salesforce objects to show, match fields between systems, filter results, and set a data refresh rate (default 60 minutes).

Agents then click the Apps button on a ticket to reveal the panel. Handy detail for larger orgs: the app supports connecting multiple Salesforce organizations to one Zendesk instance, so agents covering different business units can each see the right CRM data.

This is the highest-leverage piece for support teams day-to-day — it turns every ticket into an account-aware conversation without anyone learning Salesforce.

Step 6 — Turn on ticket view in Salesforce

The mirror image of Step 5: ticket view in Salesforce lets your sales team view, create, and edit Zendesk tickets from inside Salesforce. (These are the Salesforce-side steps described from Zendesk's docs — your exact Salesforce screens will vary.)

1. In Zendesk's Salesforce connection page, click the options (⋯) menu next to the org and choose Install managed package. This adds a Lightning component and a Visualforce component to Salesforce; Zendesk recommends "Install for All Users."
2. Back in the integration settings, select "Turn on Zendesk ticket view for Salesforce."
3. In the Map fields section, set the matching criteria that decide which tickets show on a given record.
4. Add the ticket view component to your Account, Opportunity, Contact, and Lead page layouts in Salesforce.

Once live, a Salesforce user can view, create, and edit Zendesk tickets — and add internal and public comments — directly from those CRM pages. One per-user requirement: to create or update tickets from Salesforce, each Salesforce user must authenticate with their Zendesk agent credentials in the ticket view personal settings (otherwise they can read but not write).

Step 7 — Test, then watch the limits

Before you announce it internally, run a full loop in a sandbox or with test records:

1. Create/update a Salesforce account that matches your filters and confirm the Zendesk organization appears or updates.
2. Open a Zendesk ticket for a synced customer and confirm the Salesforce app sidebar shows the right record.
3. Create a Zendesk ticket and confirm a Salesforce case is created under the correct record type.
4. From a Salesforce Contact/Account, view and create a Zendesk ticket via ticket view, then confirm it lands in Zendesk.

Keep these honest limitations in mind as you scale:

• Both syncs are one-way. Decide your source of truth deliberately — Salesforce owns account/contact data; Zendesk owns the ticket.
• Sync isn't instant for everything — the Support app refresh defaults to 60 minutes, and filter/matching limits cap how granular you can get.
• Field-type restrictions (long text, lookup, multi-select) mean some data simply won't map; plan around it.
• Closed tickets don't sync into Salesforce.
• If your Salesforce session settings re-lock to IP or PKCE gets re-enabled, the connection breaks — note that for anyone who manages Salesforce security.

Where AI fits in

Connecting Zendesk and Salesforce solves a context problem for humans: the agent can finally see the account, and the rep can finally see the tickets. That's real value. But notice the ceiling — all that connected context still sits there waiting for a person to read it and act. The integration surfaces the renewal date and the open opportunity; it doesn't answer the customer's account-specific question.

That last mile is where an AI agent like Macha fits. Macha isn't a help desk and it isn't a Zendesk or Salesforce replacement — it runs on top of your existing Zendesk, and it can use exactly this connected context to resolve account-specific questions automatically. When a customer asks "when does my plan renew?" or "why was I charged twice?", an AI agent with access to the synced CRM and ticket data can read the relevant records and answer inside the ticket — drafting the reply, tagging, and routing — instead of leaving it for a human to look up. When it isn't confident, it escalates to an agent with the full context attached. (For the underlying ticket model it works against, see our explainer on the Zendesk ticketing system.)

The honest framing: it's one more integration to configure, and it's only as good as the data you connect to it — a half-synced CRM gives a half-informed agent, human or AI. On cost, Macha bills per AI action (any automated step it takes — drafting, tagging, routing, resolving), not per closed ticket, because most automation is work done along the way rather than a tidy "resolution." If you want to see it work against your connected Zendesk, you can try it free — 7-day free trial, no credit card required. The deeper product details live on Macha for Zendesk.

Frequently asked questions

Is the Zendesk Salesforce integration free, and what plan do I need? The integration is built by Zendesk and included with the supported plans rather than sold separately. It's available on Zendesk Suite Team, Growth, Professional, Enterprise, and Enterprise Plus, and on Support Team, Professional, and Enterprise — so it's not Enterprise-only, despite a common assumption. On the Salesforce side you need an edition with API access (Performance, Unlimited, Enterprise, Developer, or Professional with the API add-on). Always confirm current gating in your own accounts.

Does the integration sync data both ways? Each piece is one-way. Data sync runs Salesforce → Zendesk (accounts → organizations, contacts/leads → users). Ticket sync runs Zendesk → Salesforce (tickets → cases). There's no native two-way merge of the same object, so choose a clear system of record for each data type.

How do I connect Zendesk to Salesforce? In Zendesk Admin Center → Apps and integrations → Integrations → Integrations → Salesforce, click Add connection, choose Production or Sandbox, accept the terms, click Connect Salesforce, and sign in with your Salesforce admin credentials. You must be both a Zendesk admin and a Salesforce admin, and you can't use an API-only Salesforce user.

Why does ticket sync need a Salesforce record type and ID? Ticket sync creates Salesforce cases from Zendesk tickets. A dedicated Case Record Type (e.g. "Zendesk Ticket Sync") keeps synced tickets separate from your other case processes, and you enter its Record Type ID (from Setup → Object Manager → Case → Record Types) so Zendesk knows where to file them.

Can Salesforce users create Zendesk tickets without opening Zendesk? Yes — with ticket view in Salesforce (installed via the managed package), Salesforce users can view, create, and edit Zendesk tickets and add comments from Account, Opportunity, Contact, and Lead pages. Each user must authenticate with their Zendesk agent credentials to create or update tickets.

Why does my Salesforce connection keep dropping? The two usual culprits are Salesforce session settings locked to an IP address and the PKCE setting being enabled in Salesforce's OAuth configuration. Both must stay off for the integration to keep its OAuth token alive.

The bottom line

Integrating Zendesk with Salesforce is a clear, four-part sequence: connect the two over OAuth in Admin Center → Apps and integrations → Integrations → Salesforce; turn on data sync so Salesforce accounts and contacts populate Zendesk organizations and users; set up ticket sync so Zendesk tickets become Salesforce cases (mind the record type, the metadata permission, and the unsupported field types); and enable the two view surfaces — the Salesforce app inside Zendesk for agents and ticket view in Salesforce for sales. Get the prerequisites right first (plan, Salesforce edition, admin roles, IP-lock and PKCE off), rehearse in a sandbox, and remember every sync is one-way. The result is what most teams actually wanted: support and sales finally looking at the same customer. And once that context is connected, it's the natural foundation for an AI agent to act on it — not just show it.

Setup steps verified against Zendesk's official Salesforce integration documentation, June 2026. Salesforce-side screens are described from Zendesk's docs; confirm exact labels in your own Zendesk and Salesforce accounts before relying on them.