Two-way sync
Changes in Apache Druid or Insightly instantly reflect in both systems. No stale data, no manual imports.
Keep Apache Druid and Insightly 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. Contacts, Organizations, Leads, Opportunities from Insightly land in Apache Druid as live tables, updated within seconds, and columns computed in Apache Druid write back to fields in Insightly. There is no separate ETL and reverse-ETL stack to stitch together and no jobs to babysit.
Deduplication and normalization done in Apache Druid can be written back, so warehouse-side cleanup actually fixes the CRM.
Accounts, contacts, and activity from Insightly are queryable in Apache Druid moments after they change, so dashboards stop lagging the reality they describe.
Lead scores, churn risk, or usage segments computed in Apache Druid appear as fields in Insightly, where the people working accounts actually see them.
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 | Insightly objects | How this pairing syncs | |
|---|---|---|---|
| Tasks Batch ingestion and compaction jobs monitored during data loads. | Tasks Activity records keep follow-ups consistent across systems. | Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions. | |
| Metrics Numeric columns, often pre-aggregated at ingestion via rollup. | Projects Delivery records created from won opportunities sync with PSA and task tools. | Metrics is specific to Apache Druid and Projects to Insightly — 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. | Events Calendar items sync for a complete activity timeline. | Ingestion Supervisors is specific to Apache Druid and Events to Insightly — each maps to any object or custom field on the other side. | |
| Lookups Key-value mappings joined at query time, refreshable from external systems. | Notes Free-text context attaches to synced records for downstream visibility. | Lookups is specific to Apache Druid and Notes to Insightly — each maps to any object or custom field on the other side. | |
| Datasources The table-like unit of storage and querying, the main target of reads and ingestion. | Products Product catalog entries support line-item syncing on opportunities and quotes. | Datasources is specific to Apache Druid and Products to Insightly — each maps to any object or custom field on the other side. | |
| Segments Time-partitioned immutable files that hold datasource data; ingestion produces them. | Custom Fields Per-object custom fields carry enrichment and billing data written from external systems. | Segments is specific to Apache Druid and Custom Fields to Insightly — each maps to any object or custom field on the other side. |
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.
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 Insightly through its API, with automatic retries and rate-limit backoff.
DetectionStacksync polls Insightly for changes on an incremental schedule, reading only records changed since the previous pass. Polling on record updated-date fields.
DeliveryEach detected change is applied to Apache Druid as a row-level write, with types converted between the two schemas.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Apache Druid–Insightly connection.
Changes in Apache Druid or Insightly instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Apache Druid or Insightly data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single Apache Druid or Insightly record.
Track your Apache Druid ⇄ Insightly sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Apache Druid and Insightly.
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 Apache Druid and Insightly 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 Apache Druid and Insightly 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 Apache Druid and Insightly: authenticate both systems, choose the objects to sync (such as Apache Druid's Tasks and Metrics), map fields visually, and changes propagate both ways in milliseconds — no code required.
Insightly: Most core objects support custom fields, which is the standard place to land externally sourced data during syncs. Apache Druid: Rollup can pre-aggregate events at ingestion time, meaning the stored granularity may differ from the raw event stream. Stacksync's field mapping accounts for these differences between Apache Druid and Insightly without custom code.
Stacksync is SOC 2 Type II and ISO 27001 certified with HIPAA BAA support. Data is encrypted in transit, and a zero-persistent-storage architecture means Apache Druid and Insightly records are not retained after a sync operation.
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Apache Druid and Insightly connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Apache Druid–Insightly integration in-house.
Yes — Stacksync ships production-grade connectors for both Apache Druid and Insightly. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
Change detection on Apache Druid: Not applicable for reads out (polling by time interval); data enters Druid through streaming or batch ingestion rather than row updates. On Insightly: Polling on record updated-date fields. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
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 450 integrations available for Apache Druid and Insightly.