Databases

Group your workspace tables into databases

Databases group the tables in your workspace. Every table belongs to exactly one database, and table names are unique within their database — so two databases in the same workspace can each have their own leads table.

Open Databases in the workspace sidebar to see them. Each database lists its tables, and you can create, rename, and delete databases from the same view.

If you used tables before databases existed: your tables were moved into a database named Default, the sidebar entry changed from "Tables" to "Databases", and old table links redirect to the new pages. Your tables' data, schemas, and workflow references are unchanged.

Creating a Database

  1. Open Databases from the workspace sidebar
  2. Click New database
  3. Name it (up to 50 characters), optionally adding a description and color

Creating, renaming, or deleting a database requires Write or Admin workspace permission. Viewing databases and their tables only requires workspace access.

The Default Database

Every workspace has a fallback database — its oldest active one, named Default unless you've renamed it. Anything created without an explicit database lands there:

  • Tables created through the API, which doesn't take a database parameter
  • Tables created by workflow tools or assistants that don't specify a database

"Default" is just a name: you can rename the database freely, and the fallback continues to target the workspace's oldest active database.

Tables in a Database

  • Open a database and click New table to create a table inside it
  • Table names must be unique within their database, not across the workspace
  • Move a table to another database in the same workspace from the table's context menu — the move fails if the target database already has a table with that name

Querying a Database

You can run read-only queries against a database's tables using a SQL-like syntax:

SELECT * FROM leads WHERE status = "active" ORDER BY created_at DESC LIMIT 100

Queries support WHERE conditions combined with AND, plus ORDER BY, LIMIT, and OFFSET — see the Database block reference for the full operator table. Queries never modify data; writes go through the Table block.

Using Databases in Workflows

The Database block gives workflows four operations:

OperationWhat it does
List DatabasesList the workspace's databases with table counts
Create DatabaseCreate a database on the fly
List Tables in DatabaseList the tables inside one database
Query DatabaseRun a read-only query against a table

Row-level reads and writes (insert, update, upsert, delete) stay on the Table block. See the Database block reference for inputs and outputs.

Limits

  • 50 databases per workspace
  • Database names up to 50 characters, descriptions up to 500
  • Table counts and row caps are unchanged and remain per workspace — see Tables limits

Common Questions

Every table belongs to a database, but you don't have to think about it: the Default database is created for you, and anything that doesn't specify a database lands there.
Yes, if they're in different databases. Within one database, table names are unique.
No. The tables API is unchanged — it doesn't yet take a database parameter, tables created through it land in the Default database, and existing table IDs are untouched.
Yes, within the same workspace, from the table's context menu. The move fails if the target database already contains a table with the same name.
Anyone with Write or Admin permission on the workspace. Viewing databases and tables requires workspace access.
No. Databases are a flat, single level of organization — a database contains tables, never other databases.

On this page