Resources · Zapier integration

Oracle Eloqua Zapier integrationAutomate Oracle Eloqua with Zapier.

The Oracle Eloqua Zapier integration offers 8 triggers, 10 actions and 4 searches. Every trigger is checked on a timer, and Eloqua is reserved to paid plans. Here is what each operation does for your marketing database, what it bills, and where it tends to break.

Premium app Zapier reserves this app to its paid plans.

See the 22 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Oracle Eloqua Zapier integration does for a marketing team

The Oracle Eloqua Zapier integration connects your Eloqua database to the other tools your team uses, without code. A contact, an account, a record or a custom object entry appears or changes in Eloqua, and Zapier reacts by writing into Eloqua or into another app. Eloqua is Oracle's cloud platform for running marketing campaigns, and this connector works on its data, not on its emails.

Three results justify most setups. First, a contact base that stays in sync: New Contact and Updated Contact push every change to a sheet, a CRM or a chat channel, and Create Contact brings people in from a form or an event tool. Second, accounts kept up to date from outside: Find Account locates the company and Update Account writes the new information into it. Third, custom objects fed automatically: Create Custom Object Data and Update Custom Object Data log registrations, purchases or any data model you built in Eloqua.

What it does not do matters as much. None of the visible operations sends an email, launches a campaign or reads campaign results; the connector stops at contacts, accounts, records and custom objects. No trigger is instant either, so nothing starts the moment a contact changes: Zapier checks at your plan's interval. Anything outside the list goes through API Request (Beta), an advanced action for people comfortable with Eloqua's own documentation.

Neither Make nor n8n has an Eloqua page on this site yet. For criteria across platforms, see Make vs Zapier, and for the tool itself, the Zapier review.

Vocabulary

The Zapier vocabulary, in plain English

Seven words carry this whole page. Here they are once, without jargon.

Zap
The automation you build on Zapier: one trigger, then one or more actions that run each time that trigger event happens.
Trigger
The event in an app that starts the Zap. Once the Zap is on, Zapier waits for that event and ignores the rest.
Action
What the Zap does after it starts: the step that writes, sends or moves something for you, in Eloqua or in another app.
Task
The unit Zapier bills: one action your Zap completes successfully. Your plan gives you a monthly count of those.
Polling vs instant
Zapier checks a polling trigger on a timer and keeps only what is new. An instant trigger is reported by the app itself.
Filter
A step that lets the Zap go on only when the incoming item meets the condition you set, and stops it otherwise.
Search step
A step that looks up something already stored in an app, so the steps after it can reuse what it found, like an ID.
Cost

What an Eloqua Zap really costs

Oracle Eloqua is a premium app on Zapier: it is reserved to paid plans and to the free trial, so the free plan is not an option here.

  • Plan requiredPaid plan or free trial
  • Trigger and checksNever billed
  • Each successful action1 task
  • Eloqua triggers8 polling, 0 instant

Inside a paid plan, the trigger never costs a task, and the checks Zapier runs on Eloqua cost nothing either, however often they happen. Each action that succeeds is one task; one that fails is not counted. A Zap with three successful actions uses three times more than a single-action Zap. A filter or a search step makes the Zap multi-step, which paid plans allow. All eight triggers are polling ones, so the grid below sets how quickly a change in Eloqua reaches your Zap.

Connect

Connect Oracle Eloqua to Zapier in three steps

  1. 01

    Open your connections

    In Zapier, open the Apps page of your account and click + Add connection. A connection is your Eloqua account linked once, then reused by every step that works with Eloqua.

  2. 02

    Choose Oracle Eloqua

    Search for Oracle Eloqua in the dialog, select it and click Add connection. A tab opens on the Eloqua side, where you sign in with the account that holds your marketing database.

  3. 03

    Grant access

    Sign in to Eloqua in that tab and grant Zapier access. You need an Eloqua account, plus read or write rights on any data you do not own yourself but want the Zap to read or change.

First Zap

Your first Eloqua Zap: log qualified contact updates in a custom object

GoalWhen a contact changes in Eloqua, keep only the ones that meet your condition and log them as custom object data.

  1. 01

    Pick the trigger

    Start a new Zap, choose Oracle Eloqua and the Updated Contact event, then select your Eloqua connection. This is a polling trigger, so changes arrive at your plan's interval.

  2. 02

    Test the trigger

    Run the test. Zapier brings back the three most recent items from your account, so you set up the next steps on a real contact rather than on a guess.

  3. 03

    Add the filter

    Add a Filter step from the plus icon. Pick the field to look at, the rule and the value, then Configure & test. Choose a text rule for text and a number rule for numbers.

  4. 04

    Add the action

    Add Create Custom Object Data, pick the Custom Object Type and map the Name from the contact. Run the step test and read what Eloqua sent back.

  5. 05

    Publish

    Click Publish to switch the Zap on. With a filter it is a multi-step Zap, which your paid plan covers. Only contacts updated after publishing will go through.

Triggers

Oracle Eloqua triggers: eight events Zapier checks for

8 events start a Zap when something happens in Oracle Eloqua. Zapier checks for them at the interval your plan allows.

1

New Account

Polling trigger

In Zapier“Triggers when a new account is created in Oracle Eloqua.”

Watches Eloqua for companies that did not exist on the last check. Each new account becomes the starting point of a Zap, so the sales side of the house hears about it without exporting a list.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your paid plan: every 2 minutes on Professional, every minute on Team and Enterprise.
When to use it
an account-based marketing team wants each new target company posted to the channel where account executives pick up leads.
Watch out
it only sees accounts created after the Zap is published; the ones already in Eloqua stay out.
2

New Contact

Polling trigger

In Zapier“Triggers when a new contact is created in Oracle Eloqua.”

Every person added to your Eloqua database on or after publishing can start this Zap. It is the most common entry point of the connector, since most marketing flows begin with someone new.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your paid plan: every 2 minutes on Professional, every minute on Team and Enterprise.
When to use it
a webinar team wants every new contact copied into the attendee sheet that the host reads before going live.
Watch out
a bulk import can send a huge batch at once, which Zapier's flood protection may hold back.
3

New Custom Object Data

Polling trigger

In Zapier“Triggers when a new custom object data is created.”

Custom objects are the tables your team built in Eloqua beyond contacts and accounts. This trigger picks up each fresh entry in the type you choose, and nothing that only changed.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your paid plan: every 2 minutes on Professional, every minute on Team and Enterprise.
When to use it
event registrations are stored as a custom object, and each new one should reach the venue planner's spreadsheet.
Watch out
the Custom Object Type is required, so one Zap follows one type; a second type needs a second Zap.
4

New or Updated Custom Object Data

Polling trigger

In Zapier“Triggers when custom object data is created or updated.”

Broader than the previous one: it reacts to custom object entries that appear and to those that change. Use it when the later edits matter as much as the first version.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your paid plan: every 2 minutes on Professional, every minute on Team and Enterprise.
When to use it
a subscription record moves from trial to active, and finance needs both the creation and the change.
Watch out
pairing it with Update Custom Object Data on the same type makes the Zap restart on its own edits.
5

New or Updated Record

Polling trigger

In Zapier“Triggers when a record is created or updated.”

Covers records in both directions, fresh and edited. Unlike the contact and account triggers, its label does not name one object, so check in the editor which records your connection exposes before relying on it.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your paid plan: every 2 minutes on Professional, every minute on Team and Enterprise.
When to use it
an operations lead wants one Zap to mirror every new or edited record into a reporting sheet.
Watch out
an Update Record step aimed at the same records turns this Zap into a loop that burns tasks.
6

New Record

Polling trigger

In Zapier“Triggers when a new record is created.”

The creation-only counterpart of the trigger above. Edits are ignored, so the Zap runs once per record and stays easy to predict.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your paid plan: every 2 minutes on Professional, every minute on Team and Enterprise.
When to use it
a demand generation manager wants each new record announced once in the team chat, without repeats when someone corrects it later.
Watch out
test it first and look at the three recent items Zapier brings back, to confirm these are the records you expect.
7

Updated Account

Polling trigger

In Zapier“Triggers when an account is updated in Oracle Eloqua.”

Fires on changes to existing companies, not on new ones. When someone edits an account in Eloqua, the next check spots it and the Zap carries the new version onward.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your paid plan: every 2 minutes on Professional, every minute on Team and Enterprise.
When to use it
a partner manager wants account edits copied to the partner portal's tracking sheet so both sides read the same data.
Watch out
combined with Update Account on the same company, each write looks like a fresh change and the Zap starts again.
8

Updated Contact

Polling trigger

In Zapier“Triggers when a contact is updated in Oracle Eloqua.”

Tracks edits on people already in the database. A changed job title, a new phone number, a corrected spelling: any update to a contact can start the Zap on the following check.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your paid plan: every 2 minutes on Professional, every minute on Team and Enterprise.
When to use it
a sales development team needs contact changes reflected in its outreach tool before the next call.
Watch out
most edits are minor, so add a filter to keep only the ones that matter and spare your tasks.
Actions

Oracle Eloqua actions: what a Zap can write into Eloqua

Oracle Eloqua gives you 10 actions. For each one: what it does for you, when to reach for it, and what to watch out for.

1

Create Account

Action

In Zapier“Creates a new account.”

Opens a new company record in Eloqua. Useful when a deal or a partnership starts in another tool and marketing needs the company before the first campaign.

When to use it
a signed partner agreement in your contract tool creates the matching account.
Watch out
check with Find Account first, since this action does not look for an existing one.
2

Create Contact

Action

In Zapier“Creates a new contact.”

Adds a person to your Eloqua database from whatever happened upstream: a form, a booking, a scanned badge. Pick it when the person does not exist in Eloqua yet.

When to use it
every sign-up from a trade show app becomes an Eloqua contact the same day.
Watch out
run it behind Find Contact if the person may already exist, to avoid duplicates.
3

Create Custom Object Data

Action

In Zapier“Creates a new custom object data record.”

Writes a new entry into one of your custom objects. You pick the Custom Object Type and give the entry a Name, then map whatever else that type holds.

When to use it
each paid order from your shop is stored as a purchase entry for later segmentation.
Watch out
both the type and the Name are mandatory, and the type must already exist in Eloqua.
4

Delete Record

Action

In Zapier“Deletes a record by ID.”

Removes a record from Eloqua, designated by its ID. It is the only action of the set that deletes rather than writes.

When to use it
test entries created during a campaign dry run should vanish once the run is over.
Watch out
put a filter in front so the Zap deletes only what your condition allows.
5

Create Record

Action

In Zapier“Creates a new record.”

Creates a new record through the connector's generic record action, the write-side partner of New Record and Find Record.

When to use it
a form in another tool must leave a trace in Eloqua that is neither a contact nor an account.
Watch out
look at which fields the editor shows before mapping, since the label alone does not say which object it writes.
6

Update Account

Action

In Zapier“Updates an existing account.”

Edits a company already in Eloqua. The Account ID is required, so this action almost always follows a trigger or a search that carries it.

When to use it
a renewal closed in the billing tool updates the account before the next nurture wave.
Watch out
Find Account is the usual way to get the ID, which makes the Zap multi-step.
7

Update Contact

Action

In Zapier“Updates an existing contact.”

Changes an existing person in Eloqua. You identify the contact by its Contact ID or its Email Address, one of the two is enough, then map the new values.

When to use it
a lead qualified by sales gets its new status written back into Eloqua.
Watch out
without the ID or the email in an earlier step, add Find Contact first.
8

Update Custom Object Data

Action

In Zapier“Updates an existing custom object data record.”

Rewrites an existing custom object entry. It needs the Custom Object Type and the entry's ID, then takes the new values you map.

When to use it
a registration changes from pending to confirmed after payment in another app.
Watch out
get the ID from Find Custom Object Data or from the trigger, never type it by hand.
9

Update Record

Action

In Zapier“Updates an existing record.”

Modifies a record that already exists, pointed out by its Record ID. It closes the loop opened by Create Record and Find Record.

When to use it
a status changed elsewhere has to be reflected on the matching Eloqua record.
Watch out
do not aim it at the records a New or Updated Record trigger watches in the same Zap.
10

API Request (Beta)

Action

In Zapier“This is an advanced action which makes a raw HTTP request that includes this integration's authentication.”

An advanced action for what the list above does not cover. It sends a hand-built request to Eloqua using your connection's sign-in, so there is no separate login to manage.

When to use it
a technical marketer needs an Eloqua operation that has no ready-made step.
Watch out
the URL must belong to the domains tied to Eloqua, and Stop on error set to Yes halts the step when Eloqua returns an error.
Searches

Oracle Eloqua searches: finding contacts, accounts and records

4 search steps look for data that already exists in Oracle Eloqua, so a later step can use it.

Searches sit at the bottom of the action-event list, under the SEARCH heading. They read Eloqua and hand what they found, often an ID, to the steps that follow. Eloqua offers no find-or-create variant for any of them. Three settings decide what happens when the result is not the one you expected.

1

Find Contact

Search

In Zapier“Finds a contact based on name or id.”

Looks up a person in Eloqua. You choose whether to search by Contact ID or by Name, then type or map the term to look for.

When to use it
right before Update Contact, to fetch the ID of someone who just replied to a survey.
Watch out
a name can match several people, so set the multiple-results option on purpose.
2

Find Custom Object Data

Search

In Zapier“Finds a custom object data based on id orname.”

Retrieves an entry inside one custom object, by its ID or its name. The Custom Object Type is the one required field.

When to use it
a payment arrives and the Zap has to find the matching registration before updating it.
Watch out
it searches one type only, so the wrong type returns nothing even if the entry exists.
3

Find Record

Search

In Zapier“Finds a record based on name or id.”

Finds a generic record by name or by ID, and passes it to Update Record or Delete Record further down.

When to use it
cleaning up a record whose name you know from another tool but whose ID you do not.
Watch out
whether it needs the exact name or something close is decided by Eloqua, so test with a real one.
4

Find Account

Search

In Zapier“Searches for an account based on specific criteria.”

Locates a company in Eloqua. Search By lets you pick Account ID or Name, and Search Term holds the value to match.

When to use it
before Update Account, when the incoming deal only carries the company name.
Watch out
if nothing matches and the first setting is off, the Zap stops here and the update never runs.

The three settings every search exposes

  1. Successful if no search results are found?
    Left on its default, a search that finds nothing stops the Zap there and the steps that depended on it are skipped. Switched on, the Zap carries on empty-handed.
  2. Create X if it doesn't exist yet?
    On apps that support it, this box turns the search into a find-or-create. None of the four Eloqua searches offers that variant.
  3. If multiple search results are found?
    Three ways out when several items match: keep the first one, which is the default, stop the Zap, or hand all of them on at once.
When it breaks

When an Oracle Eloqua Zap breaks

Zapier links two help articles to Eloqua: How to get started with Oracle Eloqua on Zapier, and one on fixing address errors in custom actions. The rest is the general list, applied to a marketing database.

Six traps, all of them avoidable before publishing: two come from the advanced request step, four from how Zapier watches Eloqua. When a run fails anyway, the Zapier troubleshooting page is a sensible next step.

  • Existing contacts are never picked up

    A Zap only reacts to what happens after you switch it on. Contacts and accounts already in Eloqua are not processed; moving that backlog is a separate job.

  • Update triggers feed themselves

    Updated Contact followed by Update Contact on the same person makes each write look like a new change. The Zap restarts on its own output and burns tasks fast.

  • A list import gets held back

    A bulk import or a migration can make a trigger return a huge batch at once. Zapier's flood protection may hold it back instead of running every item.

  • The same contact never runs twice

    On a polling trigger, Zapier remembers what it has already seen. An item that started the Zap once will not start it again on a later check.

  • The advanced request refuses its address

    API Request (Beta) only accepts addresses on the domains tied to Eloqua. Zapier has a help article on fixing address errors in custom actions.

  • A failed request goes unnoticed

    With Stop on error set to No, the advanced step runs whatever Eloqua returns. Set it to Yes to halt the step on an error instead of passing it on.
Need help

Need help automating Oracle Eloqua with Zapier?

A person reads every message.

FAQ

Oracle Eloqua Zapier integration: common questions

01Is the Oracle Eloqua Zapier integration free?
No. Oracle Eloqua is a premium app on Zapier, which means it is reserved to paid plans and to the free trial. The free plan, with its 100 tasks a month and two-step Zaps, cannot use it at all. On a paid plan, the trigger and Zapier's checks cost nothing; only the actions that succeed are billed, one task each. The free trial is the way to build and test an Eloqua Zap before deciding on a plan.
02How many tasks does an Eloqua Zap use?
One task per action that succeeds, and nothing for the trigger. An action that fails is not counted against your plan. If a Zap creates a contact and then a custom object entry, a complete run costs two tasks. Zapier also notes that a few apps and actions take more than one task when they complete, so read the task count after the first real runs before scaling up. The checks Zapier runs on Eloqua to spot new items cost nothing, however often they happen.
03Does Oracle Eloqua trigger Zaps in real time?
No. All eight Eloqua triggers are polling triggers: Zapier asks Eloqua for new or changed items at a fixed interval. How often depends on your paid plan, every 2 minutes on Professional and every minute on Team and Enterprise. The 15-minute interval of the free plan never applies, since Eloqua is not available there. On paid plans you can also run a check by hand from the editor while testing.
04What does it take to connect Oracle Eloqua to Zapier?
A paid Zapier plan or the free trial, an Eloqua account, and rights on the data the Zap will touch. You add the connection from the Apps page with + Add connection, pick Oracle Eloqua, sign in in the tab that opens and grant Zapier access. For custom object steps, the Custom Object Type has to exist in Eloqua and be visible to your account, otherwise there is nothing to select. Once linked, the connection serves every Eloqua step.
05Why does Update Contact fail without an ID?
Because the action has to know which person to change. Update Contact needs either the Contact ID or the Email Address, and Update Account and Update Record need their own IDs. If the trigger does not carry that value, add Find Contact, Find Account or Find Record before the update, so the search hands the ID to the next step. A search makes the Zap multi-step, which your paid plan already allows.
06What if the Eloqua operation you need is not in Zapier?
Then the ready-made steps do not cover it. The visible list is eight triggers, ten actions and four searches, centred on contacts, accounts, records and custom objects; none sends an email or reads campaign results. The fallback is API Request (Beta), an advanced action that reuses your Eloqua connection, but it expects you to know Eloqua's own reference. If that is out of reach, a team that works with Zapier can tell you whether it fits or another route suits that step better.
07Zapier, Make or n8n for Oracle Eloqua?
It comes down to your own criteria rather than a ranking. On Zapier, Eloqua is a premium app with eight polling triggers, ten actions and four searches, plus an advanced request step for the rest. If your flows need near-instant reactions, or many steps per run, check how each platform handles polling, what it bills per run and whether it covers the Eloqua objects you depend on. Test the exact events you need on a trial before committing.
Same platform

Other docs you might need on this stack.

Browse all integrations