PostgreSQL

Node catalog Actions
On this page

Query, select, and manage PostgreSQL schemas, tables, and rows

Usage and specifics

Choose a credential or PostgreSQL service through connectionSource. Guided modes manage schemas, tables and rows; SQL mode executes the supplied query. DELETE, DROP and cascade can remove data.

Technical type : postgres. Runtime : nodulz.

Credentials and prerequisites

Create credentials in your nodulz instance’s Credentials area, then select them on the node. Availability depends on ownership and sharing. See the credentials guide for access and rotation.

Parameters

Names below are technical keys. Defaults are not a ready-to-run configuration: complete fields required by your operation. Paths containing [] describe list items; some fields depend on the selected mode.

Parameter Type Default Values / limits
credentialId string - -
serviceInstanceId string - -
connectionSource enum "credential" credential, service
operation enum "query" query, select, insert, update, delete, create_schema, drop_schema, create_table, drop_table, alter_table
query string "SELECT 1 AS ok" -
rawExpressions boolean false -
schema string "" -
table string "" -
columns string "*" -
data string "" -
match string "" -
orderBy string "" -
limit string "" -
ddl string "" -
ifNotExists boolean false -
ifExists boolean false -
cascade boolean false -
returning string "" -

Configuration help

connectionSource
Connection source
Use a manual credential or a service deployed in the Services space.
serviceInstanceId
Service instance
Only Available services matching the app binding are listed.
credentialId
Database credential
Connection settings are stored on the Credentials page.
operation
Operation
SQL operation type to run on PostgreSQL.
query
SQL query
Any SQL statement (SELECT, INSERT, DDL…). Expressions are sent as parameters: do not wrap them in quotes.
rawExpressions
Insert expressions as-is (unsafe)
Only for dynamic table or column names, with trusted values.
schema
Schema
PostgreSQL schema name (letters, numbers, underscore).
table
Table
Use double curly braces for dynamic values, e.g. {{ nodes.http1.body.id }}
columns
Columns
Comma-separated column list or * for all columns.
data
Data (JSON object)
JSON object: keys are column names, values are strings (workflow expressions allowed in each value).
orderBy
ORDER BY
Sort order, e.g. created_at DESC. Identifiers only.
limit
LIMIT
Maximum number of rows to return (positive integer).
returning
RETURNING (optional)
Columns to return after insert/update, e.g. * or id, created_at.
ddl
Definition
For create table: column definitions in parentheses. For alter: clause starting with ADD, DROP, ALTER, or RENAME.
ifNotExists
IF NOT EXISTS
Adds IF NOT EXISTS to the DDL statement.
ifExists
IF EXISTS
Adds IF EXISTS to the DDL statement.
cascade
CASCADE
Propagates deletion to dependent objects (DROP CASCADE).

Initial configuration

Initial catalog configuration example, to adapt before running. Keep secrets in credentials.

json
{
  "operation": "query",
  "query": "SELECT 1 AS ok",
  "schema": "",
  "table": "",
  "columns": "*",
  "data": "",
  "match": "",
  "orderBy": "",
  "limit": "",
  "ddl": "",
  "ifNotExists": false,
  "ifExists": false,
  "cascade": false,
  "returning": ""
}

Verification

Test with representative data. Check node output in the inspector and logs, then use editor mapping for downstream fields. A trigger test with a simulated payload does not validate external service delivery.

See also : Expressions and data, Executions, Node catalog.