Two-way sync
Changes in ClickHouse or Smartrecruiters instantly reflect in both systems. No stale data, no manual imports.
Keep ClickHouse and Smartrecruiters in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.
Workforce data is some of the most requested data in the warehouse and some of the most awkward to move: the record types are many, the fields carry sensitive personal information, the APIs are strict, and hand-built extract jobs go stale or break quietly. Whether Smartrecruiters is the system of record for employees and payroll, for candidates and applications, or for learners and course completions, the reporting belongs in ClickHouse next to everything else the company measures.
Stacksync syncs Offers, Users, Approvals, Candidates from Smartrecruiters into tables in ClickHouse continuously, handling API limits and schema drift as they come. The connection is bi-directional, so values computed in ClickHouse, such as headcount rollups, cost allocations, or attrition risk flags, can be written back to fields in Smartrecruiters where the HR team acts on them. You configure which records and fields cross over, and in which direction, instead of maintaining pipeline code.
Analysts combine Smartrecruiters's workforce records with finance, product, or operational data already in ClickHouse for reporting the HR system cannot produce on its own.
Because changes stream continuously, reports query current workforce data rather than waiting for an overnight load window to finish.
A continuously synced copy in ClickHouse gives you a durable, queryable record of how Smartrecruiters's records change over time, for headcount planning and audit questions.
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 | Smartrecruiters objects | How this pairing syncs | |
|---|---|---|---|
| Databases Namespaces that group tables and scope permissions for sync users. | Offers Offer records tied to an Application with status, custom offer fields, and offer documents; readable and writable, commonly synced to an HRIS on hire (documents endpoint limited to 2 requests/sec). | Databases is specific to ClickHouse and Offers to Smartrecruiters — each maps to any object or custom field on the other side. | |
| Views Saved queries used as curated, read-only sync sources. | Users Company users (recruiters, hiring managers) with roles, access groups, and activation state; read and written via the User Management API. | Views is specific to ClickHouse and Users to Smartrecruiters — each maps to any object or custom field on the other side. | |
| Materialized views Insert-time transformations that reshape incoming synced rows into aggregates. | Approvals Approval requests for jobs and offers; requests can be created, retrieved as pending, commented on, and approved or rejected via the Approvals API. | Materialized views is specific to ClickHouse and Approvals to Smartrecruiters — each maps to any object or custom field on the other side. | |
| Distributed tables Query-routing tables over cluster shards in self-managed deployments. | Candidates Person records with contact details, tags, attachments, custom properties, and consent; created, updated, and searched via the Candidates API, often populated from sourcing or enrichment pipelines. | Distributed tables is specific to ClickHouse and Candidates to Smartrecruiters — each maps to any object or custom field on the other side. | |
| Dictionaries In-memory lookup structures refreshed from external sources, sometimes fed by syncs. | Applications Links a Candidate to a Job and carries the current hiring status and source; created and advanced through statuses (screening, interview, offer, hired, rejected) via the Application API. | Dictionaries is specific to ClickHouse and Applications to Smartrecruiters — each maps to any object or custom field on the other side. | |
| Tables (MergeTree family) Columnar, append-optimized tables that serve as the destination for high-volume sync loads. | Jobs Requisitions (positions) with openings, departments, locations, and hiring team; created, patched, and read out for requisition and time-to-fill reporting via the Jobs API. | Tables (MergeTree family) is specific to ClickHouse and Jobs to Smartrecruiters — 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 ClickHouse for changes on an incremental schedule, reading only records changed since the previous pass. No log-based CDC for consumers.
DeliveryEach detected change is written to Smartrecruiters through its API, with automatic retries and rate-limit backoff.
DetectionSmartrecruiters notifies Stacksync of record changes through webhook events. Webhooks API — subscribe to events (new application, candidate updated, status changed) delivered with a signing secret and retrievable callback logs.
DeliveryEach detected change is applied to ClickHouse as a row-level write, with types converted between the two schemas.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every ClickHouse–Smartrecruiters connection.
Changes in ClickHouse or Smartrecruiters instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever ClickHouse or Smartrecruiters 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 Smartrecruiters record.
Track your ClickHouse ⇄ Smartrecruiters sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between ClickHouse and Smartrecruiters.
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 Smartrecruiters 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 Smartrecruiters 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 Smartrecruiters: authenticate both systems, choose the objects to sync (such as ClickHouse's Databases and Views), map fields visually, and changes propagate both ways in milliseconds — no code required.
Common patterns for ClickHouse and Smartrecruiters: Headcount and cost joined with everything else; Fresh data instead of last night's load; Queryable history for planning and audit. Analysts combine Smartrecruiters's workforce records with finance, product, or operational data already in ClickHouse for reporting the HR system cannot produce on its own.
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. Smartrecruiters: SmartRecruiters REST APIs (SmartAPIs) on api.smartrecruiters.com — Candidates, Application, Jobs, Interviews, Offers, Users, Approvals, plus a Webhooks API for event subscriptions. Authentication: X-SmartToken API key header for a customer's own integration (grants full company access, no scopes or expiry), or OAuth 2.0 authorization-code flow for partner and Marketplace apps with user-scoped permissions. Stacksync manages authentication, retries, and rate limits on both sides.
ClickHouse: Storage is columnar and organized by the MergeTree engine family, which makes large batched inserts far more efficient than single-row writes. Smartrecruiters: SmartRecruiters exposes a genuine two-way API — Candidates, Applications, Jobs, Job Postings, Interviews, and Offers can be created and updated, and applications moved through hiring statuses, not just read. Stacksync's field mapping accounts for these differences between ClickHouse and Smartrecruiters 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 ClickHouse and Smartrecruiters records are not retained after a sync operation.
Stacksync pricing is usage-based and starts at $1,000/month, including the managed ClickHouse and Smartrecruiters connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom ClickHouse–Smartrecruiters integration in-house.
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 540 integrations available for ClickHouse and Smartrecruiters.