Two-way sync
Changes in Apache Druid or Campfire instantly reflect in both systems. No stale data, no manual imports.
Keep Apache Druid and Campfire in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.
Whatever Campfire 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 Chart of Accounts, Chart Transaction, Fixed Asset, Fixed Asset Class from Campfire 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 Campfire where the tool can use them.
Segments, scores, or reference values computed in Apache Druid sync back onto records in Campfire, putting analysis where the work happens.
A continuously synced copy in Apache Druid preserves a queryable record even as data ages out of Campfire or gets changed inside it.
Records and events from Campfire land in Apache Druid as queryable tables, current within seconds and ready to join with the rest of the warehouse.
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 | Campfire objects | |
|---|---|---|
| Tasks Batch ingestion and compaction jobs monitored during data loads. | Bill Synced with incremental and full sync per the Stacksync docs. | |
| Datasources The table-like unit of storage and querying, the main target of reads and ingestion. | Debit Memo Synced with incremental and full sync per the Stacksync docs. | |
| Segments Time-partitioned immutable files that hold datasource data; ingestion produces them. | Invoice Synced with incremental and full sync per the Stacksync docs. | |
| Dimensions String and categorical columns used for filtering and grouping in synced queries. | Credit Memo Synced with incremental and full sync per the Stacksync docs. | |
| Metrics Numeric columns, often pre-aggregated at ingestion via rollup. | Bank Account Synced with incremental and full sync per the Stacksync docs. | |
| Ingestion Supervisors Long-running specs that pull from streams like Kafka; the write path into Druid. | Bank Transaction Synced with incremental and full sync per the Stacksync docs. |
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Apache Druid–Campfire connection.
Changes in Apache Druid or Campfire instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Apache Druid or Campfire 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 Campfire record.
Track your Apache Druid ⇄ Campfire sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Apache Druid and Campfire.
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 Campfire 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 Campfire 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 Campfire: authenticate both systems, choose the objects to sync (such as Apache Druid's Tasks and Datasources), map fields visually, and changes propagate both ways in milliseconds — no code required.
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 Apache Druid and Campfire: Where Campfire accepts updates: operational write-back; History that outlives the tool; Analytics on Campfire's data. Segments, scores, or reference values computed in Apache Druid sync back onto records in Campfire, putting analysis where the work happens.
Apache Druid: 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. Campfire: HTTP endpoints for bot integrations on a self-hosted instance. Authentication: API key — create an API user with a Super User Role in Campfire (Settings -> API Keys), generate an API Key secret, and provide it in the Stacksync connection setup. Stacksync manages authentication, retries, and rate limits on both sides.
Campfire: The current Campfire is distributed by 37signals as self-hosted, open-source software, so the available integration surface depends on the deployed instance and its version. Apache Druid: Streaming ingestion from Kafka or Kinesis is managed by supervisors designed to provide exactly-once ingestion semantics. Stacksync's field mapping accounts for these differences between Apache Druid and Campfire 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 Campfire records are not retained after a sync operation.
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 Apache Druid and Campfire.