Two-way sync
Changes in Oracle DB or Smartrecruiters instantly reflect in both systems. No stale data, no manual imports.
Keep Oracle DB 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. Oracle DB 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 Materialized views, Schemas, Sequences, PL/SQL procedures and packages in Oracle DB 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 Materialized views, Schemas, Sequences, PL/SQL procedures and packages in Oracle DB 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.
When a person record is added, changed, or deactivated in either system, the matching row in the other stays current, ending dual maintenance.
Offers, Users, Approvals, Candidates replicate into Oracle DB where they join operational tables, so headcount, roles, and status reports run on the live state without manual pulls.
Groups, departments, managers, and reporting lines from Smartrecruiters stay consistent in Oracle DB, so hierarchy-driven logic and permissions don't drift.
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.
| Oracle DB objects | Smartrecruiters objects | How this pairing syncs | |
|---|---|---|---|
| JSON columns Document data stored in the converged engine and synced alongside relational rows | 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). | JSON columns is specific to Oracle DB and Job Postings to Smartrecruiters — each maps to any object or custom field on the other side. | |
| Tables The primary read/write surface for row-level sync over SQL | 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 Oracle DB and Interviews to Smartrecruiters — each maps to any object or custom field on the other side. | |
| Views Curated read-only projections exposed to 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 Oracle DB and Offers to Smartrecruiters — each maps to any object or custom field on the other side. | |
| Materialized views Precomputed results occasionally used as stable replication sources | Users Company users (recruiters, hiring managers) with roles, access groups, and activation state; read and written via the User Management API. | Materialized views is specific to Oracle DB and Users to Smartrecruiters — each maps to any object or custom field on the other side. | |
| Schemas Per-user namespaces that scope sync permissions and object visibility | Approvals Approval requests for jobs and offers; requests can be created, retrieved as pending, commented on, and approved or rejected via the Approvals API. | Schemas is specific to Oracle DB and Approvals to Smartrecruiters — each maps to any object or custom field on the other side. | |
| Sequences Key generators to respect when external systems insert 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. | Sequences is specific to Oracle DB and Candidates 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 Oracle DB are captured at the source via change data capture — no polling loop against its API. Log-based CDC from redo logs via LogMiner or GoldenGate, or trigger and timestamp 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 Oracle DB as a row-level write, with types converted between the two schemas.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Oracle DB–Smartrecruiters connection.
Changes in Oracle DB or Smartrecruiters instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Oracle DB 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 Oracle DB or Smartrecruiters record.
Track your Oracle DB ⇄ Smartrecruiters sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Oracle DB 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 Oracle DB 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 Oracle DB 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 Oracle DB and Smartrecruiters: authenticate both systems, choose the objects to sync (such as Oracle DB's JSON columns 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 Oracle DB and Smartrecruiters connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Oracle DB–Smartrecruiters integration in-house.
Yes — Stacksync ships production-grade connectors for both Oracle DB and Smartrecruiters. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
Change detection on Oracle DB: Log-based CDC from redo logs via LogMiner or GoldenGate, or trigger and timestamp polling. 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 Oracle DB side: Materialized views, Schemas, Sequences, PL/SQL procedures and packages, plus custom fields where Oracle DB exposes them. On the Smartrecruiters side: Offers, Users, Approvals, Candidates. 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 458 integrations available for Oracle DB and Smartrecruiters.