Two-way sync
Changes in Nutshell or Oracle Fusion Cloud HCM instantly reflect in both systems. No stale data, no manual imports.
Keep Nutshell 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.
Nutshell runs on people as much as on accounts: every contact, deal, and account has an owner, and those owners are employees whose roles, teams, and status are held in Oracle Fusion Cloud HCM. Oracle Fusion Cloud HCM is the system of record for the workforce, from new hires to promotions to departures, and often for the candidates the business is still deciding on. When the two systems are connected only by re-keying or an overnight export, they drift apart, and the CRM ends up assigning accounts to people who have left, holding territories that no longer match the org chart, and waiting days to give a new rep access.
Stacksync syncs People, Companies, Activities, Tasks in Nutshell with Departments (Organizations), Locations, Grades and Salaries, Absences (workerAbsenceEntries) in Oracle Fusion Cloud HCM field by field, in real time, and in both directions. You decide which system owns which fields, so Oracle Fusion Cloud HCM stays authoritative on roles and org structure while Nutshell keeps ownership and territory current, and Stacksync resolves conflicts by the rules you set.
A person's name, title, email, phone, or manager corrected in either system updates the other, so both stop maintaining separate copies of the same individual.
A person recorded in Oracle Fusion Cloud HCM, such as a candidate or applicant, can create or update the matching contact in Nutshell, so relationship history and outreach are not rebuilt from scratch when the same individual appears in both.
When Oracle Fusion Cloud HCM records a new hire, a matching user or owner is created in Nutshell, so a new rep can start working accounts without waiting on a manual setup ticket.
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.
| Nutshell objects | Oracle Fusion Cloud HCM objects | How this pairing syncs | |
|---|---|---|---|
| Leads Nutshell's deal object; synced as the pipeline record linked to people and companies | Absences (workerAbsenceEntries) Time-off and leave entries; synced into scheduling or workforce-management databases for coverage planning. | Leads is specific to Nutshell and Absences (workerAbsenceEntries) to Oracle Fusion Cloud HCM — each maps to any object or custom field on the other side. | |
| People Individual contacts, kept consistent with marketing and outreach tools | 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. | People is specific to Nutshell and Workers (publicWorkers) to Oracle Fusion Cloud HCM — each maps to any object or custom field on the other side. | |
| Companies Account records that group people and leads for account-level syncs | Assignments Child of a worker's work relationship carrying job, position, department, location, grade, and manager; effective-dated, so writes go through PATCH with an effective date. | Companies is specific to Nutshell and Assignments to Oracle Fusion Cloud HCM — each maps to any object or custom field on the other side. | |
| Activities Logged calls, meetings, and emails used for engagement reporting | Jobs Job catalog reference data; commonly read out to align titles and job codes in a warehouse or written to keep downstream systems consistent. | Activities is specific to Nutshell and Jobs to Oracle Fusion Cloud HCM — each maps to any object or custom field on the other side. | |
| Tasks Rep to-dos mirrored into external work-management or reporting systems | Positions Position-management records used where positions control headcount; synced to keep vacancy and reporting structures aligned with finance/ERP. | Tasks is specific to Nutshell and Positions to Oracle Fusion Cloud HCM — each maps to any object or custom field on the other side. | |
| Notes Free-text history attached to leads and contacts, replicated for a full timeline | Departments (Organizations) Org-structure records that define cost centers and reporting lines; typically mastered in HCM and read into other systems. | Notes is specific to Nutshell and Departments (Organizations) 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.
DetectionNutshell notifies Stacksync of record changes through webhook events. Webhook subscriptions for record events, with polling as 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 Nutshell through its API, with automatic retries and rate-limit backoff.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Nutshell–Oracle Fusion Cloud HCM connection.
Changes in Nutshell or Oracle Fusion Cloud HCM instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Nutshell 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 Nutshell or Oracle Fusion Cloud HCM record.
Track your Nutshell ⇄ Oracle Fusion Cloud HCM sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Nutshell 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 Nutshell 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 Nutshell 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 Nutshell and Oracle Fusion Cloud HCM: authenticate both systems, choose the objects to sync (such as Nutshell's Leads and People), map fields visually, and changes propagate both ways in milliseconds — no code required.
On the Nutshell side: People, Companies, Activities, Tasks, plus custom fields where Nutshell exposes them. On the Oracle Fusion Cloud HCM side: Departments (Organizations), Locations, Grades and Salaries, Absences (workerAbsenceEntries). 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 Nutshell and Oracle Fusion Cloud HCM: One directory of people; Where Oracle Fusion Cloud HCM tracks people the business also engages: contacts stay in sync; New team members provisioned when they are hired. A person's name, title, email, phone, or manager corrected in either system updates the other, so both stop maintaining separate copies of the same individual.
Nutshell: JSON-RPC API over HTTPS; a newer REST API is also offered. Authentication: HTTP Basic with account email and API key. Oracle Fusion Cloud HCM: REST API (/hcmRestApi/resources), Atom feeds, and HCM Data Loader (HDL) for bulk. Authentication: OAuth 2.0 bearer tokens via Oracle Identity Cloud Service (IDCS/IAM); HTTP Basic and SAML/JWT bearer over SSL are also accepted, enforced by Oracle Web Services Manager (OWSM). Stacksync manages authentication, retries, and rate limits on both sides.
Nutshell: Nutshell's most full-featured API is JSON-RPC: each call names a method such as findLeads or editLead instead of hitting resource URLs, though a newer REST API is also available. Oracle Fusion Cloud HCM: Transactional REST is not optimized for mass loads; initial workforce loads and mass corrections should use HCM Data Loader (HDL), with REST reserved for incremental lookups and updates. Stacksync's field mapping accounts for these differences between Nutshell and Oracle Fusion Cloud HCM without custom code.
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 419 integrations available for Nutshell and Oracle Fusion Cloud HCM.