Two-way sync
Changes in MotherDuck or Smartrecruiters instantly reflect in both systems. No stale data, no manual imports.
Keep MotherDuck 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 MotherDuck next to everything else the company measures.
Stacksync syncs Users, Approvals, Candidates, Applications from Smartrecruiters into tables in MotherDuck continuously, handling API limits and schema drift as they come. The connection is bi-directional, so values computed in MotherDuck, 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.
Because changes stream continuously, reports query current workforce data rather than waiting for an overnight load window to finish.
A continuously synced copy in MotherDuck gives you a durable, queryable record of how Smartrecruiters's records change over time, for headcount planning and audit questions.
Segments, rollups, or risk flags computed in MotherDuck sync back onto the matching records in Smartrecruiters, where the HR team sees them in the system they already use.
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.
| MotherDuck objects | Smartrecruiters objects | How this pairing syncs | |
|---|---|---|---|
| Schemas Namespaces within a database used to organize synced tables. | 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. | Schemas is specific to MotherDuck and Candidates to Smartrecruiters — each maps to any object or custom field on the other side. | |
| Tables The main landing target for synced records and source for analysis. | 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. | Tables is specific to MotherDuck and Applications to Smartrecruiters — each maps to any object or custom field on the other side. | |
| Views Modeled projections used as outbound sync sources. | 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. | Views is specific to MotherDuck and Jobs to Smartrecruiters — each maps to any object or custom field on the other side. | |
| Database Shares Read-only copies of a database shared with other users or teams. | 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). | Database Shares is specific to MotherDuck and Job Postings to Smartrecruiters — each maps to any object or custom field on the other side. | |
| Attached Local DuckDB Databases Local files attached alongside cloud databases for hybrid queries. | Interviews Interview types, timeslots, templates, and scheduled interviews with interviewers and times; created, updated, and read for scheduling and interviewer-load analytics. | Attached Local DuckDB Databases is specific to MotherDuck and Interviews to Smartrecruiters — each maps to any object or custom field on the other side. | |
| Databases Cloud-hosted DuckDB databases that scope a sync's reads and writes. | 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 MotherDuck and Offers 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 MotherDuck for changes on an incremental schedule, reading only records changed since the previous pass. Polling.
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 MotherDuck as a row-level write, with types converted between the two schemas.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every MotherDuck–Smartrecruiters connection.
Changes in MotherDuck or Smartrecruiters instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever MotherDuck 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 MotherDuck or Smartrecruiters record.
Track your MotherDuck ⇄ Smartrecruiters sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between MotherDuck 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 MotherDuck 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 MotherDuck 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 MotherDuck and Smartrecruiters: authenticate both systems, choose the objects to sync (such as MotherDuck's Schemas and Tables), map fields visually, and changes propagate both ways in milliseconds — no code required.
Stacksync pricing is usage-based and starts at $1,000/month, including the managed MotherDuck and Smartrecruiters connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom MotherDuck–Smartrecruiters integration in-house.
Yes — Stacksync ships production-grade connectors for both MotherDuck and Smartrecruiters. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
Change detection on MotherDuck: Polling; no log-based CDC or webhook surface is exposed. 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 MotherDuck side: Schemas, Tables, Views, Database Shares, plus custom fields where MotherDuck exposes them. On the Smartrecruiters side: Users, Approvals, Candidates, Applications. 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.
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 MotherDuck and Smartrecruiters.