Real-time
Two-way sync
Changes in Databricks or Smartrecruiters instantly reflect in both systems. No stale data, no manual imports.
Data warehouse ⇄ Human resources
Databricks to Smartrecruiters integration — real-time, two-way sync
Keep Databricks 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 Databricks and Smartrecruiters
Land the people and organization records from Smartrecruiters in Databricks as live tables for workforce reporting, without extract jobs, and write computed results back where Smartrecruiters can use them.
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 Databricks next to everything else the company measures.
Stacksync syncs Approvals, Candidates, Applications, Jobs from Smartrecruiters into tables in Databricks continuously, handling API limits and schema drift as they come. The connection is bi-directional, so values computed in Databricks, 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.
Common use cases
- 01 Serve ML feature outputs computed in Databricks to production apps through a synced operational store.
- 02 Land CRM and ERP records in Delta tables continuously so lakehouse models work from current operational data.
- 03 Two-way sync Candidates and Applications with Postgres so recruiting-ops apps read and update hiring status, tags, and custom fields in SQL while recruiters keep working in SmartRecruiters.
- 04 Write enriched or sourced Candidates from external sourcing tools into SmartRecruiters and keep contact fields refreshed as data changes.
Common sync patterns
Fresh data instead of last night's load
Because changes stream continuously, reports query current workforce data rather than waiting for an overnight load window to finish.
Queryable history for planning and audit
A continuously synced copy in Databricks gives you a durable, queryable record of how Smartrecruiters's records change over time, for headcount planning and audit questions.
Write-back of computed values
Segments, rollups, or risk flags computed in Databricks sync back onto the matching records in Smartrecruiters, where the HR team sees them in the system they already use.
What you can sync between Databricks 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.
| Databricks objects | Smartrecruiters objects | How this pairing syncs | |
|---|---|---|---|
| Schemas Group tables and views; syncs typically target a dedicated schema per source system. | 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 Databricks and Candidates to Smartrecruiters — each maps to any object or custom field on the other side. | |
| Delta Tables The primary read and write target; operational data lands here as managed or external tables. | 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. | Delta Tables is specific to Databricks and Applications to Smartrecruiters — each maps to any object or custom field on the other side. | |
| Views Curated read-only projections used as sync sources for downstream tools. | 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 Databricks and Jobs to Smartrecruiters — each maps to any object or custom field on the other side. | |
| Materialized Views Precomputed results read on a schedule for reverse-ETL style syncs. | 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). | Materialized Views is specific to Databricks and Job Postings to Smartrecruiters — each maps to any object or custom field on the other side. | |
| Volumes Unity Catalog file storage used for staging bulk loads. | Interviews Interview types, timeslots, templates, and scheduled interviews with interviewers and times; created, updated, and read for scheduling and interviewer-load analytics. | Volumes is specific to Databricks and Interviews to Smartrecruiters — each maps to any object or custom field on the other side. | |
| SQL Warehouses The compute endpoint a sync connects to for query execution. | 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). | SQL Warehouses is specific to Databricks and Offers to Smartrecruiters — each maps to any object or custom field on the other side. |
How changes propagate between Databricks 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.
Databricks Smartrecruiters Sub-second propagation
DetectionChanges in Databricks are captured at the source via change data capture — no polling loop against its API. Delta Lake Change Data Feed for row-level changes.
DeliveryEach detected change is written to Smartrecruiters through its API, with automatic retries and rate-limit backoff.
Smartrecruiters Databricks 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 Databricks as a row-level write, with types converted between the two schemas.
Rate-limit considerations
- Databricks: Throughput depends on the SQL warehouse size; API calls are subject to workspace rate limits.
- 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 Databricks ⇄ Smartrecruiters
Connect Databricks and Smartrecruiters for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Databricks–Smartrecruiters connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Databricks 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 Databricks or Smartrecruiters record.
Observability
Monitoring
Track your Databricks ⇄ Smartrecruiters sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between Databricks and Smartrecruiters.
How the Databricks and Smartrecruiters connectors work
Databricks
- Integration surface
- SQL over JDBC/ODBC via SQL warehouses, plus a REST API including statement execution
- Authentication
- Personal access tokens or OAuth machine-to-machine credentials for service principals
- Change detection
- Delta Lake Change Data Feed for row-level changes; otherwise incremental polling on watermark columns
- Capabilities
- read · write · CDC
- Rate limits
- Throughput depends on the SQL warehouse size; API calls are subject to workspace rate limits
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 Databricks 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 Databricks 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.
Databricks
connected
Smartrecruiters
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Databricks 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 · Databricks ⇄ 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.
Databricks SmartrecruitersCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Databricks and Smartrecruiters integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Databricks and Smartrecruiters: authenticate both systems, choose the objects to sync (such as Databricks's Schemas and Delta Tables), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Databricks: Unity Catalog imposes a three-level namespace (catalog.schema.table) that governs access across workspaces. Smartrecruiters: Every response returns rate-limit metadata via X-RateLimit-Limit/Remaining and X-RateLimit-Concurrent-Limit/Remaining headers. Stacksync's field mapping accounts for these differences between Databricks 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 Databricks and Smartrecruiters records are not retained after a sync operation.
-
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Databricks and Smartrecruiters connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Databricks–Smartrecruiters integration in-house.
-
Yes — Stacksync ships production-grade connectors for both Databricks and Smartrecruiters. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
-
Change detection on Databricks: Delta Lake Change Data Feed for row-level changes; otherwise incremental polling on watermark columns. 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.
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 550 integrations available for Databricks and Smartrecruiters.
Popular · 8 of 550
-
Databricks ⇄ Paylocity -
Databricks ⇄ Ukg Ready -
Databricks ⇄ BambooHR -
Databricks ⇄ Success Factors -
Smartrecruiters ⇄ Apache Druid -
Smartrecruiters ⇄ Apache Hive -
Smartrecruiters ⇄ Apache Impala -
Smartrecruiters ⇄ Apache Kylin
No integrations match .
