Two-way sync
Changes in Couchbase or Smartrecruiters instantly reflect in both systems. No stale data, no manual imports.
Keep Couchbase 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. Couchbase is where internal tools, dashboards, provisioning jobs, and analytics actually read and store records. The overlap is the workforce itself: Applications, Jobs, Job Postings, Interviews in Smartrecruiters need to exist as queryable XDCR replications, Full-text search indexes, Buckets, Scopes in Couchbase 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 XDCR replications, Full-text search indexes, Buckets, Scopes in Couchbase with Applications, Jobs, Job Postings, Interviews 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.
When a person record is added, changed, or deactivated in either system, the matching row in the other stays current, ending dual maintenance.
Applications, Jobs, Job Postings, Interviews replicate into Couchbase 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 Couchbase, so hierarchy-driven logic and permissions don't drift.
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.
| Couchbase objects | Smartrecruiters objects | How this pairing syncs | |
|---|---|---|---|
| JSON Documents The core records; schemaless JSON keyed by document id, flattened or mapped to relational rows 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). | JSON Documents is specific to Couchbase and Offers to Smartrecruiters — each maps to any object or custom field on the other side. | |
| Global Secondary Indexes Indexes that make SQL++ query-based extraction efficient. | Users Company users (recruiters, hiring managers) with roles, access groups, and activation state; read and written via the User Management API. | Global Secondary Indexes is specific to Couchbase and Users to Smartrecruiters — each maps to any object or custom field on the other side. | |
| XDCR replications Cluster-to-cluster replication streams, useful context when choosing a sync source cluster. | Approvals Approval requests for jobs and offers; requests can be created, retrieved as pending, commented on, and approved or rejected via the Approvals API. | XDCR replications is specific to Couchbase and Approvals to Smartrecruiters — each maps to any object or custom field on the other side. | |
| Full-text search indexes Search indexes over documents, relevant when syncing searchable content. | 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. | Full-text search indexes is specific to Couchbase and Candidates to Smartrecruiters — each maps to any object or custom field on the other side. | |
| Buckets Top-level data containers, roughly analogous to a database, that scope replication and memory quotas. | 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. | Buckets is specific to Couchbase and Applications to Smartrecruiters — each maps to any object or custom field on the other side. | |
| Scopes Namespaces inside a bucket used to group collections, similar to schemas. | 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. | Scopes is specific to Couchbase 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.
DetectionChanges in Couchbase are captured at the source via change data capture — no polling loop against its API. Database Change Protocol (DCP) streams document mutations.
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 Couchbase as a row-level write, with types converted between the two schemas.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Couchbase–Smartrecruiters connection.
Changes in Couchbase or Smartrecruiters instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Couchbase 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 Couchbase or Smartrecruiters record.
Track your Couchbase ⇄ Smartrecruiters sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Couchbase 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 Couchbase 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 Couchbase 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 Couchbase and Smartrecruiters: authenticate both systems, choose the objects to sync (such as Couchbase's JSON Documents and Global Secondary Indexes), map fields visually, and changes propagate both ways in milliseconds — no code required.
Couchbase: The Database Change Protocol (DCP) exposes an ordered stream of document mutations, and it is the same mechanism Couchbase's own XDCR replication and Kafka connector consume. Smartrecruiters: Authentication is either an X-SmartToken API key (full company access, no scopes or expiry) or an OAuth 2.0 authorization-code flow that scopes access to the authorizing user's permissions. Stacksync's field mapping accounts for these differences between Couchbase 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 Couchbase and Smartrecruiters records are not retained after a sync operation.
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Couchbase and Smartrecruiters connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Couchbase–Smartrecruiters integration in-house.
Yes — Stacksync ships production-grade connectors for both Couchbase and Smartrecruiters. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
Change detection on Couchbase: Database Change Protocol (DCP) streams document mutations; SQL++ polling on document fields as an alternative. 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.
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 421 integrations available for Couchbase and Smartrecruiters.