Two-way sync
Changes in Full Enrich or Oracle Fusion Cloud HCM instantly reflect in both systems. No stale data, no manual imports.
Keep Full Enrich and Oracle Fusion Cloud HCM in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.
Each tool in Full Enrich keeps its own list of who can use it: users, members, or agents, along with the team they sit on and whether they are still active. Oracle Fusion Cloud HCM is the authoritative record of the same people as employees, with their department, manager, and employment status. When those two are connected only by manual account admin or a periodic export, the work tools drift: new hires wait days for access, team and manager changes never catch up, and people who have left keep standing accounts.
Stacksync syncs Credits, Enrichment requests, Contacts, Enrichment results in Full Enrich with Assignments, Jobs, Positions, Departments (Organizations) in Oracle Fusion Cloud HCM bi-directionally and in real time. A person added, moved, or offboarded in Oracle Fusion Cloud HCM creates or updates the matching user in Full Enrich within seconds, with field-level mapping and conflict resolution in place of spreadsheets and one-off account changes. Where Full Enrich captures details of its own, such as a corrected contact or a login identity, those can flow back to Oracle Fusion Cloud HCM in whichever direction you configure.
Because the sync is field-level, each system keeps its own extras; only the shared facts, who a person is, which team they belong to, and whether their access should be on, are held in agreement.
When someone is marked as leaving in Oracle Fusion Cloud HCM, the matching account in Full Enrich is deactivated or flagged, so departures do not leave open access behind.
A person's name, title, contact details, or status corrected in either system updates the other, so both sides stop maintaining separate copies of the same person.
Department, team, and reporting-line changes from Oracle Fusion Cloud HCM keep the groups, queues, or projects in Full Enrich assigned to the right people.
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.
| Full Enrich objects | Oracle Fusion Cloud HCM objects | How this pairing syncs | |
|---|---|---|---|
| Enrichment requests Submitted batches of contacts to enrich; processed asynchronously by the waterfall. | Positions Position-management records used where positions control headcount; synced to keep vacancy and reporting structures aligned with finance/ERP. | Enrichment requests is specific to Full Enrich and Positions to Oracle Fusion Cloud HCM — each maps to any object or custom field on the other side. | |
| Contacts The person inputs (name plus company or domain) sent for enrichment. | Departments (Organizations) Org-structure records that define cost centers and reporting lines; typically mastered in HCM and read into other systems. | Contacts is specific to Full Enrich and Departments (Organizations) to Oracle Fusion Cloud HCM — each maps to any object or custom field on the other side. | |
| Enrichment results Completed records fetched by request ID or delivered via webhook. | Locations Physical work locations referenced by assignments; synced so downstream provisioning and directory tools resolve the same location codes. | Enrichment results is specific to Full Enrich and Locations to Oracle Fusion Cloud HCM — each maps to any object or custom field on the other side. | |
| Emails Returned addresses with verification status, written back to the CRM or database. | Grades and Salaries Grade, grade-rate, and worker compensation records; usually read out for compensation and headcount analytics, and written back for corrections. | Emails is specific to Full Enrich and Grades and Salaries to Oracle Fusion Cloud HCM — each maps to any object or custom field on the other side. | |
| Phone numbers Returned mobile and direct-dial numbers from the provider waterfall. | Absences (workerAbsenceEntries) Time-off and leave entries; synced into scheduling or workforce-management databases for coverage planning. | Phone numbers is specific to Full Enrich and Absences (workerAbsenceEntries) to Oracle Fusion Cloud HCM — each maps to any object or custom field on the other side. | |
| Credits Account balance consumed on successful finds; monitored to pace sync jobs. | Workers (publicWorkers) Person master with personNumber, names, national IDs, and work relationships; synced two-way via the /workers resource, which replaced the desupported /emps resource. | Credits is specific to Full Enrich and Workers (publicWorkers) to Oracle Fusion Cloud HCM — 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.
DetectionFull Enrich notifies Stacksync of record changes through webhook events. Webhook callbacks when enrichment batches complete, with polling of result endpoints as a fallback.
DeliveryEach detected change is written to Oracle Fusion Cloud HCM through its API, with automatic retries and rate-limit backoff.
DetectionChanges in Oracle Fusion Cloud HCM are captured at the source via change data capture — no polling loop against its API. Atom feeds expose changes-only feeds for key events (new hire, termination, assignment change).
DeliveryEach detected change is written to Full Enrich through its API, with automatic retries and rate-limit backoff.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Full Enrich–Oracle Fusion Cloud HCM connection.
Changes in Full Enrich or Oracle Fusion Cloud HCM instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Full Enrich or Oracle Fusion Cloud HCM data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single Full Enrich or Oracle Fusion Cloud HCM record.
Track your Full Enrich ⇄ Oracle Fusion Cloud HCM sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Full Enrich and Oracle Fusion Cloud HCM.
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 Full Enrich and Oracle Fusion Cloud HCM 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 Full Enrich and Oracle Fusion Cloud HCM 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 Full Enrich and Oracle Fusion Cloud HCM: authenticate both systems, choose the objects to sync (such as Full Enrich's Enrichment requests and Contacts), 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 Full Enrich and Oracle Fusion Cloud HCM connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Full Enrich–Oracle Fusion Cloud HCM integration in-house.
Yes — Stacksync ships production-grade connectors for both Full Enrich and Oracle Fusion Cloud HCM. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
Change detection on Full Enrich: Webhook callbacks when enrichment batches complete, with polling of result endpoints as a fallback. On Oracle Fusion Cloud HCM: Atom feeds expose changes-only feeds for key events (new hire, termination, assignment change); REST q= filters on LastUpdateDate and HCM Extract in incremental mode cover broader deltas. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
On the Full Enrich side: Credits, Enrichment requests, Contacts, Enrichment results, plus custom fields where Full Enrich exposes them. On the Oracle Fusion Cloud HCM side: Assignments, Jobs, Positions, Departments (Organizations). 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 385 integrations available for Full Enrich and Oracle Fusion Cloud HCM.