Resources · Make integration

Oracle Eloqua Make integrationAutomate Oracle Eloqua with Make.

Can Make keep your Oracle Eloqua records and folders tidy without a line of code? The Oracle Eloqua Make integration offers 12 modules: 1 scheduled trigger, 9 actions and 2 searches. Below, marketing ops teams get the connection steps and a first scenario to build.

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

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Oracle Eloqua Make integration let you automate?

The Oracle Eloqua Make integration links your Eloqua account to Make so records and folders move without manual work. You build a scenario, the automation itself, out of modules: small bricks that each watch, search or change one thing in Eloqua or in another app.

New records land in Eloqua on their own. Put the first module of your form tool or spreadsheet at the head of the scenario, then add Create a Record. Every entry becomes an Eloqua record, and nobody has to import a file by hand.

The rest of your stack hears about new records. Watch Records picks up records created in Eloqua and hands each one to the next module, so a sales channel, a sheet or a CRM gets the news without anyone copying it.

Campaign folders stay organized. Search Folders tells you what already exists, Create a Folder adds the missing one, and Update a Folder fixes a name that drifted. Folder housekeeping stops depending on memory.

Know the limits before you start. The app is available on the Make Enterprise plan only, and its single trigger is scheduled: it reports created records, not edited ones. When a listed module falls short, Make an API Call reaches the rest of the Eloqua API with the same connection. If you are weighing Make against another tool, the n8n vs Make comparison sets out the criteria, and the Make review covers the editor in depth. Stuck on a run that fails? Head to Make troubleshooting.

Connect

How do you connect Oracle Eloqua to Make?

  1. 01

    Open the connection window

    Log in to Make, add any Oracle Eloqua module to your scenario and click Create a connection. The Connection name field is optional; a clear name helps when several Eloqua accounts sit in the same Make organization.

  2. 02

    Enter your Eloqua sign-in details

    Type in Company Name the company name you use when you sign in to Eloqua. Then fill Username and Password with the same credentials you use on the Eloqua login page.

  3. 03

    Save and confirm access

    Click Save. If Eloqua asks you to authenticate, confirm access. The connection is now stored, and every other Oracle Eloqua module in your scenarios can reuse it without asking again.

First scenario

Your first scenario: push new leads into Oracle Eloqua

GoalWhen a new entry lands in another app, Make creates the matching record in Oracle Eloqua.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the +. This first slot holds the app where your leads start, a form tool or a spreadsheet for instance.

  2. 02

    Pick the source module

    Search that app by name, choose the module that returns new entries and link your account. Each entry it returns becomes a bundle: one item handed to the next module.

  3. 03

    Add Create a Record

    Click the + on the right, search Oracle Eloqua and pick Create a Record. Use the connection you set up earlier, then map the data from the source module into the Eloqua fields Make lists.

  4. 04

    Test with Run once

    Click Run once. Make runs the scenario a single time; open each module to read the bundles it received and check the new record in Eloqua before going further.

  5. 05

    Schedule and switch on

    Open the clock on the first module and set the schedule, every 15 minutes by default. Switch the scenario on. Each module run counts as one operation on your plan.

Triggers

What starts an Oracle Eloqua scenario?

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

Oracle Eloqua1Watch Records

Watch Records

Scheduled trigger

In MakeTriggers when records are created.

Watch Records gives your scenario a starting point inside Eloqua: each newly created record arrives as its own bundle, ready for the modules that follow. It is the only trigger of the app, so every Eloqua-first scenario begins here.

How it fires
scheduled. Make checks the app on the scenario's schedule, set on the clock of the first module, every 15 minutes by default.
When to use it
you want a sheet, a chat channel or another CRM to learn about each record your team adds in Eloqua.
Watch out
it reacts to created records only. An edit to an existing record will not start the scenario.
Modules

What can each Oracle Eloqua module do?

Oracle Eloqua gives you 11 modules in 3 groups. For each one: what it does for you, when to reach for it, and what to watch out for.

Records

5 modules
Oracle Eloqua1

Search Records

Search

In MakeRetrieves a list of records filtered by criteria.

Search Records finds the Eloqua records that match your criteria and returns them as bundles, so later modules can act on each match.

When to use it
before an update, when you know some details of a record but not its ID, and need the record itself.
Watch out
a search can return zero, one or many bundles; plan for the empty case and for duplicates.
Oracle Eloqua2

Create a Record

Action

In MakeCreates a new record.

With Create a Record, a new Eloqua record appears from data mapped out of an earlier module, a form entry or a spreadsheet row.

When to use it
leads collected outside Eloqua need to reach it without a manual import.
Watch out
it creates every time it runs. Put Search Records in front if the same person may come back twice.
Oracle Eloqua3

Get a Record

Action

In MakeRetrieves the details of a record by its ID.

Get a Record pulls the full details of one record when you already hold its ID, so the next modules can read every value it carries.

When to use it
an earlier step passed along a record ID, and you need the rest of the record to fill a message or a report.
Watch out
no ID, no result; this module does not search by name.
Oracle Eloqua4

Update a Record

Action

In MakeUpdates a record by its ID.

Update a Record changes values on an existing Eloqua record, targeted by its ID, and leaves the record itself in place.

When to use it
a status changed in your CRM or billing tool and Eloqua should reflect it for the next campaign.
Watch out
it needs the ID. Chain it after Search Records or Watch Records so the ID is mapped, not typed.
Oracle Eloqua5

Delete a Record

Action

In MakeDeletes a record by its ID.

Delete a Record removes one record from Eloqua by its ID, which keeps test entries or withdrawn leads out of your lists.

When to use it
a cleanup scenario where another app confirms the record must go.
Watch out
treat the deletion as final. Run the scenario on a throwaway record first, and double check which ID you mapped.

Folders

5 modules
Oracle Eloqua6

Search Folders

Search

In MakeRetrieves a list of folders.

Search Folders lists the folders of your Eloqua account and returns each one as a bundle you can map downstream.

When to use it
you need to know whether a campaign folder already exists before creating or renaming one.
Watch out
the list may hold many folders; each bundle it returns can run the next modules once, and each run uses operations.
Oracle Eloqua7

Create a Folder

Action

In MakeCreates a new folder.

Create a Folder adds a new folder in Eloqua, which gives a fresh campaign or a new client its own place from the start.

When to use it
a project card appears in your planning tool and the matching Eloqua folder should follow.
Watch out
nothing stops a second folder with the same purpose; check with Search Folders first.
Oracle Eloqua8

Get a Folder

Action

In MakeRetrieves an existing folder.

Get a Folder reads one existing folder and passes its details on, so the next steps work from the folder as it is today, not from an old copy.

When to use it
you stored a folder reference elsewhere and want its current state before acting on it.
Watch out
it reads one folder; to browse the whole tree, Search Folders is the right pick.
Oracle Eloqua9

Update a Folder

Action

In MakeUpdates an existing folder.

Update a Folder edits an existing Eloqua folder, so a naming rule applied elsewhere can reach Eloqua too.

When to use it
a campaign gets renamed in your planning tool and the Eloqua folder should carry the same name.
Watch out
map the folder from Search Folders or Get a Folder rather than picking it by hand, or the scenario always edits the same one.
Oracle Eloqua10

Delete a Folder

Action

In MakeDeletes an existing folder.

Delete a Folder removes an existing folder from Eloqua and clears space once a campaign is archived for good.

When to use it
a closing step in a cleanup scenario, after another app marks the project as finished.
Watch out
deletion cannot be walked back from Make. Test it on an empty test folder before switching the scenario on.

Other

1 module
Oracle Eloqua11

Make an API Call

Action

In MakePerforms an arbitrary authorized API Call.

Make an API Call lets your scenario ask Eloqua for anything its API offers, even what no listed module covers, reusing the connection you already created.

When to use it
the 11 listed modules stop short, for instance when you need an Eloqua object beyond records and folders.
Watch out
you write the request yourself, so keep the Eloqua API documentation open and test with Run once.
Need help

Need help automating Oracle Eloqua with Make?

A person reads every message.

FAQ

Oracle Eloqua and Make: common questions

01Is the Oracle Eloqua Make integration free?
No. The Oracle Eloqua app is reserved for the Make Enterprise plan, so the Free plan does not include it. The Free plan does cover more than 3,000 standard apps, with 2 active scenarios, a 15 minute minimum interval between scheduled runs and 5 minutes of execution at most. Paid plans are Core, Pro, Teams and Enterprise, and usage is counted in operations per month. Check with whoever manages your Make subscription that the organization runs on Enterprise before you start building.
02What do you need to connect Oracle Eloqua to Make?
You need an Oracle Eloqua account and a Make organization on the Enterprise plan. The documentation lists no other prerequisite. In the connection window, you enter the company name you use to sign in to Eloqua, your Eloqua username and your password, then click Save. Eloqua may ask you to authenticate and confirm access. The connection is stored once and reused by every Oracle Eloqua module, so later scenarios skip this step entirely.
03Is the Oracle Eloqua trigger in Make instant or scheduled?
Scheduled. Watch Records has no webhook: Make checks Eloqua on the schedule you set on the first module, every 15 minutes by default. Paid plans allow a minimum interval of 1 minute. The trigger only reports records that were created, so an edit to an existing record does not start the scenario. If the start of your flow is another app, put that app's module first and use the Eloqua modules as actions further down the chain.
04What if an Oracle Eloqua module is missing in Make?
Use Make an API Call. It calls any endpoint of the Eloqua API from the scenario, with the connection you already set up, so you reach what the 11 listed modules do not cover. The listed modules focus on records and folders: search, create, read, update and delete. For anything else, the API call is the route. Write the request, test it with Run once, and read the returned bundle before mapping its values into the next modules.
05Should you use Make or n8n for Oracle Eloqua?
It depends on what you need. In Make, Oracle Eloqua comes with 12 modules covering records and folders, a scheduled trigger and Make an API Call for the rest, but only on the Enterprise plan. Many apps also have an n8n node; check whether one exists for Eloqua and what it covers before choosing. Compare the modules each tool offers for your use case and the plan you already pay for, then build where both line up.