Skip to content
CRM ⇄ Human resources

Close to Oracle Fusion Cloud HCM integration — real-time, two-way sync

Keep Close 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.

  • 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 Close and Oracle Fusion Cloud HCM

Keep the people who own accounts in Close in step with the workforce records in Oracle Fusion Cloud HCM, so ownership, roles, and org structure stay current in both systems, in real time and in both directions.

Close 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 Tasks, Custom Activities, Custom Fields, Users in Close with Assignments, Jobs, Positions, Departments (Organizations) 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 Close keeps ownership and territory current, and Stacksync resolves conflicts by the rules you set.

Common use cases

  • 01 Keep Close contacts aligned with a marketing automation platform so outreach lists stay current.
  • 02 Push call, SMS, and email activity data into a warehouse for rep performance and outreach-cadence analysis.
  • 03 Provision identities and app access downstream when an Atom new-hire or termination feed event fires, joining Workers, Assignments, Departments, and Locations.
  • 04 Replicate Grades and Salaries into a warehouse for compensation and headcount analytics without exporting HDL files.

Common sync patterns

Where Oracle Fusion Cloud HCM tracks people the business also engages: contacts stay in sync

A person recorded in Oracle Fusion Cloud HCM, such as a candidate or applicant, can create or update the matching contact in Close, so relationship history and outreach are not rebuilt from scratch when the same individual appears in both.

New team members provisioned when they are hired

When Oracle Fusion Cloud HCM records a new hire, a matching user or owner is created in Close, so a new rep can start working accounts without waiting on a manual setup ticket.

Ownership and territory follow the org chart

When a person changes team, manager, or region in Oracle Fusion Cloud HCM, their accounts and territory assignments in Close update to match, so pipeline stays with the right owner.

What you can sync between Close and Oracle Fusion Cloud HCM

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.

Close objects Oracle Fusion Cloud HCM objects How this pairing syncs
Contacts People nested under a lead, with emails and phone numbers used for outreach syncs. Grades and Salaries Grade, grade-rate, and worker compensation records; usually read out for compensation and headcount analytics, and written back for corrections. Contacts is specific to Close and Grades and Salaries to Oracle Fusion Cloud HCM — each maps to any object or custom field on the other side.
Opportunities Deal records with value, confidence, and status; commonly synced to reporting and billing systems. Absences (workerAbsenceEntries) Time-off and leave entries; synced into scheduling or workforce-management databases for coverage planning. Opportunities is specific to Close and Absences (workerAbsenceEntries) to Oracle Fusion Cloud HCM — each maps to any object or custom field on the other side.
Activities Calls, emails, SMS, notes, and meetings logged against a lead; the source for engagement analytics. 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. Activities is specific to Close and Workers (publicWorkers) to Oracle Fusion Cloud HCM — each maps to any object or custom field on the other side.
Tasks Follow-up items assigned to users; synced for workload and SLA reporting. 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. Tasks is specific to Close and Assignments to Oracle Fusion Cloud HCM — each maps to any object or custom field on the other side.
Custom Activities User-defined activity types with their own custom fields, mapped like standard activities. Jobs Job catalog reference data; commonly read out to align titles and job codes in a warehouse or written to keep downstream systems consistent. Custom Activities is specific to Close and Jobs to Oracle Fusion Cloud HCM — each maps to any object or custom field on the other side.
Custom Fields Org-specific fields on leads, contacts, and opportunities; addressed by stable field ids in syncs. Positions Position-management records used where positions control headcount; synced to keep vacancy and reporting structures aligned with finance/ERP. Custom Fields is specific to Close and Positions to Oracle Fusion Cloud HCM — each maps to any object or custom field on the other side.

How changes propagate between Close and Oracle Fusion Cloud HCM

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.

Close Oracle Fusion Cloud HCM Sub-second propagation

DetectionClose notifies Stacksync of record changes through webhook events. Webhook subscriptions for record events, with polling on date_updated fields for backfills.

DeliveryEach detected change is written to Oracle Fusion Cloud HCM through its API, with automatic retries and rate-limit backoff.

Oracle Fusion Cloud HCM Close Sub-second propagation

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 Close through its API, with automatic retries and rate-limit backoff.

Rate-limit considerations

  • Close: Subject to per-endpoint rate limits communicated in response headers.
  • Oracle Fusion Cloud HCM: Oracle publishes no fixed per-tenant REST rate limit; pages are capped via limit/offset and Oracle recommends client-side throttling, backoff, and using HDL for mass loads rather than transactional REST.
What ships with Close ⇄ Oracle Fusion Cloud HCM

Connect Close and Oracle Fusion Cloud HCM for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Close–Oracle Fusion Cloud HCM connection.

Real-time

Two-way sync

Changes in Close or Oracle Fusion Cloud HCM instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Close or Oracle Fusion Cloud HCM 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 Close or Oracle Fusion Cloud HCM record.

Observability

Monitoring

Track your Close ⇄ Oracle Fusion Cloud HCM sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Close and Oracle Fusion Cloud HCM.

How the Close and Oracle Fusion Cloud HCM connectors work

Close

Integration surface
REST API
Authentication
API key (sent via HTTP Basic auth)
Change detection
Webhook subscriptions for record events, with polling on date_updated fields for backfills
Capabilities
read · write · webhooks
Rate limits
Subject to per-endpoint rate limits communicated in response headers

Oracle Fusion Cloud HCM

Integration surface
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)
Change detection
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
Capabilities
read · write · CDC
Rate limits
Oracle publishes no fixed per-tenant REST rate limit; pages are capped via limit/offset and Oracle recommends client-side throttling, backoff, and using HDL for mass loads rather than transactional REST.
How it works

How to connect Close to Oracle Fusion Cloud HCM — 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.

  1. 01

    Connect your apps

    Authenticate Close 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.

    • OAuth 2.0
    • SSH tunnel
    • VPC peering
    Close connected
    Oracle Fusion Cloud HCM connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Close 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.

    • Standard objects
    • Custom objects
    • Auto-schema
    objects · Close ⇄ Oracle Fusion Cloud HCM
    Customers 12,480
    Sales Orders 8,213
    Invoices 5,902
    Items 1,344
  3. 03

    Map fields

    Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.

    • Auto-map
    • Type casting
    • Transforms
    Close Oracle Fusion Cloud HCM
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

Close and Oracle Fusion Cloud HCM integration FAQ

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.

Learn more about security
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:

OAuth 2 SSH Tunnelling SSL certificates IP Whitelisting VPN gateway VPC peering and more

Related integrations

Every pair below is a real-time, two-way sync. Search all 528 integrations available for Close and Oracle Fusion Cloud HCM.

Popular · 8 of 528
All Close integrations All Oracle Fusion Cloud HCM integrations Browse all integrations
Coworkers laughing in front of a laptop in a casual office setting

Your last integration took months.
Your next one takes a prompt.

Book a demo Tour the platform on your own