Connector library

Implemented source Data, Storage & Cloud APIs

Oracle Database connector.

Discover Oracle REST Data Services metadata catalog resources and read object column, type and primary-key metadata through two named ORDS GET actions using a managed bearer credential.

Download connector See all connectors

Connector download

Download Oracle Database

Versioned ZIP for your CXFabric tenant.

Sign in to download Using connectors

Use this connector in a flow

  1. Register the ZIP in your tenant, or add a new version if the connector is already installed.
  2. Create or select a credential if the action requires one.
  3. In a Draft flow, add an available action, choose its version, connect it, and map inputs.
  4. Test the step and flow; review output and failures before activation.

See readme.md in the ZIP for settings and limitations.

Version
v0.2.0.0 Choose version
Release
2026-10-04
Package
Implemented source
Schema credentials
Bearer token
Connection settings
Metadata Catalog URL
Package size
10 KB
SHA-256
20b096c50592c93f25b7f7bb8ed626b230409c78c14037fc3c792bf4f3b83e93

Version history

What's new

  1. v0.2.0.0Latest · 2026-10-04 · Implemented source

    No change summary is recorded for this version; review its source and setup guide before use.

    Full release notesView download
  2. v0.1.1.0Earlier · 2026-10-02 · Starter scaffold

    No change summary is recorded for this version; review its source and setup guide before use.

    View download

Included in this version

Included actions

Implemented in v0.2.0.0. Use a separate flow trigger; no webhook trigger is included.

List REST-enabled resources

Read one native catalog response of named REST-enabled resources and checked canonical metadata links.

Get object metadata

Read one exact canonical object metadata URL and return its checked name, columns/types and optional primary key.

Vendor API

API and access

Vendor API documentation Vendor website
Implementation considerations
  • Configure the complete approved HTTPS Metadata Catalog URL ending in /metadata-catalog/. An installed ORDS service, REST-enabled schema/objects and matching catalog privileges are required. Store an issued ORDS OAuth or accepted JWT token in managed bearerToken; requests use Bearer Authorization.
  • Map the exact resource name and canonical Object Metadata URL from discovery. A name such as EMP may differ from the emp URL alias. Canonical links stay beneath the same configured catalog; data and next links are not followed.
  • Catalog coverage is the first native page of REST-enabled resources, not a complete database inventory. Maximum Items and Maximum Columns are local caps, not server paging queries. Native hasMore is retained; there is no automatic paging or completeness inference.
  • Optional primary-key metadata preserves absence and empty arrays. Column names/types and optional vectorInfo retain native values; duplicate columns/keys, mismatched identities and excessive results fail without truncation.
  • Two GET actions expose metadata only. Native Oracle connections, SQL execution, row retrieval, writes, provisioning and administration/monitoring APIs are excluded. Metadata access does not establish database health or permissions for other operations.
  • Normal TLS trust, a 1 MiB response cap, strict JSON/UTF-8 and a shared 1–8 second budget are required. Stalled and trickling responses are canceled without redirects, proxies or replay. Hosted import, executor dependencies and live token/privilege/response behavior remain untested.
  • Two packaged ORDS metadata reads use canonical catalog links and an issued managed bearer credential. The current native developer guide grounds metadata and authentication; hosted dependencies and live catalog privileges/response behavior need validation.

Support

Need help with Oracle Database?

Tell us what you need to connect or change.

Contact us Back to connectors