Skip to content
Documentation
Contact
← Back to documentation
Technical Reference

Oracle Database

Enterprise-grade relational database

CategoryDeveloper Tools
Authenticationcustom
Version0.1.13
Published scopes0 published scopes
Last updatedSeptember 30, 2026

Overview

Connect Oracle Database with Flows360

Enterprise-grade relational database

Use the Oracle Database connector to include its declared actions and events in Flows360 workflows without duplicating the integration logic inside each consuming system. This pinned connector version currently exposes 6 actions and 1 trigger.

Available actions

  • Insert Row
  • Insert Rows
  • Run Custom SQL
  • Update Row
  • Delete Row
  • Find Row

Available triggers

  • New Row

The capability list above is generated from the exact reviewed connector package so the public description stays aligned with the version Flows360 operates.

Technical guide

Technical reference

Package identity

  • Connector: Oracle Database
  • Package: @activepieces/piece-oracle-database@0.1.13
  • Exact artifact digest: sha256:a5b1f1d0b49c7a678bcbdda91ede91a7a3c3656ad7da97424f183e3d6a699c05
  • Runtime: Activepieces-compatible deterministic worker
  • Source: the exact reviewed Activepieces source

Authentication

CUSTOM AUTH. Connection values are tenant-specific and remain in the consuming Studio instance; CDK stores definitions and field metadata, not customer credential values.

Action contracts

  • Insert Row (insert_row), Insert a row into an Oracle table Classification: read.
  • Insert Rows (insert_rows), Insert multiple rows into an Oracle table Classification: read.
  • Run Custom SQL (run_custom_sql), Execute custom SQL or PL/SQL in Oracle Classification: read.
  • Update Row (update_row), Update rows in an Oracle table Classification: read.
  • Delete Row (delete_row), Delete rows from an Oracle table Classification: read.
  • Find Row (find_row), Find rows in an Oracle table Classification: read.

Trigger contracts

  • New Row, polling.

Verification

Runtime execution evidence is managed separately from package metadata.

Capability summary

Authenticationcustom
Supported objects7
Supported actions6
Triggers1

Authentication

Authentication method: custom

Authentication profiles

connection · custom
  • Connection Type Required
  • Host Optional
  • Port Optional
  • Service Name Optional
  • Connection String Optional
  • Username Required
  • Password Required · protected credential
  • Thick Mode Optional

Supported objects

ObjectReadWriteNotes
Insert Row Yes No Insert a row into an Oracle table
Insert Rows Yes No Insert multiple rows into an Oracle table
Run Custom SQL Yes No Execute custom SQL or PL/SQL in Oracle
Update Row Yes No Update rows in an Oracle table
Delete Row Yes No Delete rows from an Oracle table
Find Row Yes No Find rows in an Oracle table
New Row Yes No polling trigger declared by the pinned package.

Supported actions

Insert Row · Read

Insert a row into an Oracle table

insert_row · Risk: low · Retry: safe

Inputs

  • tableName · string · Required
  • row · object · Required, Column names and values to insert
Insert Rows · Read

Insert multiple rows into an Oracle table

insert_rows · Risk: low · Retry: safe

Inputs

  • tableName · string · Required
  • rows · array · Required, Array of objects with column names and values
Run Custom SQL · Read

Execute custom SQL or PL/SQL in Oracle

run_custom_sql · Risk: low · Retry: safe

Inputs

  • markdown · string · Optional, **DO NOT** insert dynamic input directly into the query. Use bind parameters (:param) to prevent **SQL injection**.
  • sql · string · Required, SQL or PL/SQL to execute. Use :param for bind parameters.
  • binds · object · Optional, Key-value pairs for bind variables
Update Row · Read

Update rows in an Oracle table

update_row · Risk: low · Retry: safe

Inputs

  • tableName · string · Required
  • values · object · Required, Column names and new values to set
  • filter · object · Required, Conditions to match rows. Empty object updates ALL rows.
Delete Row · Read

Delete rows from an Oracle table

delete_row · Risk: low · Retry: safe

Inputs

  • tableName · string · Required
  • filter · object · Required, Conditions to match rows for deletion
Find Row · Read

Find rows in an Oracle table

find_row · Risk: low · Retry: safe

Inputs

  • tableName · string · Required
  • filter · object · Required, Conditions to match rows

Triggers

New Row · Poll

Triggers when a new row is created

Inputs

  • description · string
  • tableName · string
  • orderBy · string
  • orderDirection · string

Setup

Setup

  1. Add the Oracle Database connector to the workflow in the target Flows360 Studio instance.
  2. Create or select the tenant-specific connection required by the connector. Connection secrets remain in the Studio connection boundary and are not copied into CDK documentation.
  3. Provide the connection fields declared by the pinned package:
  • Connection Type (connectionType), required.
  • Host (host), optional.
  • Port (port), optional.
  • Service Name (serviceName), optional.
  • Connection String (connectionString), optional.
  • Username (user), required.
  • Password (password), required; stored as a sensitive connection value.
  • Thick Mode (thickMode), optional.
  1. Select the required action or trigger and complete its declared input fields. Required and optional inputs are defined by the exact package schema.
  2. Test the workflow in the appropriate environment before enabling production scheduling or event delivery.

Limitations

Limitations and operational notes

  • This content describes @activepieces/piece-oracle-database@0.1.13; provider behaviour can change independently and should be revalidated when the provider or connector version changes.
  • Only the 6 actions and 1 trigger declared by this pinned package are represented here.
  • Tenant credentials and connection values are not stored in the public connector record.
  • Provider-side permissions, account entitlements, quotas and rate limits remain subject to the connected provider account and are not inferred when the package does not declare them.
  • Runtime execution evidence is managed separately from package metadata.

Troubleshooting

Why canu2019t the connector authenticate?

Check the tenant connection in Studio and confirm every required Oracle Database connection field is present. Re-authorise OAuth-based connections if the provider token or consent has expired. Do not place credential values in CDK content or logs.

Why is an action or trigger unavailable?

Confirm that the workflow is using @activepieces/piece-oracle-database@0.1.13 and compare the requested capability with the declared action and trigger list for this version. A capability that is not declared by the pinned package should not be presented as supported.

What should I check after a provider-side change?

Revalidate authentication, required fields, action/trigger behaviour and provider documentation before publishing refreshed connector content or moving a new package version into production.

github.com