--- title: "Oracle Fusion Cloud HCM Integration" description: "Connect AI agents to Oracle Fusion Cloud HCM. Agents onboard workers, read worker assignments, sync active employees, search the person directory, and reach any other HCM REST resource through generic advanced actions." url: https://flowrunner.ai/integrations/oracle-fusion-cloud-hcm date_modified: 2026-08-01T02:40:32-07:00 --- # Oracle Fusion Cloud HCM [HR](https://flowrunner.ai/integrations/category/hr) Connect AI agents to Oracle Fusion Cloud HCM. Agents onboard workers, read worker assignments, sync active employees, search the person directory, and reach any other HCM REST resource through generic advanced actions. [Verified](https://flowrunner.ai/integrations/verified "What does verified mean?") · 9 actions · Basic auth · available [Oracle Fusion Cloud HCM website](https://oracle.com/) · [Platform Documentation](https://docs.oracle.com/en/cloud/saas/human-resources/25b/farws/index.html) · Capability data verified 2026-08-12 1. A candidate's hire completes in the applicant tracking system with a signed offer and a start date 2. The agent assembles the Fusion payload: names, hire date, and the work relationship establishing the person as an Employee for the correct legal employer 3. List Workers searches by name and person number patterns to confirm the person does not already exist, catching rehires and duplicates 4. The HR operations lead reviews the assembled worker record, legal employer, worker type, start date, against the offer before anything is written 5. Create Worker establishes the person and work relationship in Fusion 6. Get Worker confirms the assigned person number, which flows back to the ATS and downstream provisioning 7. IT and payroll receive the new person number and start date through their intake channels ## What This Integration Enables An HCM platform is the system of record for the most consequential data a company holds: who is employed, by which legal entity, in what job, reporting to whom, paid how. Fusion's REST surface is broad and deeply nested, which is exactly why it usually gets touched only by integration specialists. This connector changes who can build against it. FlowRunner agents onboard workers as complete person-plus-work-relationship records, read workers with expandable child resources, sync active employees through the flattened emps view, search the public directory, and reach every other HCM resource, grades, jobs, positions, departments, salaries, through generic advanced actions. The stance: HR systems earn their gravity. Reads should flow freely to the systems that need them; writes into the employment record should pass through the same review a paper personnel file would have. - Onboard hires from any ATS into Fusion as structured worker records - Read worker assignments, job, department, manager, salary context, for downstream automation - Sync active employees to warehouses, sheets, and provisioning systems on schedule - Serve people-finder and org-chart experiences from the non-sensitive public directory - Reach any Fusion HCM REST resource the dedicated operations do not cover ### Without FlowRunner **Onboarding as re-keying**: The data the candidate already gave the ATS gets typed into Fusion again by hand, with a new chance of error each time **HR data requests queue behind HRIS analysts**: Every downstream system that needs headcount, assignments, or org structure waits on an export from the one team with access **Directory questions answered by asking around**: Who someone's manager is, and which department owns a role, is tribal knowledge with a search problem ### With FlowRunner **ATS to Fusion in one governed pass**: Hires flow into Fusion as structured worker records, deduplicated first, reviewed by a person, keyed by the returned person number **HCM data as a governed feed**: Employees, assignments, and any Fusion resource stream to downstream systems on schedule through the connector's read operations **The org answers its own questions**: People-finder and org-chart flows read the public directory view, which exposes only non-sensitive attributes by design ## Use Case Scenarios ### Hire to system-of-record without the re-keying A hire completes in [Greenhouse](https://flowrunner.ai/integrations/greenhouse). The agent maps the candidate data into the Fusion structure, names, hire date, work relationship with the correct legal employer, runs the duplicate check through List Workers, and stages the record for HR review. On approval, Create Worker writes it, Get Worker confirms the person number, and the number posts to the IT provisioning channel in [Slack](https://flowrunner.ai/integrations/slack). Day-one readiness stops depending on whether someone got to the data entry. ### The headcount feed that finance stops asking for On the first of each month, the agent pulls List Employees, active employment relationships in the flattened self-service view, pages through the collection envelope, and writes headcount by department and location to [Google Sheets](https://flowrunner.ai/integrations/google-sheets). List Worker Assignments enriches the roll-up with job and grade detail for the roles finance tracks closely. The report that used to be an email chain between FP&A and HRIS becomes a scheduled flow with a timestamp. ### The people-finder bot built on the safe view An internal assistant answers "who owns procurement in the Austin office?" by querying List Public Workers, the directory view that exposes name, work email, work phone, manager, and department and nothing sensitive. For org-chart depth, the bot walks manager references across the same view. Because the connector reads the publicWorkers resource rather than the full worker record, the bot is useful by default and safe by construction: the data it can leak is the data the directory already publishes. ## Human-in-Loop Highlight Create Worker does not add a row to a database, it establishes a legal employment relationship: a person, a legal employer, a worker type, a hire date, the record that payroll, benefits, tax reporting, and access provisioning will all treat as truth. Written wrong, it cascades, a duplicate person means double provisioning and a compliance headache; a wrong legal employer means wrong tax jurisdiction; and unwinding an erroneous hire record in an HCM system is a project, not an undo. FlowRunner flows therefore stage every worker creation: the agent maps the ATS data, runs the duplicate search, and presents the complete record to the HR operations lead through a [human-in-the-loop](https://flowrunner.ai/concepts/human-in-the-loop) step, and only their approval releases the write. The generic Create Resource action, which can POST into any Fusion resource including salaries and assignments, sits behind the same gate with a stricter policy: named resources, reviewed payloads, no exceptions. Reads run on schedule all day. The employment record changes only when a person who understands employment law says go. Agent processes routinely Detects exception requiring judgment Clear match Continues automatically Ambiguous Routes to human via preferred channel Human decides Agent resumes with decision ## Agent Capabilities 9 actions ### Workers 4 - **Create Worker** Creates a new worker, person plus work relationship, with hire date, names, and the relationship establishing them as an Employee or Contingent Worker for a legal employer. A complex nested payload assembled through the Names, Work Relationships, and Extra Fields inputs. The write this page's human gate governs. - **Get Worker** Retrieves a single worker by PersonId, optionally expanding child resources, names, addresses, emails, phones, workRelationships, assignments, into the response. The confirmation step after onboarding and the detail call for HR workflows. - **List Workers** Retrieves a paginated list of workers of all types, employees, contingent workers, pending workers, non-workers, with raw Fusion q-queries, convenience filters on name and person number, and field selection. The duplicate check and the broad search. - **List Worker Assignments** Retrieves a worker's assignments: job, position, department, grade, location, manager, and salary context within a work relationship. The enrichment behind org and compensation-adjacent automations. ### Employees 1 - **List Employees** Retrieves paginated employee records from the emps resource, scoped to active employment relationships and flattened for self-service style reads. The workhorse for headcount syncs and reporting feeds. ### Directory 1 - **List Public Workers** Retrieves workers from the publicWorkers directory view, which exposes only non-sensitive, shareable attributes: name, work email, work phone, manager, department. The right surface for people-finder and org-chart flows. ### Advanced 3 - **List Resource** Generic list against any HCM REST collection under the Fusion resources path, for resources without a dedicated operation: grades, jobs, positions, departments, locations, salaries. Takes the exact resource name and standard Fusion query parameters. - **Get Resource** Generic get-by-id against any HCM REST resource. Takes the exact resource name and the record's primary key. - **Create Resource** Generic POST against any HCM REST resource, with the full request body supplied. Powerful and gated accordingly: in FlowRunner flows this action runs only with reviewed payloads against named resources. ## Frequently Asked Questions ### What can FlowRunner do with Oracle Fusion Cloud HCM? FlowRunner agents can run List Workers, Get Worker, and Create Worker in Oracle Fusion Cloud HCM, plus 6 more actions. ### Does connecting Oracle Fusion Cloud HCM to FlowRunner require OAuth? No. Oracle Fusion Cloud HCM connects to FlowRunner with basic authentication (a username and password), no OAuth flow required. ### Can Oracle Fusion Cloud HCM trigger a FlowRunner workflow automatically? Oracle Fusion Cloud HCM doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger. **Work at Oracle Fusion Cloud HCM?** This integration exposes Oracle Fusion Cloud HCM to AI agents on every FlowRunner plan, including through MCP, at no cost to you. [See what FlowRunner offers integration partners](https://flowrunner.ai/integrations/partners), including how to keep this page current. --- Markdown version of https://flowrunner.ai/integrations/oracle-fusion-cloud-hcm. Site index: https://flowrunner.ai/llms.txt