Two-way sync
Changes in SingleStore or Smartrecruiters instantly reflect in both systems. No stale data, no manual imports.
Keep SingleStore 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.
Smartrecruiters is the system of record for the people side of the business — employees, candidates, roles, and the org structure around them. SingleStore is where internal tools, dashboards, provisioning jobs, and analytics actually read and store records. The overlap is the workforce itself: Jobs, Job Postings, Interviews, Offers in Smartrecruiters need to exist as queryable Views, Reference Tables, Pipelines, Stored Procedures in SingleStore before an app can act on them. When that bridge is a nightly export or a hand-run CSV, every downstream system spends the day working from a roster that has already moved on.
Stacksync syncs Views, Reference Tables, Pipelines, Stored Procedures in SingleStore with Jobs, Job Postings, Interviews, Offers in Smartrecruiters field by field, in real time. You decide which system owns which fields — Smartrecruiters typically owns identity and org attributes, while operational or computed values can flow back the other way — and Stacksync keeps every copy consistent, matching records on a stable key and resolving conflicts by rules you set.
The result is one live picture of the workforce on both sides: HR keeps its source of truth, and the database keeps a current mirror that internal apps, reports, and access controls can trust without a batch window in between.
Records maintained in Smartrecruiters land as queryable Views, Reference Tables, Pipelines, Stored Procedures in SingleStore, so internal apps and dashboards read live data instead of a periodic export.
When a person record is added, changed, or deactivated in either system, the matching row in the other stays current, ending dual maintenance.
Jobs, Job Postings, Interviews, Offers replicate into SingleStore where they join operational tables, so headcount, roles, and status reports run on the live state without manual pulls.
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.
| SingleStore objects | Smartrecruiters objects | How this pairing syncs | |
|---|---|---|---|
| Databases The connection target containing the tables a sync addresses. | 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. | Databases is specific to SingleStore and Jobs to Smartrecruiters — each maps to any object or custom field on the other side. | |
| Tables (rowstore and columnstore) Primary read/write target; storage type affects whether a table suits point lookups or scans. | Job Postings Job ads and publications pushed to the career site and job boards; created and managed via the job publication endpoints (rate-limited to 2 requests/sec). | Tables (rowstore and columnstore) is specific to SingleStore and Job Postings to Smartrecruiters — each maps to any object or custom field on the other side. | |
| Views Read-only projections used as curated sync sources. | Interviews Interview types, timeslots, templates, and scheduled interviews with interviewers and times; created, updated, and read for scheduling and interviewer-load analytics. | Views is specific to SingleStore and Interviews to Smartrecruiters — each maps to any object or custom field on the other side. | |
| Reference Tables Small tables replicated to every node, often used for dimension data in syncs. | 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). | Reference Tables is specific to SingleStore and Offers to Smartrecruiters — each maps to any object or custom field on the other side. | |
| Pipelines Native ingestion jobs from Kafka or object storage that coexist with external syncs. | Users Company users (recruiters, hiring managers) with roles, access groups, and activation state; read and written via the User Management API. | Pipelines is specific to SingleStore and Users to Smartrecruiters — each maps to any object or custom field on the other side. | |
| Stored Procedures Existing logic sometimes invoked on write paths. | Approvals Approval requests for jobs and offers; requests can be created, retrieved as pending, commented on, and approved or rejected via the Approvals API. | Stored Procedures is specific to SingleStore and Approvals 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 SingleStore for changes on an incremental schedule, reading only records changed since the previous pass. Polling on timestamp or watermark columns.
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 SingleStore as a row-level write, with types converted between the two schemas.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every SingleStore–Smartrecruiters connection.
Changes in SingleStore or Smartrecruiters instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever SingleStore 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 SingleStore or Smartrecruiters record.
Track your SingleStore ⇄ Smartrecruiters sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between SingleStore 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 SingleStore 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 SingleStore 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 SingleStore and Smartrecruiters: authenticate both systems, choose the objects to sync (such as SingleStore's Databases and Tables (rowstore and columnstore)), map fields visually, and changes propagate both ways in milliseconds — no code required.
Yes — Stacksync ships production-grade connectors for both SingleStore and Smartrecruiters. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
Change detection on SingleStore: Polling on timestamp or watermark columns; the platform also provides change-observation features in recent versions. On Smartrecruiters: Webhooks API — subscribe to events (new application, candidate updated, status changed) delivered with a signing secret and retrievable callback logs; otherwise poll list endpoints with updated-after-style filters. No log-based change data capture. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
On the SingleStore side: Views, Reference Tables, Pipelines, Stored Procedures, plus custom fields where SingleStore exposes them. On the Smartrecruiters side: Jobs, Job Postings, Interviews, Offers. 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 SingleStore and Smartrecruiters: Mirror people records into the database; One directory of record; Reporting and analytics on current data. Records maintained in Smartrecruiters land as queryable Views, Reference Tables, Pipelines, Stored Procedures in SingleStore, so internal apps and dashboards read live data instead of a periodic export.
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 449 integrations available for SingleStore and Smartrecruiters.