JSON rows stored in nodulz, scoped to this workflow (no external database)
Usage and specifics
These tables persist in nodulz and belong to the workflow. Define columns and types before inserting. Conflict and matching modes control upserts and updates.
Technical type : workflow_table. Runtime : nodulz.
Credentials and prerequisites
This node defines no dedicated external credential. Remote sources or execution targets may still need their own access credentials.
See the credentials guide if a remote source or execution target requires access.
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.
Create or query an internal table identified by name within this workflow.
insertFieldMode Inserted fields
Schema columns only (drop extra keys) or extend the table schema from keys found in the data.
insertConflictMode On constraint conflict
When a row violates a primary key or unique column: fail the operation, skip the row, merge into the existing row (upsert), or delete the existing row then insert (replace). With no PK or unique columns, every row is inserted.
seedData Seed rows
Rows inserted when the table is created. Values may be workflow expressions.
columns Columns
Comma-separated column list or * for all columns.
orderBy ORDER BY
Sort on a row field, e.g. score DESC or created_at ASC.
limit LIMIT
Maximum number of rows to return (positive integer).
ifNotExists IF NOT EXISTS
Adds IF NOT EXISTS to the DDL statement.
ifExists IF EXISTS
Adds IF EXISTS to the DDL statement.
Initial configuration
Initial catalog configuration example, to adapt before running. Keep secrets in credentials.
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.
JSON rows stored in nodulz, scoped to this workflow (no external database)
Usage and specifics
These tables persist in nodulz and belong to the workflow. Define columns and types before inserting. Conflict and matching modes control upserts and updates.
Technical type :
workflow_table. Runtime :nodulz.Credentials and prerequisites
This node defines no dedicated external credential. Remote sources or execution targets may still need their own access credentials.
See the credentials guide if a remote source or execution target requires access.
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.
tableScopeenum"workspace"workspace,legacytableIdstringoperationenum"select"list_tables,create_table,alter_table,drop_table,clear_table,select,insert,bulk_insert,update,deletetablestring"items"tableNameInputModeenum"select"select,textschemaColumnsstring"[]"seedDatastring""columnsstring"*"datastring""matchstring""orderBystring""limitstring""insertFieldModeenum"schema_only"schema_only,extend_schemainsertConflictModeenum"fail"fail,skip,upsert,replaceifNotExistsbooleanfalseifExistsbooleanfalseConfiguration help
operationOperation
insertFieldModeInserted fields
insertConflictModeOn constraint conflict
seedDataSeed rows
columnsColumns
orderByORDER BY
limitLIMIT
ifNotExistsIF NOT EXISTS
ifExistsIF EXISTS
Initial configuration
Initial catalog configuration example, to adapt before running. Keep secrets in credentials.
{ "tableScope": "workspace", "operation": "select", "table": "items", "tableNameInputMode": "select", "schemaColumns": "[]", "seedData": "", "columns": "*", "data": "", "match": "", "orderBy": "", "limit": "", "insertFieldMode": "schema_only", "insertConflictMode": "fail", "ifNotExists": false, "ifExists": false }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.