Skip to content
Data warehouse ⇄ Communications

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

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

Land the messages, calls, and events from Zoom in Apache Druid as live tables, and write results back, without building or maintaining a pipeline.

Zoom produces a constant stream of activity — messages sent and received, calls placed and answered, meetings held, and the delivery and engagement events attached to them. That record is what the rest of the company wants to analyze, and it usually sits behind an API rather than in the warehouse. Building and babysitting an extraction pipeline is the tax most teams pay to get it out.

Stacksync syncs Meetings, Webinars, Registrants, Cloud Recordings from Zoom into tables in Apache Druid in real time, handling schema, rate limits, and retries. Because the connection works in both directions, results computed in Apache Druid — segments, contact updates, suppression flags — can be written back into fields in Zoom wherever it exposes them, so analysis lands where outreach actually happens.

Common use cases

  • 01 Write Meetings and webinar Registrants from a CRM or event platform into Zoom, then read Participant Reports back onto the lead or contact record.
  • 02 Land Cloud Recording metadata and past-meeting Participant Reports into a warehouse for compliance archival and usage analytics.
  • 03 Query aggregated event metrics from Druid and sync them into CRM account fields for usage-based selling.
  • 04 Feed operational records into Druid via batch ingestion so analysts get interactive slice-and-dice on fresh data.

Common sync patterns

Where Zoom accepts updates: operational write-back

Segments, contact fields, or suppression flags computed in Apache Druid sync back onto records in Zoom, putting warehouse analysis where the outreach happens.

Queryable history that outlives retention

A continuously synced copy in Apache Druid preserves messages, call logs, and events for reporting and audit even as they age out of Zoom or get purged inside it.

Communications analytics without ETL

Messages, calls, and events from Zoom arrive in Apache Druid as queryable tables, current within seconds instead of a day behind.

What you can sync between Apache Druid and Zoom

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 Zoom objects How this pairing syncs
Segments Time-partitioned immutable files that hold datasource data; ingestion produces them. Webinars Webinar events (requires the Webinar license); created and managed via API, with panelists and settings written from event tools. Segments is specific to Apache Druid and Webinars to Zoom — each maps to any object or custom field on the other side.
Dimensions String and categorical columns used for filtering and grouping in synced queries. Registrants Meeting and webinar registrant records; added, listed, and status-updated so signups flow between event platforms and Zoom. Dimensions is specific to Apache Druid and Registrants to Zoom — each maps to any object or custom field on the other side.
Metrics Numeric columns, often pre-aggregated at ingestion via rollup. Cloud Recordings Recording file metadata and time-limited download URLs; read out to a warehouse or storage for archival and compliance. Metrics is specific to Apache Druid and Cloud Recordings to Zoom — each maps to any object or custom field on the other side.
Ingestion Supervisors Long-running specs that pull from streams like Kafka; the write path into Druid. Participant Reports Past-meeting and webinar attendance from the Reports and Dashboard APIs; read-only, used to write attendance onto CRM records. Ingestion Supervisors is specific to Apache Druid and Participant Reports to Zoom — each maps to any object or custom field on the other side.
Lookups Key-value mappings joined at query time, refreshable from external systems. Zoom Phone Call Logs Call detail records and recordings from Zoom Phone (requires the Phone license); read into a database to log calls against customers. Lookups is specific to Apache Druid and Zoom Phone Call Logs to Zoom — each maps to any object or custom field on the other side.
Tasks Batch ingestion and compaction jobs monitored during data loads. Team Chat Channels and Messages Chat channels, membership, and messages; listed and sent two-way to align collaboration spaces with team data. Tasks is specific to Apache Druid and Team Chat Channels and Messages to Zoom — each maps to any object or custom field on the other side.

How changes propagate between Apache Druid and Zoom

Each direction of the sync is driven by what the source system can signal and what the destination accepts — detection, delivery, and expected latency below.

Apache Druid Zoom Interval-based propagation

DetectionStacksync polls Apache Druid for changes on an incremental schedule, reading only records changed since the previous pass. Data enters Druid through streaming or batch ingestion rather than row updates.

DeliveryEach detected change is written to Zoom through its API, with automatic retries and rate-limit backoff.

Zoom Apache Druid Sub-second propagation

DetectionZoom notifies Stacksync of record changes through webhook events. Webhooks via Event Subscriptions (meeting.started/ended, participant joined/left, user.created/updated, recording.completed, and more) for real-time.

DeliveryEach detected change is applied to Apache Druid as a row-level write, with types converted between the two schemas.

Rate-limit considerations

  • Apache Druid: No fixed API quotas; query concurrency is bounded by broker and historical node capacity.
  • Zoom: APIs are grouped into Light, Medium, Heavy, and Resource-intensive categories with per-second and daily quotas that scale by plan (e.g. Business+ Heavy APIs allow 40/second within a 60,000/day combined cap); exceeding a limit returns HTTP 429.
What ships with Apache Druid ⇄ Zoom

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

Track your Apache Druid ⇄ Zoom 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 Zoom.

How the Apache Druid and Zoom 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

Zoom

Integration surface
REST API (v2) with webhook Event Subscriptions
Authentication
OAuth 2.0 — user-authorized OAuth or Server-to-Server OAuth using account credentials; access tokens are valid for one hour and requests use granular per-resource scopes (e.g. meeting:read, user:write)
Change detection
Webhooks via Event Subscriptions (meeting.started/ended, participant joined/left, user.created/updated, recording.completed, and more) for real-time events, with polling on list endpoints using date-range filters for backfill and objects without an event
Capabilities
read · write · webhooks
Rate limits
APIs are grouped into Light, Medium, Heavy, and Resource-intensive categories with per-second and daily quotas that scale by plan (e.g. Business+ Heavy APIs allow 40/second within a 60,000/day combined cap); exceeding a limit returns HTTP 429.
How it works

How to connect Apache Druid to Zoom — 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 Zoom 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
    Zoom connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Apache Druid and Zoom 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 ⇄ Zoom
    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 Zoom
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

Apache Druid and Zoom integration FAQ

SECURITY

Security teams trust 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.

Learn more about security
SOC 2 Type II
ISO 27001
HIPAA BAA
GDPR
CCPA
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:

OAuth 2 SSH Tunnelling SSL certificates IP Whitelisting VPN gateway VPC peering and more

Related integrations

Every pair below is a real-time, two-way sync. Search all 344 integrations available for Apache Druid and Zoom.

Popular · 7 of 344
All Apache Druid integrations All Zoom integrations Browse all integrations
Coworkers laughing in front of a laptop in a casual office setting

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

Book a demo Tour the platform on your own