Two-way sync
Changes in Smartrecruiters or VoltDB instantly reflect in both systems. No stale data, no manual imports.
Keep Smartrecruiters and VoltDB 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. VoltDB is where internal tools, dashboards, provisioning jobs, and analytics actually read and store records. The overlap is the workforce itself: Offers, Users, Approvals, Candidates in Smartrecruiters need to exist as queryable Stored Procedures, Materialized Views, Streams, Export Targets and Topics in VoltDB 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 Stored Procedures, Materialized Views, Streams, Export Targets and Topics in VoltDB with Offers, Users, Approvals, Candidates 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.
Offers, Users, Approvals, Candidates replicate into VoltDB where they join operational tables, so headcount, roles, and status reports run on the live state without manual pulls.
Groups, departments, managers, and reporting lines from Smartrecruiters stay consistent in VoltDB, so hierarchy-driven logic and permissions don't drift.
Values assembled or corrected in VoltDB write onto the matching record in Smartrecruiters where those fields are writable, keeping the people system enriched.
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.
| Smartrecruiters objects | VoltDB objects | How this pairing syncs | |
|---|---|---|---|
| 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 Synchronously maintained aggregates over tables, useful as pre-computed read sources. | Approvals is specific to Smartrecruiters and Materialized Views to VoltDB — each maps to any object or custom field on the other side. | |
| 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. | Streams Insert-only constructs that feed the export subsystem with committed rows. | Candidates is specific to Smartrecruiters and Streams to VoltDB — each maps to any object or custom field on the other side. | |
| 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. | Export Targets and Topics Connectors that push committed data to external systems such as Kafka or JDBC sinks. | Applications is specific to Smartrecruiters and Export Targets and Topics to VoltDB — each maps to any object or custom field on the other side. | |
| 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. | Partitioned Tables Tables sharded across partitions by a partitioning column; the primary transactional store and sync target. | Jobs is specific to Smartrecruiters and Partitioned Tables to VoltDB — each maps to any object or custom field on the other side. | |
| 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). | Replicated Tables Small reference tables copied to every partition, a common landing spot for synced lookup data. | Job Postings is specific to Smartrecruiters and Replicated Tables to VoltDB — each maps to any object or custom field on the other side. | |
| Interviews Interview types, timeslots, templates, and scheduled interviews with interviewers and times; created, updated, and read for scheduling and interviewer-load analytics. | Stored Procedures Precompiled transactional units that serve as the primary write interface. | Interviews is specific to Smartrecruiters and Stored Procedures to VoltDB — 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.
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 VoltDB as a row-level write, with types converted between the two schemas.
DetectionStacksync polls VoltDB for changes on an incremental schedule, reading only records changed since the previous pass. Export streams and topics push committed changes to configured targets.
DeliveryEach detected change is written to Smartrecruiters through its API, with automatic retries and rate-limit backoff.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Smartrecruiters–VoltDB connection.
Changes in Smartrecruiters or VoltDB instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Smartrecruiters or VoltDB data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single Smartrecruiters or VoltDB record.
Track your Smartrecruiters ⇄ VoltDB sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Smartrecruiters and VoltDB.
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 Smartrecruiters and VoltDB 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 Smartrecruiters and VoltDB 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 Smartrecruiters and VoltDB: authenticate both systems, choose the objects to sync (such as Smartrecruiters's Approvals and Candidates), map fields visually, and changes propagate both ways in milliseconds — no code required.
Yes — Stacksync ships production-grade connectors for both Smartrecruiters and VoltDB. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
Change detection 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. On VoltDB: Export streams and topics push committed changes to configured targets; otherwise polling. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
On the VoltDB side: Stored Procedures, Materialized Views, Streams, Export Targets and Topics, plus custom fields where VoltDB exposes them. On the Smartrecruiters side: Offers, Users, Approvals, Candidates. 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 Smartrecruiters and VoltDB: Reporting and analytics on current data; Org and structure stay aligned; Computed and operational fields flow back. Offers, Users, Approvals, Candidates replicate into VoltDB where they join operational tables, so headcount, roles, and status reports run on the live state without manual pulls.
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 445 integrations available for Smartrecruiters and VoltDB.