Skip to content
Data warehouse ⇄ Business productivity

Apache Druid to Zendesk integration — real-time, two-way sync

Keep Apache Druid 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 Apache Druid and Zendesk

Get the data locked inside Zendesk into Apache Druid as live tables, and send results back where Zendesk can use them, without writing a pipeline.

Whatever Zendesk is used for, it accumulates data the rest of the company wants to analyze, and that data usually sits behind an API rather than in the warehouse. Building and babysitting an extraction pipeline is the tax most teams pay for it.

Stacksync syncs Tickets Comments, Users, Organizations, Attachments from Zendesk into tables in Apache Druid continuously, handling schema, rate limits, and retries. Because the sync is bi-directional, results computed in Apache Druid can also be written back into fields in Zendesk where the tool can use them.

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.
  • Query aggregated event metrics from Druid and sync them into CRM account fields for usage-based selling.
  • Feed operational records into Druid via batch ingestion so analysts get interactive slice-and-dice on fresh data.

Where Zendesk accepts updates: operational write-back

Segments, scores, or reference values computed in Apache Druid sync back onto records in Zendesk, putting analysis where the work happens.

History that outlives the tool

A continuously synced copy in Apache Druid preserves a queryable record even as data ages out of Zendesk or gets changed inside it.

Analytics on Zendesk's data

Records and events from Zendesk land in Apache Druid as queryable tables, current within seconds and ready to join with the rest of the warehouse.

What you can sync between Apache Druid 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.

Apache Druid objects Zendesk objects
Ingestion Supervisors Long-running specs that pull from streams like Kafka; the write path into Druid. Attachments Synced with incremental and full sync per the Stacksync docs.
Lookups Key-value mappings joined at query time, refreshable from external systems. Ticket Forms Synced with incremental and full sync per the Stacksync docs.
Tasks Batch ingestion and compaction jobs monitored during data loads. Tickets The central work object; synced to databases for SLA and volume reporting or mirrored into engineering tools.
Datasources The table-like unit of storage and querying, the main target of reads and ingestion. Tickets Comments Synced with incremental and full sync per the Stacksync docs.
Segments Time-partitioned immutable files that hold datasource data; ingestion produces them. Users End users and agents; matched to CRM contacts to keep requester data consistent.
Dimensions String and categorical columns used for filtering and grouping in synced queries. Organizations Company groupings for users; typically kept aligned with CRM accounts.
What ships with Apache Druid ⇄ Zendesk

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Apache Druid 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 Apache Druid or Zendesk record.

Observability

Monitoring

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

Trading partners

EDI

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

How the Apache Druid and Zendesk connectors work

Apache Druid

Integration surface
REST API (SQL over HTTP and native JSON queries); JDBC via Avatica
Authentication
Deployment-dependent: basic authentication or an authenticator extension; often fronted by a proxy
Change detection
Not applicable for reads out (polling by time interval); data enters Druid through streaming or batch ingestion rather than row updates
Capabilities
read · write
Rate limits
No fixed API quotas; query concurrency is bounded by broker and historical node capacity

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 Apache Druid 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 Apache Druid 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
    Apache Druid connected
    Zendesk connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Apache Druid 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 · Apache Druid ⇄ 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
    Apache Druid Zendesk
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
FAQ

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