Resources · Make integration

Oracle Fusion Cloud HCM Make integrationAutomate Oracle Fusion Cloud HCM with Make.

Can Make read and write your HR records in Oracle Fusion Cloud HCM without a line of code? Yes: the Oracle Fusion Cloud HCM Make integration offers 7 modules, one trigger and six actions or searches. This page shows HR and ops teams how to connect the account and ship a first working scenario.

Enterprise app This app is reserved to Make's Enterprise plan.

Try the Oracle Fusion Cloud HCM integration on MakeSee the 7 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Oracle Fusion Cloud HCM Make integration do for you?

The Oracle Fusion Cloud HCM Make integration links your Oracle Cloud service to Make, so records can be watched, looked up, created, changed or removed from a scenario (the automation you build in Make, one module after another). You pick the record types once, and every module works on them without any code on your side.

Spot new records as they land. Watch Records starts a scenario whenever a record is created, and Get a Record pulls its full details so the next app in the chain gets every value it needs.

Keep HCM aligned with another source. When a change arrives from a form or a spreadsheet, Search Records finds the matching entry and Update a Record writes the new values. Create a Record covers the case where nothing matches yet.

Clear out what should not stay. Delete a Record removes an entry by its ID, which suits cleanup flows that you have already reviewed by hand.

One limit to know upfront: this app is only available on the Make Enterprise plan, so a Free or Core account cannot use it. Anything the six listed modules skip can still be reached through Make an API Call, with the same connection. The same app often has an n8n node too; the n8n vs Make comparison helps you pick, and the Make pricing page explains the plans. If you prefer help, our Make agency builds these flows with HR teams.

Connect

How do you connect Oracle Fusion Cloud HCM to Make?

  1. 01

    Open the connection window

    In your scenario, add any Oracle Fusion Cloud HCM module and click Create a connection. A connection is your Oracle account linked to Make once, then reused by every module of the app. The Connection name field is optional, and a clear name makes the connection easy to find later.

  2. 02

    Enter your server and login

    In Server Name, paste the URL of your Oracle Cloud service, in the shape servername.fa.us2.oraclecloud.com. Then fill Username and Password with an Oracle login that already has permission to reach the records you plan to automate.

  3. 03

    Pick the scope and save

    Under Scope, tick the record types the scenario really needs, then click Save. Keep the window open: the doc warns that the link can take up to 5 minutes before it reports success, so closing it early leaves you with nothing.

First scenario

Your first scenario with Oracle Fusion Cloud HCM

GoalWhen a row changes in another app, Make finds the matching record in Oracle Fusion Cloud HCM and updates it.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the +. Pick the app that holds the changes, for example the spreadsheet or form your HR team already fills in.

  2. 02

    Add Search Records

    Click the + to the right of that first module, search for Oracle Fusion Cloud HCM and choose Search Records. Click Create a connection and follow the three steps above.

  3. 03

    Map the search criteria

    Once connected, Make lists the record types it can read. Choose one, then map a value from the first module as the filter, so each incoming row looks up its own record.

  4. 04

    Add Update a Record

    Add Update a Record after the search. Map the ID returned by Search Records, then map the values you want to change from the first module.

  5. 05

    Test with Run once

    Click Run once. Open each module bubble and read the bundles it received: if the search returned several records, the update ran on each one, which tells you to tighten the filter.

  6. 06

    Schedule and switch on

    Click the clock on the first module to set the schedule, every 15 minutes by default, then switch the scenario on. From now on it runs by itself.

Triggers

The trigger that starts your scenarios

1 module starts a scenario when something happens in Oracle Fusion Cloud HCM. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Oracle Fusion Cloud HCM as soon as it happens.

Oracle Fusion Cloud HCM1Watch Records

Watch Records

Scheduled trigger

In Make“Triggers when records are created.”

Watch Records hands your scenario each record newly created in Oracle Fusion Cloud HCM, one bundle at a time (a bundle is one item passed from module to module). It is the only way this app can open a scenario on its own.

How it fires
scheduled, Make checks the app on the scenario's schedule. It is not real time: a record created just after a check waits for the next one.
When to use it
a new record should set off work elsewhere, such as notifying a manager or copying the entry to another tool.
Watch out
the module reacts to creations only. An edit to an existing record will not start the scenario.
Modules

Every Oracle Fusion Cloud HCM module, explained

Oracle Fusion Cloud HCM gives you 6 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Oracle Fusion Cloud HCM1

Create a Record

Action

In Make“Creates a new record.”

Create a Record adds a fresh entry to Oracle Fusion Cloud HCM from data that arrives in the scenario, so nobody has to retype it in the HR system.

When to use it
after a search came back empty, to add the entry that is missing instead of updating one that does not exist.
Watch out
only record types ticked in the connection's Scope show up here.
Oracle Fusion Cloud HCM2

Delete a Record

Action

In Make“Deletes a record by its ID.”

Delete a Record removes one entry, identified by its ID, straight from a scenario. You get a cleanup step that runs without anyone opening the HCM console.

When to use it
at the end of a flow where the IDs to drop have already been checked, for instance a list validated by a person.
Watch out
treat every deletion as final and try it on a test record first with Run once.
Oracle Fusion Cloud HCM3

Get a Record

Action

In Make“Retrieves the details of a record by its ID.”

Get a Record fetches the complete details of one entry when you already hold its ID, giving the next modules every value to map.

When to use it
right after Watch Records or a search, when you hold an ID and the next modules need the rest of the record.
Watch out
without a valid ID it has nothing to fetch; map the ID from an earlier module rather than typing it.
Oracle Fusion Cloud HCM4

Make an API Call

Action

In Make“Performs an arbitrary authorized API Call.”

Make an API Call lets you reach any endpoint of the Oracle Fusion Cloud HCM API from the scenario, reusing the connection you already set up. It covers everything the five other actions and the search leave aside.

When to use it
the job you need is not one of the listed modules.
Watch out
you describe the request yourself, so keep the Oracle API documentation open to find the right endpoint.
Oracle Fusion Cloud HCM5

Update a Record

Action

In Make“Updates a record by its ID.”

Update a Record changes the values of an existing entry, found by its ID, so HCM follows what happens in your other tools without manual edits.

When to use it
paired with Search Records, when a form or sheet says something changed and the matching record must reflect it.
Watch out
feed it one ID per run. If the search upstream found several records, each one gets updated.
Oracle Fusion Cloud HCM6

Search Records

Search

In Make“Retrieves a list of records filtered by criteria.”

Search Records returns the entries that match your criteria, which is how a scenario finds the right record when it does not know the ID yet.

When to use it
before an update or a deletion, to turn a value from another app into the record it refers to.
Watch out
the result can be zero, one or several bundles, and every following module runs once per bundle, each run counting as an operation on your plan.
Need help

Need help automating Oracle Fusion Cloud HCM with Make?

A person reads every message.

FAQ

Questions people ask next

01Is the Oracle Fusion Cloud HCM Make integration free?
No. Make lists Oracle Fusion Cloud HCM as an enterprise app, and enterprise apps are reserved to the Enterprise plan. The Free plan still gives you 2 active scenarios, a 15 minute minimum between scheduled runs and access to 3,000+ standard apps, which is enough to learn the editor with other tools. To run the modules on this page, though, your organization needs an Enterprise account. No price is quoted here, for Make or for Oracle, because there is no verified figure to cite.
02What do you need to connect Oracle Fusion Cloud HCM to Make?
Three things: the URL of your Oracle Cloud service for the Server Name field, an Oracle username and password, and a Make account on the Enterprise plan. The Oracle login must already have permission to access the records you want Make to handle, otherwise Make cannot reach them. You also choose a Scope, meaning the record types the connection covers. Keep that list short, because a very wide Scope triggers the data.collection is too big error on save.
03Does the Oracle Fusion Cloud HCM trigger work in real time?
No. Watch Records is a scheduled trigger: Make polls Oracle Fusion Cloud HCM on the scenario's schedule instead of being called by the app through a webhook. A new scenario checks every 15 minutes by default. Paid plans, Enterprise included, let you lower the interval to 1 minute, which gets close to live without being instant. Also note that the trigger fires on created records only, so changes to existing entries need a different starting point, such as a schedule followed by Search Records.
04What if the Oracle Fusion Cloud HCM module you need is missing?
Use Make an API Call. It sends a request to any endpoint of the Oracle Fusion Cloud HCM API with the connection you already have, so nothing new to authorize. The Oracle API documentation lists the available endpoints. If the problem is rather the data.collection is too big error, the fix is on the connection side: narrow its Scope to the specific record types your scenario actually uses, then save again. Waiting is sometimes the answer too, since a connection can take up to 5 minutes.
05Should you use Make or n8n for Oracle Fusion Cloud HCM?
It depends on where your team already works. On Make, this app needs the Enterprise plan, so the question often comes down to whether your company has that account. Many apps also exist as an n8n node, so check whether one covers the records you need before deciding. Then compare on your own criteria: who will maintain the flows, which other tools sit in the chain, and how comfortable the team is with each editor. Neither tool is better by default here.
Same platform

Other docs you might need on this stack.

Browse all integrations