Two-way sync
Changes in Oracle Fusion Cloud HCM or Tinybird instantly reflect in both systems. No stale data, no manual imports.
Keep Oracle Fusion Cloud HCM and Tinybird in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.
Workforce data is some of the most requested data in the warehouse and some of the most awkward to move: the record types are many, the fields carry sensitive personal information, the APIs are strict, and hand-built extract jobs go stale or break quietly. Whether Oracle Fusion Cloud HCM is the system of record for employees and payroll, for candidates and applications, or for learners and course completions, the reporting belongs in Tinybird next to everything else the company measures.
Stacksync syncs Grades and Salaries, Absences (workerAbsenceEntries), Workers (publicWorkers), Assignments from Oracle Fusion Cloud HCM into tables in Tinybird continuously, handling API limits and schema drift as they come. The connection is bi-directional, so values computed in Tinybird, such as headcount rollups, cost allocations, or attrition risk flags, can be written back to fields in Oracle Fusion Cloud HCM where the HR team acts on them. You configure which records and fields cross over, and in which direction, instead of maintaining pipeline code.
A continuously synced copy in Tinybird gives you a durable, queryable record of how Oracle Fusion Cloud HCM's records change over time, for headcount planning and audit questions.
Segments, rollups, or risk flags computed in Tinybird sync back onto the matching records in Oracle Fusion Cloud HCM, where the HR team sees them in the system they already use.
People and organization records from Oracle Fusion Cloud HCM arrive in Tinybird as queryable tables, current within seconds instead of a day behind, replacing hand-built extract jobs.
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 Fusion Cloud HCM objects | Tinybird objects | How this pairing syncs | |
|---|---|---|---|
| Absences (workerAbsenceEntries) Time-off and leave entries; synced into scheduling or workforce-management databases for coverage planning. | Tokens Scoped credentials that control read and append rights per resource. | Absences (workerAbsenceEntries) is specific to Oracle Fusion Cloud HCM and Tokens to Tinybird — each maps to any object or custom field on the other side. | |
| 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. | Data Sources ClickHouse-backed tables that receive ingested rows; the write target for syncs into Tinybird. | Workers (publicWorkers) is specific to Oracle Fusion Cloud HCM and Data Sources to Tinybird — each maps to any object or custom field on the other side. | |
| 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. | Pipes Chained SQL nodes that transform Data Sources into query-ready results. | Assignments is specific to Oracle Fusion Cloud HCM and Pipes to Tinybird — each maps to any object or custom field on the other side. | |
| Jobs Job catalog reference data; commonly read out to align titles and job codes in a warehouse or written to keep downstream systems consistent. | API Endpoints Published Pipe outputs exposed as parameterized HTTP queries; the main read surface. | Jobs is specific to Oracle Fusion Cloud HCM and API Endpoints to Tinybird — each maps to any object or custom field on the other side. | |
| Positions Position-management records used where positions control headcount; synced to keep vacancy and reporting structures aligned with finance/ERP. | Materialized Views Pipes materialized into new Data Sources for pre-aggregation at ingest time. | Positions is specific to Oracle Fusion Cloud HCM and Materialized Views to Tinybird — each maps to any object or custom field on the other side. | |
| Departments (Organizations) Org-structure records that define cost centers and reporting lines; typically mastered in HCM and read into other systems. | Workspaces Project boundary that scopes Data Sources, Pipes, and tokens for a sync. | Departments (Organizations) is specific to Oracle Fusion Cloud HCM and Workspaces to Tinybird — 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 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 applied to Tinybird as a row-level write, with types converted between the two schemas.
DetectionStacksync polls Tinybird for changes on an incremental schedule, reading only records changed since the previous pass. Append-oriented ingestion.
DeliveryEach detected change is written to Oracle Fusion Cloud HCM through its API, with automatic retries and rate-limit backoff.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Oracle Fusion Cloud HCM–Tinybird connection.
Changes in Oracle Fusion Cloud HCM or Tinybird instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Oracle Fusion Cloud HCM or Tinybird 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 Fusion Cloud HCM or Tinybird record.
Track your Oracle Fusion Cloud HCM ⇄ Tinybird sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Oracle Fusion Cloud HCM and Tinybird.
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 Fusion Cloud HCM and Tinybird 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 Fusion Cloud HCM and Tinybird 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 Fusion Cloud HCM and Tinybird: authenticate both systems, choose the objects to sync (such as Oracle Fusion Cloud HCM's Absences (workerAbsenceEntries) and Workers (publicWorkers)), map fields visually, and changes propagate both ways in milliseconds — no code required.
Change detection 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. On Tinybird: Append-oriented ingestion; reads are pulled by querying published endpoints, no outbound CDC. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
On the Tinybird side: Materialized Views, Workspaces, Tokens, Data Sources, plus custom fields where Tinybird exposes them. On the Oracle Fusion Cloud HCM side: Grades and Salaries, Absences (workerAbsenceEntries), Workers (publicWorkers), Assignments. 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 Oracle Fusion Cloud HCM and Tinybird: Queryable history for planning and audit; Write-back of computed values; HR data in the warehouse, minus the pipeline. A continuously synced copy in Tinybird gives you a durable, queryable record of how Oracle Fusion Cloud HCM's records change over time, for headcount planning and audit questions.
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). Tinybird: REST API (Events API for ingestion, published query endpoints) with a ClickHouse SQL dialect. Authentication: Scoped auth tokens. Stacksync manages authentication, retries, and rate limits on both sides.
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 430 integrations available for Oracle Fusion Cloud HCM and Tinybird.