Configure integrations

Enable an integration on a repository and enter its connection settings so your authors can use it. Integrations are configured per repository, in the repository’s settings — each repository can point at a different external account. CM Box currently ships one built-in integration, Oracle Eloqua, which this page uses as the example; custom integrations are delivered as part of your CM Box build (see Building integrations).

Before you start: you need a role with the admin.repositories.* permissions to open the Repositories admin area (see Security), and the credentials of the external account — for Eloqua, the company name, user name, and password of an Eloqua user allowed to create assets.

Set up the Eloqua integration

The Oracle Eloqua integration lets site builders export a rendered page to Eloqua as an email asset. It is a beta feature, so its labels carry a (BETA) tag.

1. In the admin area, open Repositories and select the repository to configure.
2. Scroll to the Repository Features: table and check Oracle Eloqua Integration (BETA). The feature’s settings section appears at the bottom of the page.
3. Expand Oracle Eloqua Integration Settings (BETA) and fill in:
   • Company Name — your Eloqua company (site) name. CM Box signs in to Eloqua as CompanyName\UserName, Eloqua’s standard login format.
   • User Name — the Eloqua user to authenticate as.
   • Password — that user’s password.
4. Under Allowed Export Types, select the content types whose pages may be exported. The list offers the repository’s site-page content types; the Export action only appears on items of the types you select here.
5. Click Save Config.

Verify

Open a page of one of the allowed export types in the site builder — an Export action now appears (as a button and in the page’s actions menu). Choosing it opens the export drawer with Export system: set to Eloqua and Export type: set to Email; a successful export offers Edit Exported Item and View Exported Item Preview links that open the new asset in Eloqua.

To check the credentials without exporting, call the integration’s test route with an API client:

GET /api/integration/eloqua/<repository-id>/test

It verifies the stored credentials against Eloqua’s sign-in service. There is no test button in the admin UI. See Building integrations for the integration’s full route table.

Troubleshooting

• No Export action on a page — either the Oracle Eloqua Integration (BETA) feature is off for that repository, or the page’s content type is not in Allowed Export Types.
• Exports fail after a credential change in Eloqua — re-enter the Company Name, User Name, and Password in the repository settings and save. The fields are not validated when you save, so a typo only surfaces when an export (or the test route) runs.