Two-way sync
Changes in MySQL or Smartrecruiters instantly reflect in both systems. No stale data, no manual imports.
Keep MySQL 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. MySQL is where internal tools, dashboards, provisioning jobs, and analytics actually read and store records. The overlap is the workforce itself: Users, Approvals, Candidates, Applications in Smartrecruiters need to exist as queryable Triggers, Databases (Schemas), Tables, Views in MySQL 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 Triggers, Databases (Schemas), Tables, Views in MySQL with Users, Approvals, Candidates, Applications 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.
Records maintained in Smartrecruiters land as queryable Triggers, Databases (Schemas), Tables, Views in MySQL, so internal apps and dashboards read live data instead of a periodic export.
When a person record is added, changed, or deactivated in either system, the matching row in the other stays current, ending dual maintenance.
Users, Approvals, Candidates, Applications replicate into MySQL where they join operational tables, so headcount, roles, and status reports run on the live state without manual pulls.
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.
| MySQL objects | Smartrecruiters objects | How this pairing syncs | |
|---|---|---|---|
| Columns Field-level mapping targets with engine-typed values. | 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). | Columns is specific to MySQL and Offers to Smartrecruiters — each maps to any object or custom field on the other side. | |
| Primary and Unique Keys Match keys for idempotent upserts and conflict handling. | Users Company users (recruiters, hiring managers) with roles, access groups, and activation state; read and written via the User Management API. | Primary and Unique Keys is specific to MySQL and Users to Smartrecruiters — each maps to any object or custom field on the other side. | |
| JSON Columns Validated semi-structured payloads for nested SaaS data. | Approvals Approval requests for jobs and offers; requests can be created, retrieved as pending, commented on, and approved or rejected via the Approvals API. | JSON Columns is specific to MySQL and Approvals to Smartrecruiters — each maps to any object or custom field on the other side. | |
| Stored Procedures Server-side logic that can post-process synced rows. | 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. | Stored Procedures is specific to MySQL and Candidates to Smartrecruiters — each maps to any object or custom field on the other side. | |
| Triggers An alternative change-capture mechanism when binlog access is unavailable. | 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. | Triggers is specific to MySQL and Applications to Smartrecruiters — each maps to any object or custom field on the other side. | |
| Databases (Schemas) Top-level namespaces that scope a sync's reads and writes. | 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. | Databases (Schemas) is specific to MySQL 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 MySQL 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 (requires log_bin_trust_function_creators=ON when.
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 MySQL as a row-level write, with types converted between the two schemas.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every MySQL–Smartrecruiters connection.
Changes in MySQL or Smartrecruiters instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever MySQL 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 MySQL or Smartrecruiters record.
Track your MySQL ⇄ Smartrecruiters sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between MySQL 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 MySQL 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 MySQL 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 MySQL and Smartrecruiters: authenticate both systems, choose the objects to sync (such as MySQL's Columns and Primary and Unique Keys), map fields visually, and changes propagate both ways in milliseconds — no code required.
Common patterns for MySQL and Smartrecruiters: Mirror people records into the database; One directory of record; Reporting and analytics on current data. Records maintained in Smartrecruiters land as queryable Triggers, Databases (Schemas), Tables, Views in MySQL, so internal apps and dashboards read live data instead of a periodic export.
MySQL: SQL wire protocol (MySQL client/server protocol). Authentication: Database credentials entered as a connection string or parameters, with optional SSL root certificate upload and optional SSH tunnel (SSH user + SSH host). Smartrecruiters: 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. Stacksync manages authentication, retries, and rate limits on both sides.
MySQL: The binary log in ROW format records every row-level change, enabling log-based CDC without adding triggers to user tables. Smartrecruiters: Change tracking uses the Webhooks API (event subscriptions with a signing secret and callback logs) plus updated-after-style polling; there is no log-based change data capture. Stacksync's field mapping accounts for these differences between MySQL 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 MySQL and Smartrecruiters records are not retained after a sync operation.
Stacksync pricing is usage-based and starts at $1,000/month, including the managed MySQL and Smartrecruiters connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom MySQL–Smartrecruiters integration in-house.
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 546 integrations available for MySQL and Smartrecruiters.