Skip to content
CRM ⇄ Business productivity

Close to Zendesk integration — real-time, two-way sync

Keep Close and Zendesk in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.

  • SOC 2 and 6 other compliance frameworks
  • POC with real engineers in minutes

Adopted by fast-scaling companies moving mission-critical data in real time

Case study
Migrated from Mulesoft
Case study
Migrated from Celigo
Migrated from Heroku Connect
Migrated from Matillion
Case study
Migrated from Fivetran
Case study
Migrated from Celigo
Why teams connect Close and Zendesk

Sync what happens in Zendesk with the customer records in Close, in real time and in both directions.

The CRM is supposed to be the record of every customer relationship, but customer-relevant information also accumulates in the other tools a team runs. Whatever Zendesk holds or produces that touches a customer, whether conversations, payments, replies, enriched data, or notes, the CRM only benefits if it arrives without someone copying it over.

Stacksync connects Tickets, Tickets Comments, Users, Organizations in Zendesk to Tasks, Custom Activities, Custom Fields, Users in Close with bi-directional, real-time sync. Activity and record changes in Zendesk update the matching contact or account in Close, and CRM data flows the other way wherever Zendesk can store and use it.

Common use cases

  • Sync tickets, users, and organizations into Postgres so support analytics run on SQL instead of repeated API pulls.
  • Write CRM account tier, owner, and renewal data onto Zendesk organizations and ticket fields so agents see context in the ticket.
  • Sync Close leads and opportunities into Postgres or a warehouse for pipeline reporting outside Close's built-in reports.
  • Two-way sync between Close and a billing or ERP system so closed-won opportunities create customers and invoices automatically.

Where Zendesk handles support or shared inboxes

Tickets and conversations attach to the right contact and account in Close, so sales sees open issues before the next call.

Where Zendesk supplies contact or company data

Enriched fields land directly on records in Close, and refreshes keep them from going stale.

Where Zendesk can store CRM context: fields kept current

Owner, lifecycle stage, or account details from Close sync into Zendesk, so people working there have the context without switching tools.

What you can sync between Close and Zendesk

Representative objects on each side — any object or custom field can map to any target. Schemas are auto-detected; types are converted between the two systems.

Close objects Zendesk objects
Users Sales reps referenced as owners on leads, opportunities, and activities. Ticket Forms Synced with incremental and full sync per the Stacksync docs.
Smart Views Saved lead searches that can scope which records a segment-based sync pulls. Tickets The central work object; synced to databases for SLA and volume reporting or mirrored into engineering tools.
Leads The top-level record in Close; represents a company and holds its contacts, opportunities, and activity history. Tickets Comments Synced with incremental and full sync per the Stacksync docs.
Contacts People nested under a lead, with emails and phone numbers used for outreach syncs. Users End users and agents; matched to CRM contacts to keep requester data consistent.
Opportunities Deal records with value, confidence, and status; commonly synced to reporting and billing systems. Organizations Company groupings for users; typically kept aligned with CRM accounts.
Activities Calls, emails, SMS, notes, and meetings logged against a lead; the source for engagement analytics. Attachments Synced with incremental and full sync per the Stacksync docs.
What ships with Close ⇄ Zendesk

Connect Close and Zendesk for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Close–Zendesk connection.

Real-time

Two-way sync

Changes in Close or Zendesk instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Close or Zendesk data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.

At scale

Event queues

Handle millions of events per minute without losing a single Close or Zendesk record.

Observability

Monitoring

Track your Close ⇄ Zendesk sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Close and Zendesk.

How the Close and Zendesk connectors work

Close

Integration surface
REST API
Authentication
API key (sent via HTTP Basic auth)
Change detection
Webhook subscriptions for record events, with polling on date_updated fields for backfills
Capabilities
read · write · webhooks
Rate limits
Subject to per-endpoint rate limits communicated in response headers

Zendesk

Integration surface
REST API
Authentication
OAuth app authorization: enter your Zendesk subdomain (from {sub_domain_name}.zendesk.com) in Stacksync Connections and click "Authorize App"
Change detection
Incremental export endpoints with cursor-based pagination, plus webhooks fired by triggers
Capabilities
read · write · webhooks
Rate limits
Request limits vary by plan; incremental export endpoints have their own allowances.
Zendesk setup guide
How it works

How to connect Close to Zendesk — three steps, no code

Configure and sync within minutes, no code. Whether you sync 50k or 100M+ records, Stacksync handles the queues, infra, and plumbing. Integrations are non-invasive and need zero setup on your systems.

  1. 01

    Connect your apps

    Authenticate Close and Zendesk with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.

    • OAuth 2.0
    • SSH tunnel
    • VPC peering
    Close connected
    Zendesk connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Close and Zendesk objects to sync — Stacksync auto-detects both schemas, including custom fields where the platform exposes them. Sync to existing tables, or let Stacksync create new ones with ideal data types.

    • Standard objects
    • Custom objects
    • Auto-schema
    objects · Close ⇄ Zendesk
    Customers 12,480
    Sales Orders 8,213
    Invoices 5,902
    Items 1,344
  3. 03

    Map fields

    Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.

    • Auto-map
    • Type casting
    • Transforms
    Close Zendesk
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
FAQ

Close and Zendesk integration FAQ

SECURITY

Security teams love Stacksync

As a data company, we understand the importance of keeping your data secure. Stacksync is built with security best practices to keep your data safe at every layer, and is DPF-certified for US, EU, UK and CH data transfers.

SOC 2 type II
ISO 27001
HIPAA BAA
GDPR
CCPA
CSA STAR
DPF US-EU-UK-CH
→ SECURITY WITH BENEFITS

SSO & SCIM

Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.

Alerts

Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.

Secure connection options

Securely connects to your systems with:

Related integrations

Every pair below is a real-time, two-way sync. Search all 386 integrations available for Close and Zendesk.

Popular · 8 of 386
Coworkers laughing in front of a laptop in a casual office setting

Your last integration took months.
Your next one takes a prompt.