1. Support
  2. Integrations
  3. NoSQL Database
Databases 16 nodes

NoSQL Database

Databases integration · 16 node(s).

00Overview

Work with Oracle Cloud NoSQL Database straight from a flow — create and manage tables and their secondary indexes, and read, insert, replace and delete individual rows by primary key. Run SQL SELECT queries across a compartment's tables, prepare reusable statements, move tables between compartments, and adjust throughput and storage limits as your automation runs. Track a table's read/write and storage usage over time so a flow can watch capacity and act before limits are reached.

Every field below is exactly what you see in the Flomation editor. Fields marked ● live picker let you choose from a list pulled live from your account — no IDs to look up.

01Connecting NoSQL Database

  1. In the node's Authentication field, choose how to connect: Connect Oracle Cloud (the default) lets you pick a saved Flomation-managed Oracle Cloud account from the Oracle Cloud connection field, while API signing key (advanced) reveals the raw signing fields so you can paste an existing key by hand.
  2. For Connect Oracle Cloud, open the Oracle Cloud connection picker, then add or select an Oracle Cloud account and follow the guided connection flow — once the connection tests green the signing key is configured for you, so you can skip the remaining key steps.
  3. For API signing key (advanced), sign in to the Oracle Cloud Console, open the Profile menu (the avatar at the top-right) → My profile, then under Resources choose API keys → Add API key and download the private key (a .pem file).
  4. Oracle Cloud then shows a Configuration file preview — copy its values into the node: tenancy → Tenancy OCID, user → User OCID, fingerprint → Key Fingerprint, and region → Region (a plain region key such as uk-london-1).
  5. Set the Compartment OCID on every node — open Identity & Security → Compartments and copy the OCID of the compartment that holds the tables you want to work with (use the tenancy OCID for the root compartment).
  6. Store the downloaded private key as a Flomation environment secret (e.g. nosql_secret) and select it in the node's Private Key (PEM) field; if the key is passphrase-protected, add the passphrase as a secret too and pick it in Private Key Passphrase.
FieldTypeDetails
AuthenticationstringConnect Oracle Cloud, API signing key (advanced)
Oracle Cloud connectioncredentialPick a connected Oracle Cloud account
Regionstringe.g. uk-london-1
Private Key (PEM)secretThe API signing private key — full PEM, incl. BEGIN/END lines
Private Key PassphrasesecretOnly if the key is encrypted (optional)
Tenancy OCIDstringocid1.tenancy.oc1..aaaa…
User OCIDstringocid1.user.oc1..aaaa…
Key Fingerprintstringaa:bb:cc:… fingerprint of the uploaded API key
Good to know

Pick an Environment on your flow (Flow Settings → Environment) so the secret resolves. Secret fields never show the value — they reference ${secrets.your_secret}.

02Index

OCI NoSQL: Create Index

oracle/nosql/index_create · Action

Create a secondary index on a NoSQL table — give it a name and a comma-separated list of key columns. Runs asynchronously and returns a work-request OCID to track until ACTIVE.

FieldTypeDetails
Compartment OCIDstringRequiredocid1.compartment.oc1..aaaa… (the table's compartment)
Table OCID or NamestringRequiredA table OCID, or a table name within the compartment
Index NamestringRequiredA name for the new index
Key Columns (CSV)stringRequiredComma-separated column names, e.g. lastName,firstName

Returns: tool_result, id, work_request_id, success, error

OCI NoSQL: Delete Index

oracle/nosql/index_delete · Action

Delete a secondary index from a NoSQL Database table by name. Asynchronous — returns a work-request id you can poll until the drop completes.

FieldTypeDetails
Compartment OCIDstringRequiredocid1.compartment.oc1..aaaa…
Table OCID or NamestringRequiredThe table's OCID, or its name within the compartment
Index NamestringRequiredThe name of the index to delete

Returns: tool_result, id, work_request_id, success, error

OCI NoSQL: Get Index

oracle/nosql/index_get · Action

Fetch a single secondary index on a NoSQL Database table by name — its key columns and lifecycle state.

FieldTypeDetails
Compartment OCIDstringocid1.compartment.oc1..aaaa… (needed to interpret a table name — optional)
Table Name or OCIDstringRequiredA table name within the compartment, or a table OCID
Index NamestringRequiredThe name of the table's index

Returns: tool_result, index, name, lifecycle_state, success, error

OCI NoSQL: List Indexes

oracle/nosql/index_list · Action

List the secondary indexes of a NoSQL Database table, identified by table name or OCID. Walks pagination up to a safe cap.

FieldTypeDetails
Compartment OCIDstringocid1.compartment.oc1..aaaa… — needed to interpret a table name (optional)
Table Name or OCIDstringRequiredA table name within the compartment, or a table OCID

Returns: tool_result, indexes, count, truncated, success, error

03Prepare

OCI NoSQL: Prepare Statement

oracle/nosql/prepare_statement · Action

Compile a NoSQL SQL statement into a reusable prepared statement and return its query execution plan.

FieldTypeDetails
Compartment OCIDstringRequiredocid1.compartment.oc1..aaaa…
SQL StatementtextRequiredA NoSQL SQL statement, e.g. SELECT * FROM my_table WHERE id = $id

Returns: tool_result, prepared, success, error

04Query

OCI NoSQL: Run Query

oracle/nosql/query · Action

Run a NoSQL SQL SELECT statement against the tables in a compartment and return the matching rows. Walks pagination up to a safe cap.

FieldTypeDetails
Compartment OCIDstringRequiredocid1.compartment.oc1..aaaa… (use the tenancy OCID for the root)
SQL StatementtextRequiredSELECT * FROM my_table WHERE id = 1

Returns: tool_result, rows, count, truncated, success, error

05Row

OCI NoSQL: Delete Row

oracle/nosql/row_delete · Action

Delete a single row from a NoSQL Database table by its primary key.

FieldTypeDetails
Compartment OCIDstringocid1.compartment.oc1..aaaa… — needed when the table is given by name (optional)
Table Name or OCIDstringRequiredA table name within the compartment, or a table OCID
Primary KeystringRequiredComma-separated column:value pairs, e.g. id:42,region:emea

Returns: tool_result, success, error

OCI NoSQL: Get Row

oracle/nosql/row_get · Action

Fetch a single row from a NoSQL Database table by its primary key — the row's column values.

FieldTypeDetails
Compartment OCIDstringocid1.compartment.oc1..aaaa… — needed when identifying the table by name
Table OCID or NamestringRequiredocid1.nosqltable.oc1..aaaa… or a plain table name
Primary KeystringRequiredComma-separated "column:value" pairs in PK order, e.g. id:42,region:emea

Returns: tool_result, row, success, error

OCI NoSQL: Update Row

oracle/nosql/row_update · Action

Put (insert or replace) a single row in a NoSQL Database table from a JSON object of column values, returning the new row version.

FieldTypeDetails
Compartment OCIDstringRequiredocid1.compartment.oc1..aaaa… (use the tenancy OCID for the root)
Table Name or OCIDstringRequiredA table name within the compartment, or a table OCID
Row Value (JSON)textRequired{"id":1,"name":"Ada"} — a JSON object mapping every primary-key (and any) column to its value

Returns: tool_result, version, existing_version, generated_value, success, error

06Table

OCI NoSQL: Change Table Compartment

oracle/nosql/table_change_compartment · Action

Move a NoSQL table into a different compartment — the table keeps its OCID, only its compartment placement changes.

FieldTypeDetails
Compartment OCIDstringRequiredocid1.compartment.oc1..aaaa… (the table's current compartment)
Table OCID or NamestringRequiredA table OCID, or a table name within the current compartment
Destination Compartment OCIDstringRequiredocid1.compartment.oc1..aaaa… (where to move the table)

Returns: tool_result, id, work_request_id, success, error

OCI NoSQL: Create Table

oracle/nosql/table_create · Action

Create a NoSQL Database table from a CREATE TABLE DDL statement and its read/write/storage limits. Returns a work-request id — poll Get Table until ACTIVE.

FieldTypeDetails
Compartment OCIDstringRequiredocid1.compartment.oc1..aaaa…
Table NamestringRequiredThe table name (must match the DDL)
CREATE TABLE StatementtextRequiredCREATE TABLE my_table (id INTEGER, name STRING, PRIMARY KEY(id))
Max Read UnitsintegerRequiredMaximum sustained read throughput (e.g. 50)
Max Write UnitsintegerRequiredMaximum sustained write throughput (e.g. 50)
Max Storage (GB)integerRequiredMaximum storage in GB (e.g. 25)

Returns: tool_result, work_request_id, success, error

OCI NoSQL: Delete Table

oracle/nosql/table_delete · Action

Delete a NoSQL Database table by name or OCID — its rows and indexes are removed too. Returns a work-request id to poll.

FieldTypeDetails
Compartment OCIDstringRequiredocid1.compartment.oc1..aaaa…
Table Name or OCIDstringRequiredA table name within the compartment, or ocid1.nosqltable.oc1..aaaa…

Returns: tool_result, id, work_request_id, success, error

OCI NoSQL: Get Table

oracle/nosql/table_get · Action

Fetch a single NoSQL Database table by OCID (or by name within a compartment) — its schema, limits and lifecycle state.

FieldTypeDetails
Compartment OCIDstringocid1.compartment.oc1..aaaa… — needed when identifying the table by name
Table OCID or NamestringRequiredocid1.nosqltable.oc1..aaaa… or a plain table name

Returns: tool_result, table, id, lifecycle_state, success, error

OCI NoSQL: List Tables

oracle/nosql/table_list · Action

List the NoSQL Database tables in a compartment, optionally filtered by a shell-globbing-style (*?[]) name pattern. Walks pagination up to a safe cap.

FieldTypeDetails
Compartment OCIDstringRequiredocid1.compartment.oc1..aaaa… (use the tenancy OCID for the root)
Name FilterstringShell-globbing-style (*?[]) filter for table names (optional)
Page SizestringMax items to fetch per page (optional)

Returns: tool_result, tables, count, truncated, success, error

OCI NoSQL: Update Table

oracle/nosql/table_update · Action

Partially update a NoSQL Database table — change its throughput/storage limits and/or run an ALTER TABLE DDL statement. Asynchronous: returns a work-request id, so poll Get Table until the change is applied.

FieldTypeDetails
Compartment OCIDstringRequiredocid1.compartment.oc1..aaaa… (required to resolve a table by name)
Table OCID or NamestringRequiredocid1.nosqltable.oc1..aaaa… or a table name — the table to update
Max Read UnitsstringNew sustained read throughput limit (supply all three limits together)
Max Write UnitsstringNew sustained write throughput limit (supply all three limits together)
Max Storage (GB)stringNew maximum storage in GB (supply all three limits together)
DDL StatementtextComplete ALTER TABLE … statement (optional)

Returns: tool_result, id, work_request_id, success, error

OCI NoSQL: List Table Usage

oracle/nosql/table_usage_list · Action

Report a NoSQL table's usage records (read/write throughput and storage per sampling period), identified by name or OCID. Optionally filter by a time window and limit; walks pagination up to a safe cap.

FieldTypeDetails
Compartment OCIDstringocid1.compartment.oc1..aaaa… (needed when the table is given by name, not OCID)
Table Name or OCIDstringRequiredA table name within the compartment, or a table OCID
Start TimestringRFC3339, e.g. 2026-07-01T00:00:00Z — omit for the most recent record (optional)
End TimestringRFC3339, e.g. 2026-07-02T00:00:00Z (optional)
LimitstringMax usage records per page (optional)

Returns: tool_result, usage, count, truncated, success, error

07Notes & Limitations

Behaviours and constraints worth knowing before you build with these nodes.

  • Creating, updating and deleting tables, and creating and deleting secondary indexes, all run asynchronously and hand back a work-request OCID; the resource is not usable (or fully removed) until a follow-up Get Table or Get Index confirms the change, reporting a lifecycle state of ACTIVE once a create or update has completed.
  • Update Row performs an insert-or-replace of the entire row from the JSON you supply, so it overwrites any existing row rather than merging individual columns, and the JSON must include every primary-key column.
  • Create Table always provisions the table in fixed-capacity mode, so the Max Read Units, Max Write Units and Max Storage (GB) limits are all mandatory and on-demand capacity cannot be selected through this node.
  • Run Query and the list actions stop walking pagination after an internal cap and set a truncated flag, so results from very large tables or compartments may come back incomplete.