Tables allow you to create and manage custom data tables directly within SteelEngine. Store, query, and manipulate structured data within your workflows without needing external database integrations.
Why Use Tables?
No external setup : Create tables instantly without configuring external databases
Workflow-native : Data persists across workflow executions and is accessible from any workflow in your workspace
Organized into databases : Every table lives in a database — a flat container that groups your workspace's tables
Flexible schema : Define columns with types (string, number, boolean, date, json) and constraints (required, unique)
Powerful querying : Filter, sort, and paginate data using MongoDB-style operators
Agent-friendly : Tables can be used as tools by AI agents for dynamic data storage and retrieval
Key Features:
Create tables with custom schemas
Insert, update, upsert, and delete rows
Query with filters and sorting
Batch operations for bulk inserts and upserts
Bulk updates, deletes, and replacements by filter
Tables per workspace and rows per table are plan-based — see Limits
Tables are created from the Databases section in the sidebar: open (or create) a database, then click New table . Workflows can also create tables with the Create Table operation (table_create). Each table requires:
Name : Alphanumeric with underscores (e.g., customer_leads), unique within its database
Description : Optional description of the table's purpose
Schema : Define columns with name, type, and optional constraints
Type Description Example Values stringText data "John Doe", "active"numberNumeric data 42, 99.99booleanTrue/false values true, falsedateDate/time values "2024-01-15T10:30:00Z"jsonComplex nested data {"address": {"city": "NYC"}}
Required : Column must have a value (cannot be null)
Unique : Values must be unique across all rows (enables upsert matching)
Filters use MongoDB-style operators for flexible querying:
Operator Description Example $eqEquals {"status": {"$eq": "active"}} or {"status": "active"}$neNot equals {"status": {"$ne": "deleted"}}$gtGreater than {"age": {"$gt": 18}}$gteGreater than or equal {"score": {"$gte": 80}}$ltLess than {"price": {"$lt": 100}}$lteLess than or equal {"quantity": {"$lte": 10}}$inIn array {"status": {"$in": ["active", "pending"]}}$ninNot in array {"type": {"$nin": ["spam", "blocked"]}}$containsString contains {"email": {"$contains": "@gmail.com"}}
Multiple field conditions are combined with AND logic:
{
"status" : "active" ,
"age" : { "$gte" : 18 }
}
Use $or for OR logic:
{
"$or" : [
{ "status" : "active" },
{ "status" : "pending" }
]
}
Specify sort order with column names and direction:
Multi-column sorting:
{
"priority" : "desc" ,
"name" : "asc"
}
Every row automatically includes:
Column Type Description idstring Unique row identifier createdAtdate When the row was created updatedAtdate When the row was last modified
These can be used in filters and sorting.
Resource Limit Databases per workspace 50 Tables per workspace Plan-based — 3 (Free), 25 (Pro), 100 (Team), 10,000 (Enterprise) Rows per table Plan-based — 100,000 (Free, Pro, Team) or 1,000,000 (Enterprise); see Tables limits Columns per table 1,000 Max row size 100 KB String value length 100 KB (the row size is the binding limit) Query limit 1,000 rows (default 100) Batch insert / upsert size 1,000 rows Bulk update / delete / replace 1,000 rows
Every table lives in a database within your workspace and is accessible from any workflow in that workspace
Use the Database block to list databases, create databases, list tables, and run read-only queries
Data persists across workflow executions
Use unique constraints to enable upsert functionality
The visual filter/sort builder provides an easy way to construct queries without writing JSON
Create and manage custom data tables. Store, query, and manipulate structured data within workflows.
Insert a new row into a table. IMPORTANT: You must use the "data" parameter (not "values", "row", "fields", or other variations) to specify the row contents.
Parameter Type Required Description tableIdstring Yes Table ID dataobject Yes Row data as JSON object
Parameter Type Description successboolean Whether row was inserted rowjson Inserted row data messagestring Status message
Insert multiple rows into a table at once (up to rows)
Parameter Type Required Description tableIdstring Yes Table ID rowsarray Yes Array of row data objects (max ${TABLE_LIMITS.MAX_BATCH_INSERT_SIZE} rows)
Parameter Type Description successboolean Whether rows were inserted rowsarray Inserted rows data insertedCountnumber Number of rows inserted messagestring Status message
Insert or update multiple rows by conflict target (up to rows). Updates require exactly one matching row; ambiguous matches are returned as per-row failures so workflows can route them without custom code.
Parameter Type Required Description tableIdstring Yes Table ID rowsarray Yes Array of row data objects to insert or update (max ${TABLE_LIMITS.MAX_BATCH_INSERT_SIZE} rows) conflictTargetstring No Column used to match existing rows. Required when the table has no single unique column; if multiple rows match a value, that row fails. continueOnErrorboolean No When true, continue processing remaining rows and return per-row failures. Defaults to true.
Parameter Type Description successboolean Whether the batch request completed rowsarray Successfully upserted rows resultsarray Per-row upsert results with operation or error insertedCountnumber Number of rows inserted updatedCountnumber Number of rows updated failedCountnumber Number of rows that failed messagestring Status message
Insert or update a row based on unique column constraints. If a row with matching unique field exists, update it; otherwise insert a new row. IMPORTANT: You must use the "data" parameter (not "values", "row", "fields", or other variations) to specify the row contents.
Parameter Type Required Description tableIdstring Yes Table ID dataobject Yes Row data to insert or update conflictTargetstring No Unique column to match when the table has multiple unique columns. If omitted, the table must have exactly one unique column.
Parameter Type Description successboolean Whether row was upserted rowjson Upserted row data operationstring Operation performed: insert or update messagestring Status message
Update an existing row in a table. Supports partial updates - only include the fields you want to change. IMPORTANT: You must use the "data" parameter (not "values", "row", "fields", or other variations) to specify the fields to update.
Parameter Type Required Description tableIdstring Yes Table ID rowIdstring Yes Row ID to update dataobject Yes Updated row data
Parameter Type Description successboolean Whether row was updated rowjson Updated row data messagestring Status message
Update multiple rows that match filter criteria. Data is merged into each row. Unique columns cannot be changed; use Update Row for those fields.
Parameter Type Required Description tableIdstring Yes Table ID filterobject Yes Filter criteria using operators like $eq, $ne, $gt, $lt, $contains, $in, etc. dataobject Yes Fields to update (merged with existing data) limitnumber No Maximum number of rows to update (default: no limit, max: ${TABLE_LIMITS.MAX_BULK_OPERATION_SIZE})
Parameter Type Description successboolean Whether rows were updated updatedCountnumber Number of rows updated updatedRowIdsarray IDs of updated rows messagestring Status message
Delete a row from a table
Parameter Type Required Description tableIdstring Yes Table ID rowIdstring Yes Row ID to delete
Parameter Type Description successboolean Whether row was deleted deletedCountnumber Number of rows deleted messagestring Status message
Delete multiple rows that match filter criteria. Use with caution - supports optional limit for safety.
Parameter Type Required Description tableIdstring Yes Table ID filterobject Yes Filter criteria using operators like $eq, $ne, $gt, $lt, $contains, $in, etc. limitnumber No Maximum number of rows to delete (default: no limit, max: ${TABLE_LIMITS.MAX_BULK_OPERATION_SIZE})
Parameter Type Description successboolean Whether rows were deleted deletedCountnumber Number of rows deleted deletedRowIdsarray IDs of deleted rows messagestring Status message
Delete rows matching filter criteria and insert replacement rows atomically. Empty replacement rows are allowed and clear the matching rows.
Parameter Type Required Description tableIdstring Yes Table ID filterobject Yes Filter criteria using operators like $eq, $ne, $gt, $lt, $contains, $in, etc. rowsarray Yes Replacement row data objects (max ${TABLE_LIMITS.MAX_BATCH_INSERT_SIZE} rows). Empty array clears matching rows. limitnumber No Maximum number of existing rows to replace (default: no limit, max: ${TABLE_LIMITS.MAX_BULK_OPERATION_SIZE})
Parameter Type Description successboolean Whether rows were replaced deletedCountnumber Number of rows deleted deletedRowIdsarray IDs of deleted rows insertedCountnumber Number of replacement rows inserted rowsarray Inserted replacement rows data messagestring Status message
Query rows from a table with filtering, sorting, and pagination
Parameter Type Required Description tableIdstring Yes Table ID filterobject No Filter conditions (MongoDB-style operators: $eq, $ne, $gt, $gte, $lt, $lte, $in, $nin, $contains) sortobject No Sort order as {field: "asc"|"desc"} limitnumber No Maximum rows to return (default: ${TABLE_LIMITS.DEFAULT_QUERY_LIMIT}, max: ${TABLE_LIMITS.MAX_QUERY_LIMIT}) offsetnumber No Number of rows to skip (default: 0)
Parameter Type Description successboolean Whether query succeeded rowsarray Query result rows rowCountnumber Number of rows returned totalCountnumber Total rows matching filter limitnumber Limit used in query offsetnumber Offset used in query
Get a single row by ID
Parameter Type Required Description tableIdstring Yes Table ID rowIdstring Yes Row ID to retrieve
Parameter Type Description successboolean Whether row was retrieved rowjson Row data messagestring Status message
Get the schema configuration of a table
Parameter Type Required Description tableIdstring Yes Table ID
Parameter Type Description successboolean Whether schema was retrieved namestring Table name columnsarray Column definitions messagestring Status message
Create a new user-defined table with schema
Parameter Type Required Description namestring Yes Table name (alphanumeric, underscores, 1-50 chars) descriptionstring No Optional table description schemaobject Yes Table schema with column definitions databaseIdstring No Optional database ID to create the table in
Parameter Type Description successboolean Whether table was created tablejson Created table metadata messagestring Status message