Skip to content
Data warehouse ⇄ Marketing

Apache Kylin to Iterable integration — real-time data sync

Keep Apache Kylin and Iterable 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 Kylin and Iterable

Flow Apache Kylin data into Iterable in real time — no exports, no schedulers, no custom scripts.

Apache Kylin is a read-only source: Stacksync reads its data in real time and delivers it into Iterable, so Iterable always reflects the current state of Apache Kylin — without exports, scripts, or schedulers.

Apache Kylin is where your team models customers, product usage, and revenue into trusted tables; Iterable runs the campaigns, audiences, and messages that reach those people. The two overlap wherever the same person, account, or segment matters to both, and when the bridge between them is a nightly export or a hand-built list, marketing targets stale data while analytics never sees what the campaign returned.

Common use cases

  • 01 Read pre-aggregated metrics from Kylin and sync them into CRM fields or planning spreadsheets on a schedule.
  • 02 Expose Kylin query results to operational dashboards without granting access to the underlying Hadoop data.
  • 03 Two-way sync User profiles and their custom data fields between Iterable and a Postgres database or CRM so attributes and subscription state stay aligned in both systems.
  • 04 Push warehouse or CRM audience segments into Iterable as Users via bulkUpdate (up to 1000 per call) and subscribe them to static Lists to drive campaigns.

Common sync patterns

Keep the contact and audience list current

New and updated contacts, leads, or audience members flow between Apache Kylin and Iterable, so the marketing audience reflects the people in your warehouse and corrections propagate instead of the two sides drifting apart.

Suppression and consent stay aligned

Unsubscribes, bounces, and consent or opt-out flags held in either system propagate to the other, so no one is messaged after opting out and Apache Kylin holds the current state for auditing.

Enrich records with warehouse context

Product-usage counts, plan tier, region, or account owner computed in Apache Kylin appear on the matching record in Iterable, so targeting, routing, and personalization use up-to-date context.

What you can sync between Apache Kylin and Iterable

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 Kylin objects Iterable objects How this pairing syncs
Segments Time-ranged build units that partition pre-computed data. Campaigns Email, SMS, push, and in-app sends; metadata and metrics read via GET /api/campaigns and /api/campaigns/metrics, created and sent via /api/campaigns/create and /api/campaigns/trigger. Segments is specific to Apache Kylin and Campaigns to Iterable — each maps to any object or custom field on the other side.
Build Jobs Batch jobs that compute or refresh segments, monitored via the REST API. Templates Reusable email/SMS/push/in-app message templates with handlebars fields; read via /api/templates and per-channel get endpoints, written via /api/templates/email/upsert and the other channel upserts. Build Jobs is specific to Apache Kylin and Templates to Iterable — each maps to any object or custom field on the other side.
Projects Top-level workspaces that group models, tables, and jobs. Lists Static subscriber lists; read via GET /api/lists and /api/lists/getUsers, with users added or removed via /api/lists/subscribe and /api/lists/unsubscribe to control who receives a send. Projects is specific to Apache Kylin and Lists to Iterable — each maps to any object or custom field on the other side.
Models Star-schema definitions over source tables that determine what can be queried. Catalogs Named catalogs of items (products, content) used for personalization and recommendations; items upserted and read via /api/catalogs/{catalogName}/items. Models is specific to Apache Kylin and Catalogs to Iterable — each maps to any object or custom field on the other side.
Cubes / Indexes Pre-computed aggregate structures that answer queries at low latency. Commerce / Purchases Purchase and cart activity tracked via /api/commerce/trackPurchase and /api/commerce/updateCart, feeding revenue attribution and abandoned-cart journeys. Cubes / Indexes is specific to Apache Kylin and Commerce / Purchases to Iterable — each maps to any object or custom field on the other side.
Source Tables Hive or other upstream tables that builds read from. Export data Historical user and event records pulled through the Export API (/api/export/data.json, data.csv, and userEvents) across data types like emailSend, emailOpen, emailClick, emailBounce, purchase, and customEvent. Source Tables is specific to Apache Kylin and Export data to Iterable — each maps to any object or custom field on the other side.

How changes propagate between Apache Kylin and Iterable

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 Kylin Iterable Interval-based propagation

DetectionStacksync polls Apache Kylin for changes on an incremental schedule, reading only records changed since the previous pass. Data freshness follows segment build and refresh jobs, so integrations poll query results.

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

Iterable Apache Kylin Sub-second propagation

DetectionIterable notifies Stacksync of record changes through webhook events. System Webhooks push email/SMS/push/in-app and custom events (send, open, click, bounce, complaint, unsubscribe) as JSON POSTs in near real time.

DeliveryApache Kylin does not accept inbound record writes, so this direction carries requests rather than records: Apache Kylin's output flows back as field updates on the originating Iterable records.

Rate-limit considerations

  • Apache Kylin: No fixed API quotas; query capacity depends on the deployment and pre-computed index coverage.
  • Iterable: Limits are per endpoint and per project/key; exceeding one returns HTTP 429, so exponential backoff is advised. Event tracking allows far higher volume than metadata endpoints like campaigns/templates, and the Export API is throttled more tightly. Since Nov 10, 2025, passing the key in the query string or body is rate-limited more strictly than the Api-Key header.
What ships with Apache Kylin ⇄ Iterable

Connect Apache Kylin and Iterable for flexible, real-time data sync.

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

Real-time

Real-time sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Apache Kylin and Iterable.

How the Apache Kylin and Iterable connectors work

Apache Kylin

Integration surface
SQL over JDBC/ODBC plus a REST API for queries and administration
Authentication
Username/password (HTTP basic authentication on the REST API)
Change detection
Not applicable for row-level capture; data freshness follows segment build and refresh jobs, so integrations poll query results
Capabilities
read
Rate limits
No fixed API quotas; query capacity depends on the deployment and pre-computed index coverage

Iterable

Integration surface
Iterable REST API (JSON over HTTPS): Users, Events, Campaigns, Templates, Lists, Catalogs, and Commerce endpoints, plus a bulk Export API for historical data
Authentication
API key sent in the Api-Key HTTP header (also accepted as Api_Key; the name is case-insensitive). Keys are scoped by type - Server-side, JavaScript (Web SDK), or Mobile - with optional JWT-enabled keys. US projects use api.iterable.com; EU projects use api.eu.iterable.com.
Change detection
System Webhooks push email/SMS/push/in-app and custom events (send, open, click, bounce, complaint, unsubscribe) as JSON POSTs in near real time; historical backfill and incremental catch-up run through the Export API over a date range.
Capabilities
read · write · webhooks
Rate limits
Limits are per endpoint and per project/key; exceeding one returns HTTP 429, so exponential backoff is advised. Event tracking allows far higher volume than metadata endpoints like campaigns/templates, and the Export API is throttled more tightly. Since Nov 10, 2025, passing the key in the query string or body is rate-limited more strictly than the Api-Key header.
How it works

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

    Choose tables

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

Apache Kylin and Iterable 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 352 integrations available for Apache Kylin and Iterable.

Popular · 8 of 352
All Apache Kylin integrations All Iterable 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