Create Records

nocodb.create_records
ActionDatabases & warehousesconnection required

Calls the NocoDB API with the connection's credentials.

Insert one record or a list of records into a table.

Connection

Required
Yes — the node will not save without one
Auth type
API key
Providers
NocoDB
Secret shape
the API token, or {"api_token": "…"}
Config it needs
base_url, base_id, table_id, workspace_id
Resolved by
config.connection_id, else node.connection_id

Configuration

2 fields, 1 required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.

FieldTypeRequiredDefaultConstraintsExample
table_id
Id of the table to act on, from Table context menu → Copy table ID. Overrides the default table id on the connection.
stringNo——mftbsyu6dxo4y8i
records
One record object of field name → value, or a list of them.
arrayYes—array of object[{"Status":"todo","Title":"Renew licence"}]

Example configuration

Every value below is the contract’s own example or default — nothing invented.

{
  "records": [
    {
      "Status": "todo",
      "Title": "Renew licence"
    }
  ],
  "table_id": "mftbsyu6dxo4y8i"
}

Output

One shape.

result

FieldTypeExample
records
The primary keys NocoDB acted on, one entry per record.
array—
count
How many records the response covered.
number—
requested
How many records were sent in the request.
number—
all_written
True when NocoDB answered for every record sent; false means the response covered fewer, so read 'records' to see which.
boolean—
table_id
The table that was written to.
string—
{
  "all_written": false,
  "count": 0,
  "records": [],
  "requested": 0,
  "table_id": ""
}

See Create Records run in a workflow.

In a technical demo we add the NocoDB connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.