Real-time
Two-way sync
Changes in MariaDB or Smartrecruiters instantly reflect in both systems. No stale data, no manual imports.
Database ⇄ Human resources
MariaDB to Smartrecruiters integration — real-time, two-way sync
Keep MariaDB 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 MariaDB and Smartrecruiters
Put your workforce data where your apps can reach it: MariaDB 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. MariaDB is where internal tools, dashboards, provisioning jobs, and analytics actually read and store records. The overlap is the workforce itself: Jobs, Job Postings, Interviews, Offers in Smartrecruiters need to exist as queryable Tables, Views, Columns, Primary and Unique Keys in MariaDB 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 Tables, Views, Columns, Primary and Unique Keys in MariaDB with Jobs, Job Postings, Interviews, Offers 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 Two-way sync between a MariaDB application database and a CRM so both systems hold the same customer records
- 02 Replicate ERP or billing master data into MariaDB databases that power customer-facing applications
- 03 Stream Jobs and Job Postings into a reporting database for requisition, funnel, and time-to-fill dashboards.
- 04 Export Interviews and Offers to a data warehouse to analyze interviewer load, offer-acceptance rates, and hiring outcomes.
Common sync patterns
Org and structure stay aligned
Groups, departments, managers, and reporting lines from Smartrecruiters stay consistent in MariaDB, so hierarchy-driven logic and permissions don't drift.
Computed and operational fields flow back
Values assembled or corrected in MariaDB write onto the matching record in Smartrecruiters where those fields are writable, keeping the people system enriched.
Mirror people records into the database
Records maintained in Smartrecruiters land as queryable Tables, Views, Columns, Primary and Unique Keys in MariaDB, so internal apps and dashboards read live data instead of a periodic export.
What you can sync between MariaDB 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.
| MariaDB objects | Smartrecruiters objects | How this pairing syncs | |
|---|---|---|---|
| Databases (Schemas) Top-level namespaces that scope a sync's reads and writes. | Interviews Interview types, timeslots, templates, and scheduled interviews with interviewers and times; created, updated, and read for scheduling and interviewer-load analytics. | Databases (Schemas) is specific to MariaDB and Interviews to Smartrecruiters — each maps to any object or custom field on the other side. | |
| Tables The primary sync target; rows map to records in connected systems. | 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). | Tables is specific to MariaDB and Offers to Smartrecruiters — each maps to any object or custom field on the other side. | |
| Views Read-side projections used as outbound sync sources. | Users Company users (recruiters, hiring managers) with roles, access groups, and activation state; read and written via the User Management API. | Views is specific to MariaDB and Users to Smartrecruiters — each maps to any object or custom field on the other side. | |
| Columns Field-level mapping targets with engine-typed values. | Approvals Approval requests for jobs and offers; requests can be created, retrieved as pending, commented on, and approved or rejected via the Approvals API. | Columns is specific to MariaDB and Approvals to Smartrecruiters — each maps to any object or custom field on the other side. | |
| Primary and Unique Keys Match keys for idempotent upserts. | 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. | Primary and Unique Keys is specific to MariaDB and Candidates to Smartrecruiters — each maps to any object or custom field on the other side. | |
| System-Versioned Tables Temporal tables that retain row history natively, useful for auditing synced changes. | 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. | System-Versioned Tables is specific to MariaDB and Applications to Smartrecruiters — each maps to any object or custom field on the other side. |
How changes propagate between MariaDB 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.
MariaDB Smartrecruiters Sub-second propagation
DetectionChanges in MariaDB are captured at the source via change data capture — no polling loop against its API. Database triggers — Stacksync creates deterministic triggers for internal logging and syncing.
DeliveryEach detected change is written to Smartrecruiters through its API, with automatic retries and rate-limit backoff.
Smartrecruiters MariaDB 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 MariaDB as a row-level write, with types converted between the two schemas.
Rate-limit considerations
- MariaDB: No API rate limits; throughput is bounded by connection limits and server resources.
- 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 MariaDB ⇄ Smartrecruiters
Connect MariaDB and Smartrecruiters for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every MariaDB–Smartrecruiters connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever MariaDB 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 MariaDB or Smartrecruiters record.
Observability
Monitoring
Track your MariaDB ⇄ Smartrecruiters sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between MariaDB and Smartrecruiters.
How the MariaDB and Smartrecruiters connectors work
MariaDB
- Integration surface
- SQL wire protocol (MySQL-compatible client/server protocol)
- Authentication
- Database credentials (connection string or parameters), with optional SSL root certificate upload and optional SSH tunnel (SSH user + host)
- Change detection
- Database triggers — Stacksync creates deterministic triggers for internal logging and syncing
- Capabilities
- read · write · CDC
- Rate limits
- No API rate limits; throughput is bounded by connection limits and server resources
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 MariaDB 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 MariaDB 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.
MariaDB
connected
Smartrecruiters
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the MariaDB 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 · MariaDB ⇄ 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.
MariaDB SmartrecruitersCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
MariaDB and Smartrecruiters integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between MariaDB and Smartrecruiters: authenticate both systems, choose the objects to sync (such as MariaDB's Databases (Schemas) and Tables), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Yes — Stacksync ships production-grade connectors for both MariaDB and Smartrecruiters. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
-
Change detection on MariaDB: Database triggers — Stacksync creates deterministic triggers for internal logging and syncing. 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 MariaDB side: Tables, Views, Columns, Primary and Unique Keys, plus custom fields where MariaDB exposes them. On the Smartrecruiters side: Jobs, Job Postings, Interviews, Offers. 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 MariaDB and Smartrecruiters: Org and structure stay aligned; Computed and operational fields flow back; Mirror people records into the database. Groups, departments, managers, and reporting lines from Smartrecruiters stay consistent in MariaDB, so hierarchy-driven logic and permissions don't drift.
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 443 integrations available for MariaDB and Smartrecruiters.
Popular · 7 of 443
-
MariaDB ⇄ Hibob -
MariaDB ⇄ Ceridian Dayforce -
MariaDB ⇄ Oracle Fusion Cloud HCM -
Smartrecruiters ⇄ Jdbc -
Smartrecruiters ⇄ Render Postgres -
Smartrecruiters ⇄ PostgreSQL -
Smartrecruiters ⇄ Amazon RDS
No integrations match .
