The wxrks Eloqua connector pulls email and dynamic content assets out of an Oracle Eloqua instance and creates a wxrks translation project from them. Once translation is finished, wxrks delivers the localized asset back into the same Eloqua instance.

💡 Who is this for? This guide is for Account Admins (or anyone your account has granted connector configuration access) who set up and maintain the Eloqua connector. If you don't see Integrations in the sidebar, ask your account admin to grant connector access.

Key concepts

Term	What it means
Configuration	A saved connection between wxrks and one Eloqua account, tied to a specific wxrks Organizational Unit. You can create more than one.
Sync	The action that pulls assets from Eloqua and creates a wxrks translation project from them. Unlike some connectors, Eloqua does not push content to wxrks automatically — a sync is triggered on demand.
Asset type	Either Email or Dynamic Content — the two kinds of Eloqua asset the connector can translate. A single sync request pulls one type at a time.
Content ID (ciTag)	A label that groups related sync requests into the same wxrks project. Reusing it lets you add more assets (including a different asset type) to a project that's already been created.

Before you start

Have the following ready:

An Eloqua company name and a username/password with API access to that Eloqua instance.
The wxrks Organizational Unit that should own the translation projects created from Eloqua. If you haven't created one yet, see How to create an Organization or Organizational Unit.
Connector configuration access in wxrks (see "Who this is for").

Step 1: Create an Eloqua configuration

In the sidebar, select Integrations, then open the Eloqua connector.
Switch to the Config tab and select Add Configuration.

Eloqua connector Config tab with the Add Configuration button highlighted

Fill in the fields:

Create new Eloqua configuration form with Organizational Unit, Name, Company Name, Workflows, Username, and Password fields

Field	What to enter
Organizational Unit	The wxrks org unit that should own projects created from this configuration.
Name	A reference name so you can recognize this configuration later.
Company Name	The company name used to sign in to this Eloqua account.
Workflows	Optional. If none are selected, syncs from this configuration use the org unit's default workflows.
Username / Password	Credentials for the Eloqua user above. The password is encrypted before it's stored. wxrks looks up your Eloqua instance's login URL automatically from these credentials — you don't need to provide it.

Select Create to save the configuration.

Step 2: Create a translation project (sync)

From the Config tab, open a configuration's row menu and select Create Project (Sync) to sync a batch of assets into a new wxrks project.

[SCREENSHOT PLACEHOLDER: Eloqua configuration row's menu open, showing the "Create Project (Sync)" option and its form] — this pass created a disposable test configuration to reach this panel, but the automated Organizational Unit selector didn't complete the save in time to capture it live. The form's fields match the sync parameters below.

The fields you'll be asked for:

Parameter	Type	Description	Required
configUUID	string	The Eloqua configuration to sync from (see Step 1). The project's Organizational Unit always comes from this configuration — it's not read from any `orgUnitUUID` you send separately.	✅
contactUUID	string	The project's point of contact in wxrks.	✅
type	string	The asset type to fetch: `EMAIL` or `DYNAMIC_CONTENT`.	✅
sourceLanguage	string	Source language of the assets. Falls back to the org unit's default if omitted.	🚫
targetLanguages	list	Languages to translate into. Falls back to the org unit's default if omitted.	🚫
ciTag	string	Groups this sync into a project. Defaults to `eloqua`.	🚫
reference	string	The project's name in wxrks. Defaults to `Eloqua CI Project`.	🚫
workflows	list	Workflows to apply to every asset in this sync. If omitted, wxrks infers a workflow per file.	🚫
tags	list	Tags to add to the project. Up to 10.	🚫
assetIds	list	Specific Eloqua asset IDs to pull, in addition to anything found under `sourcePaths`. Up to 100 per sync.	🚫
sourcePaths	list	Full Eloqua folder paths. Every matching asset in each folder and its subfolders is pulled. One path per sync.	🚫
skipSuffixes	list	Filename suffixes to skip (Eloqua sometimes encodes a language code into a Dynamic Content name, e.g. an existing `PT-BR` variant).	🚫
skipHashCheck	boolean	By default, wxrks skips re-sending an asset whose content hasn't changed since it was last sent successfully. Set to `true` to resend anyway — needed if a previous project containing the same assets was Cancelled.	🚫

Translating assets from a specific folder

sourcePaths pulls every asset of the selected type from a folder and its subfolders. For example, a sync with:

{  "configUUID": "eloqua-config-uuid",  "contactUUID": "contact-person-uuid",  "targetLanguages": ["es_es", "pt_br"],  "workflows": ["TRANSLATION", "REVIEW"],  "type": "EMAIL",  "sourcePaths": [      "/Email Group Root/BureauWorks_Test"  ]}

creates a project with every email under /Email Group Root/BureauWorks_Test, in Spanish (Spain) only, using the Translation workflow for every file.

Combining emails and dynamic content in one project

The Eloqua connector doesn't follow nested content automatically — if an email references a Dynamic Content block, that block isn't pulled in the same sync. Emails and Dynamic Content can still land in the same wxrks project: run two syncs (one per type) using the same ciTag, and wxrks adds the second batch to the project the first one created.

How delivery works

Once a synced asset finishes translation in wxrks, the connector delivers the localized version back into the same Eloqua instance automatically — there's nothing to export or re-upload by hand.

Managing your configurations and tracking status

The Entries tab on the Eloqua connector page lists every asset that's been synced, with its current translation status per target language.

Eloqua connector Entries tab listing synced assets and their translation status

Good to know

Nested content isn't automatic: an email's Dynamic Content blocks need their own sync (see "Combining emails and dynamic content" above).
Limits per sync: up to 100 assetIds, one sourcePaths entry, and up to 10 project tags.
Finding your Org Unit's UUID: open the org unit under Organizations — its UUID is the last segment of the page's URL.
Multiple Eloqua accounts: create a separate configuration for each Eloqua company/instance you need to pull from.

Troubleshooting

Symptom	Likely cause and fix
Sync fails with a "Missing Eloqua project request param" error.	A required field is missing — check `configUUID`, `contactUUID`, `type`, `sourceLanguage`, and `targetLanguages` first.
An asset didn't come through even though the sync succeeded.	Its content likely matches what was already sent (hash match). Set `skipHashCheck: true` to force it through, or check the Entries tab for its current status.
A resend after cancelling a project doesn't pick up the assets.	Set `skipHashCheck: true` on the new sync — this is required whenever the previous project containing those assets was Cancelled.

Quick reference

Task	Where
Add or edit a configuration	Sidebar > Integrations > Eloqua > Config tab
Sync assets into a project	Config row menu > Create Project (Sync)
Check sync/translation status per asset	Eloqua connector > Entries tab
API reference	dev.wxrks.com

How to create an Organization or Organizational Unit
Using the wxrks Connectors Interface — the connector UI chrome (entries, statuses, filters) shared across all connectors.

wxrks - Eloqua Connector