Real-time
Two-way sync
Changes in DuckDB or Smartrecruiters instantly reflect in both systems. No stale data, no manual imports.
Database ⇄ Human resources
DuckDB to Smartrecruiters integration — real-time, two-way sync
Keep DuckDB 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.
- SOC 2 and 6 other compliance frameworks
- POC with real engineers in minutes
Adopted by fast-scaling companies moving mission-critical data in real time
Case study
Migrated from MuleSoft
Case study
Migrated from Celigo
Migrated from Heroku Connect
Migrated from Matillion
Case study
Migrated from Fivetran
Case study
Migrated from Celigo
Why teams connect DuckDB and Smartrecruiters
Put your workforce data where your apps can reach it: DuckDB and Smartrecruiters share the same people, positions, and org structure in real time.
Smartrecruiters is the system of record for the people side of the business — employees, candidates, roles, and the org structure around them. DuckDB 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 Database files, Schemas, Tables, Views in DuckDB 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 Database files, Schemas, Tables, Views in DuckDB 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.
Common use cases
- 01 Use DuckDB as a transform step: read synced Parquet exports, aggregate with SQL, and write results back to an operational database.
- 02 Sync SaaS data to Parquet on object storage and query it with DuckDB without standing up a warehouse.
- 03 Export Interviews and Offers to a data warehouse to analyze interviewer load, offer-acceptance rates, and hiring outcomes.
- 04 Subscribe to the Webhooks API to react to new applications and status changes in near real time across downstream systems.
Common sync patterns
Mirror people records into the database
Records maintained in Smartrecruiters land as queryable Database files, Schemas, Tables, Views in DuckDB, so internal apps and dashboards read live data instead of a periodic export.
One directory of record
When a person record is added, changed, or deactivated in either system, the matching row in the other stays current, ending dual maintenance.
Reporting and analytics on current data
Offers, Users, Approvals, Candidates replicate into DuckDB where they join operational tables, so headcount, roles, and status reports run on the live state without manual pulls.
What you can sync between DuckDB and Smartrecruiters
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.
| DuckDB objects | Smartrecruiters objects | How this pairing syncs | |
|---|---|---|---|
| Attached databases Additional database files or external systems attached into one session for cross-source queries. | 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. | Attached databases is specific to DuckDB and Applications to Smartrecruiters — each maps to any object or custom field on the other side. | |
| Database files Single-file .duckdb databases that jobs read and write directly on disk or object storage. | 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. | Database files is specific to DuckDB and Jobs to Smartrecruiters — each maps to any object or custom field on the other side. | |
| Schemas Namespaces within a database used to organize tables in sync outputs. | 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). | Schemas is specific to DuckDB and Job Postings to Smartrecruiters — each maps to any object or custom field on the other side. | |
| Tables Columnar tables created via SQL; the destination for materialized sync data. | Interviews Interview types, timeslots, templates, and scheduled interviews with interviewers and times; created, updated, and read for scheduling and interviewer-load analytics. | Tables is specific to DuckDB and Interviews to Smartrecruiters — each maps to any object or custom field on the other side. | |
| Views SQL views used to shape or filter data for downstream consumers. | 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). | Views is specific to DuckDB and Offers to Smartrecruiters — each maps to any object or custom field on the other side. | |
| External files (Parquet/CSV/JSON) Files DuckDB queries in place without loading, common as a sync interchange format. | Users Company users (recruiters, hiring managers) with roles, access groups, and activation state; read and written via the User Management API. | External files (Parquet/CSV/JSON) is specific to DuckDB and Users to Smartrecruiters — each maps to any object or custom field on the other side. |
How changes propagate between DuckDB and Smartrecruiters
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.
DuckDB Smartrecruiters Interval-based propagation
DetectionStacksync polls DuckDB for changes on an incremental schedule, reading only records changed since the previous pass. Polling or full re-reads.
DeliveryEach detected change is written to Smartrecruiters through its API, with automatic retries and rate-limit backoff.
Smartrecruiters DuckDB Sub-second propagation
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 DuckDB as a row-level write, with types converted between the two schemas.
Rate-limit considerations
- DuckDB: No API rate limits; throughput is bounded by local compute and I/O.
- Smartrecruiters: Per API credential: most endpoints allow up to 10 requests/sec (job publication and offer documents 2/sec), plus a concurrency limiter of up to 8 simultaneous requests (GET /candidates capped at 1). Exceeding returns 429; responses carry X-RateLimit-Limit/Remaining and concurrent-limit headers.
What ships with DuckDB ⇄ Smartrecruiters
Connect DuckDB and Smartrecruiters for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every DuckDB–Smartrecruiters connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever DuckDB or Smartrecruiters data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
At scale
Event queues
Handle millions of events per minute without losing a single DuckDB or Smartrecruiters record.
Observability
Monitoring
Track your DuckDB ⇄ Smartrecruiters sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between DuckDB and Smartrecruiters.
How the DuckDB and Smartrecruiters connectors work
DuckDB
- Integration surface
- In-process SQL engine via client libraries (Python, Node.js, JDBC, CLI); no server or network API by default
- Authentication
- None built in; access control is file-system level (MotherDuck adds token auth for its hosted service)
- Change detection
- Polling or full re-reads; no change feed or transaction log API
- Capabilities
- read · write
- Rate limits
- No API rate limits; throughput is bounded by local compute and I/O
Smartrecruiters
- Integration surface
- 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
- Change detection
- 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.
- Capabilities
- read · write · webhooks
- Rate limits
- Per API credential: most endpoints allow up to 10 requests/sec (job publication and offer documents 2/sec), plus a concurrency limiter of up to 8 simultaneous requests (GET /candidates capped at 1). Exceeding returns 429; responses carry X-RateLimit-Limit/Remaining and concurrent-limit headers.
How it works
How to connect DuckDB to Smartrecruiters — three steps, no code
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.
- 01
Connect your apps
Authenticate DuckDB 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.
DuckDB
connected
Smartrecruiters
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the DuckDB 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.
objects · DuckDB ⇄ SmartrecruitersCustomers 12,480Sales Orders 8,213Invoices 5,902Items 1,344 - 03
Map fields
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
DuckDB SmartrecruitersCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
DuckDB and Smartrecruiters integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between DuckDB and Smartrecruiters: authenticate both systems, choose the objects to sync (such as DuckDB's Attached databases and Database files), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
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 DuckDB and Smartrecruiters records are not retained after a sync operation.
-
Stacksync pricing is usage-based and starts at $1,000/month, including the managed DuckDB and Smartrecruiters connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom DuckDB–Smartrecruiters integration in-house.
-
Yes — Stacksync ships production-grade connectors for both DuckDB and Smartrecruiters. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
-
Change detection on DuckDB: Polling or full re-reads; no change feed or transaction log API. 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 DuckDB side: Database files, Schemas, Tables, Views, plus custom fields where DuckDB exposes them. On the Smartrecruiters side: Offers, Users, Approvals, Candidates. Stacksync auto-detects both schemas and converts types between the two systems.
SECURITY
Security teams trust Stacksync
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.
SOC 2 Type II
ISO 27001
HIPAA BAA
GDPR
CCPA
DPF US-EU-UK-CH
→ SECURITY WITH BENEFITS
SSO & SCIM
Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.
Alerts
Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.
Secure connection options
Securely connects to your systems with:
Related integrations
Every pair below is a real-time, two-way sync. Search all 448 integrations available for DuckDB and Smartrecruiters.
Popular · 8 of 448
-
DuckDB ⇄ Paylocity -
DuckDB ⇄ Ukg Ready -
DuckDB ⇄ BambooHR -
DuckDB ⇄ Success Factors -
Smartrecruiters ⇄ Render Postgres -
Smartrecruiters ⇄ PostgreSQL -
Smartrecruiters ⇄ Amazon RDS -
Smartrecruiters ⇄ Supabase
No integrations match .
