Resources · Make integration

Oracle Fusion Cloud Sales Make integrationAutomate Oracle Fusion Cloud Sales with Make.

Can your CRM records move on their own when something happens elsewhere? The Oracle Fusion Cloud Sales Make integration gives you 7 modules: 1 trigger, 5 actions and 1 search. This guide is for sales ops teams on the Enterprise plan, and it walks you from the connection to a working first scenario.

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

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

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Oracle Fusion Cloud Sales Make integration do?

It lets Make read and write records in your Oracle Fusion Cloud Sales instance without code. You build a scenario (the automation itself, a chain of modules) where each module is one brick: a trigger that spots new records, an action that creates, updates or deletes one, or a search that pulls a filtered list.

Enrich a record the moment it appears. Watch Records picks up each newly created record, then Get a Record loads its full details so the next module can pass them to a messaging or reporting app your team already uses.

Keep Oracle in sync with another tool. When a signed quote or a form entry lands in a different app, Search Records finds the matching entries by criteria and Update a Record writes the new status on each one. Create a Record covers the case where nothing matches yet.

Clean up on purpose. Delete a Record removes a record by its ID, which is handy for test data you pushed while building. Anything the six ready modules skip, Make an API Call can reach with the same connection.

Two limits to know first. The app is reserved to the Make Enterprise plan, and its only trigger is scheduled, so Make checks for new records on the scenario's clock instead of being called by Oracle. If you are weighing platforms, the n8n vs Make comparison lays out the differences, and the Make review covers the editor itself. For a hands-on start, see the Make training.

Connect

How do you connect Oracle Fusion Cloud Sales to Make?

  1. 01

    Open the connection window

    Add any Oracle Fusion Cloud Sales module to your scenario and click Create a connection. A connection is your Oracle account linked to Make once, then reused by every module of the app. You can give it a clear label in Connection name.

  2. 02

    Enter your server and login

    In Server Name, paste the URL of your Oracle Cloud service, shaped like servername.fa.us2.oraclecloud.com. Then fill Username and Password with an Oracle login whose permissions cover the records you want Make to reach.

  3. 03

    Pick the scope and save

    Under Scope, tick only the record types your scenario needs, then click Save. The link can take up to 5 minutes to go through, so keep the window open until Make confirms it worked.

First scenario

Your first scenario: update Oracle when another app reports a change

GoalWhen a deal is marked as signed in another app, Make finds the matching Oracle Fusion Cloud Sales records and updates them.

  1. 01

    Start from the other app

    On the Scenarios page, create a new scenario and click the +. Add the trigger of the app where the signature or form entry shows up. That module opens the flow and hands over one bundle per event.

  2. 02

    Find the matching records

    Click the + on the right, search for Oracle Fusion Cloud Sales and pick Search Records. Create the connection if needed, then map a value from the first module into the criteria so Make looks up the right entries.

  3. 03

    Write the update

    Add Update a Record next and map the record ID returned by the search. Fill the fields you want changed. Each record the search returns becomes its own bundle, so each one gets updated.

  4. 04

    Test with Run once

    Click Run once and trigger a real event in the other app. Read the bundles each module received, then check the record in Oracle changed the way you expected.

  5. 05

    Schedule and switch on

    Open the clock on the first module to set the schedule (every 15 minutes by default on a new scenario), then flip the scenario on. From here it runs without you touching it.

Triggers

What can start an Oracle Fusion Cloud Sales scenario?

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

Oracle Fusion Cloud Sales1Watch Records

Watch Records

Scheduled trigger

In Make“Triggers when records are created.”

You get each newly created record as its own bundle, ready for the modules that follow, so nobody has to export lists by hand to spot what was added.

How it fires
scheduled. Make checks the app on the scenario's schedule, which you set with the clock badge on this module; going by its description, it reacts to new records, not to edits.
When to use it
when a freshly created record should kick off a follow-up, such as loading its details with Get a Record or alerting a colleague in another app.
Watch out
the record type must be part of the Scope you ticked in the connection, otherwise the module has nothing to watch.
Modules

What can Make do in Oracle Fusion Cloud Sales?

Oracle Fusion Cloud Sales 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 Sales1

Create a Record

Action

In Make“Creates a new record.”

This puts a brand new record into Oracle from data another module collected, so an entry typed once elsewhere lands in the CRM without copy and paste.

When to use it
when the upstream data describes something Oracle does not hold yet, like a contact coming from a form.
Watch out
run Search Records first if the same person may already exist, or you will pile up duplicates.
Oracle Fusion Cloud Sales2

Delete a Record

Action

In Make“Deletes a record by its ID.”

Removing a record by its ID keeps the CRM tidy once an entry no longer belongs there, for example test data left over from building your scenario.

When to use it
after a search or a filter has already isolated exactly the record you mean to drop.
Watch out
the ID alone decides which record disappears, so test it on a throwaway record with Run once before switching the scenario on.
Oracle Fusion Cloud Sales3

Get a Record

Action

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

Hand it an ID and it returns the full details of that one record, which gives later modules every value they need to map.

When to use it
right after Watch Records or any step that only carries an ID, when you want the complete record before sending it on.
Watch out
it needs an exact ID; to look something up by a name or another value, reach for Search Records instead.
Oracle Fusion Cloud Sales4

Make an API Call

Action

In Make“Performs an arbitrary authorized API Call.”

Your way past the six ready modules: it calls any endpoint of the Oracle API with the connection you already set up, so there is no second login to manage.

When to use it
when the operation you need, or a record type, is not covered by Create, Update, Get, Search or Delete.
Watch out
you write the request yourself, so keep the Oracle API reference open and test each call with Run once.
Oracle Fusion Cloud Sales5

Update a Record

Action

In Make“Updates a record by its ID.”

Changes the values of an existing record identified by its ID, so a status or an owner stays current in Oracle when the news arrives from another tool.

When to use it
after Search Records or Get a Record has given you the ID of the record that needs the change.
Watch out
fill only the fields you mean to change and double check the mapping, since the ID decides which record gets overwritten.
Oracle Fusion Cloud Sales6

Search Records

Search

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

Pulls a list of records that match the criteria you set, which is how you find an entry when you know a value from it but not its ID.

When to use it
before an update or a create, to check what already exists in the CRM and grab the right IDs.
Watch out
the result can be zero, one or several bundles, and every module after it then runs once per bundle, which counts operations on your plan.
Need help

Need help automating Oracle Fusion Cloud Sales with Make?

A person reads every message.

FAQ

Oracle Fusion Cloud Sales and Make: common questions

01Is the Oracle Fusion Cloud Sales Make integration free?
No. Oracle Fusion Cloud Sales is an enterprise app in Make, and enterprise apps are reserved to the Enterprise plan. The Free plan still gives access to 3,000+ standard apps, with 2 active scenarios and a 15 minute minimum between scheduled runs, but this app is not among them. Make counts usage in operations, one execution of one module on one bundle, so a search that returns many records multiplies what follows it. Check the plan your company has before you start building, since no Oracle module will run outside Enterprise.
02What is needed to connect Oracle Fusion Cloud Sales to Make?
You need the URL of your Oracle Cloud service for the Server Name field, plus a username and password for that service. The account behind those credentials needs the permissions to reach the records you plan to use in Make. You also choose a Scope, meaning the record types the connection may read and write. Keep that list short: a wide Scope can trigger the data.collection is too big error. The connection can take up to 5 minutes to establish, so leave the window open until it succeeds.
03Does the Oracle Fusion Cloud Sales trigger in Make work in real time?
No. Watch Records is a scheduled trigger, marked with a clock badge in the editor. Make polls Oracle on the scenario's schedule, which is every 15 minutes by default on a new scenario, and paid plans allow an interval as short as 1 minute. Oracle does not call Make on its own through a webhook with this app. So a record created just after a check waits until the next run. If you need a faster reaction, shorten the schedule rather than expecting an instant push.
04What if an Oracle Fusion Cloud Sales module is missing in Make?
Use Make an API Call. It reaches any endpoint of the Oracle API with the connection you already created, so an operation the six ready modules skip is still within reach. You write the request yourself, so test it with Run once and read the bundle it returns before switching the scenario on. If the problem is a record type Make cannot see, the cause is usually the Scope of the connection: add that type there, or trim the list if you hit the data.collection is too big error.
05Should Oracle Fusion Cloud Sales be automated with Make or n8n?
It depends on where your team already builds. On Make, this app needs the Enterprise plan and offers 7 modules: one scheduled trigger, five actions and one search, plus Make an API Call for the rest. Many apps also have an n8n node, so check whether one exists for Oracle Fusion Cloud Sales before you decide. The practical criteria are the plan you have, the modules each side offers for your use case, and which tool your colleagues can maintain once the scenario is live.
Same platform

Other docs you might need on this stack.

Browse all integrations