Two-way sync
Changes in ClickHouse or Gladly instantly reflect in both systems. No stale data, no manual imports.
Keep ClickHouse and Gladly in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.
The CRM feeds the warehouse and the warehouse should feed the CRM: relationship data flows one way, and computed scores, segments, and customer context flow back. Most teams build the first half as a batch pipeline and never quite get to the second.
Stacksync does both with one connection. Tasks, Customer profiles, Conversations, Conversation items from Gladly land in ClickHouse as live tables, updated within seconds, and columns computed in ClickHouse write back to fields in Gladly. There is no separate ETL and reverse-ETL stack to stitch together and no jobs to babysit.
Lead scores, churn risk, or usage segments computed in ClickHouse appear as fields in Gladly, where the people working accounts actually see them.
Join Gladly's relationship data with billing, product, and support data in ClickHouse to build the customer picture the CRM alone cannot hold.
Deduplication and normalization done in ClickHouse can be written back, so warehouse-side cleanup actually fixes the CRM.
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.
| ClickHouse objects | Gladly objects | |
|---|---|---|
| Views Saved queries used as curated, read-only sync sources. | Topics Categorization applied to conversations; the key dimension for contact-driver reporting. | |
| Materialized views Insert-time transformations that reshape incoming synced rows into aggregates. | Tasks Follow-up work items created from external triggers or synced for workload reporting. | |
| Distributed tables Query-routing tables over cluster shards in self-managed deployments. | Customer profiles The central entity; merges identifiers like email, phone, and order IDs, which syncs use for matching. | |
| Dictionaries In-memory lookup structures refreshed from external sources, sometimes fed by syncs. | Conversations Each customer's continuous timeline; status and outcomes sync to CRMs and warehouses. | |
| Tables (MergeTree family) Columnar, append-optimized tables that serve as the destination for high-volume sync loads. | Conversation items Individual messages across voice, SMS, chat, and email attached to the conversation. | |
| Databases Namespaces that group tables and scope permissions for sync users. | Agents User records used to attribute work in CX analytics. |
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every ClickHouse–Gladly connection.
Changes in ClickHouse or Gladly instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever ClickHouse or Gladly data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single ClickHouse or Gladly record.
Track your ClickHouse ⇄ Gladly sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between ClickHouse and Gladly.
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.
Authenticate ClickHouse and Gladly with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Pick the ClickHouse and Gladly 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.
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Yes. Stacksync provides a managed, real-time two-way integration between ClickHouse and Gladly: authenticate both systems, choose the objects to sync (such as ClickHouse's Views and Materialized views), map fields visually, and changes propagate both ways in milliseconds — no code required.
Change detection on ClickHouse: No log-based CDC for consumers; incremental reads use polling on monotonic columns, and ClickHouse is usually the destination rather than the source. On Gladly: Webhook event subscriptions for conversation and customer events, supplemented by polling and report exports. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
On the Gladly side: Tasks, Customer profiles, Conversations, Conversation items, plus custom fields where Gladly exposes them. On the ClickHouse side: Dictionaries, Tables (MergeTree family), Databases, Views. Stacksync auto-detects both schemas and converts types between the two systems.
Yes. Each object mapping can be bidirectional or restricted to a single direction (both systems accept writes). Read-only mirrors, one-way pushes, and full two-way sync can be mixed in the same integration.
Common patterns for ClickHouse and Gladly: Scores and segments back on the record; A single customer view; Cleanup that sticks. Lead scores, churn risk, or usage segments computed in ClickHouse appear as fields in Gladly, where the people working accounts actually see them.
ClickHouse: Native TCP protocol and HTTP interface; standard SQL dialect, with MySQL and PostgreSQL wire compatibility available. Authentication: Database credentials (username/password); ClickHouse Cloud issues per-service credentials over TLS. Gladly: REST API. Authentication: API tokens used with basic authentication tied to an agent email. Stacksync manages authentication, retries, and rate limits on both sides.
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.
Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.
Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.
Securely connects to your systems with:
Every pair below is a real-time, two-way sync. Search all 386 integrations available for ClickHouse and Gladly.