Databases
Built-in relational tables for storing structured data inside EzFlow.
EzFlow includes a built-in database layer — tenant-scoped tables you can create, manage, and read or write from inside Workflows using database nodes.
What databases are
Each workspace (tenant) has its own isolated set of tables. A table is a named container of records. Each record is a JSON object with arbitrary key-value pairs — there is no fixed schema that you define in advance. You add columns implicitly by including keys in the records you write.
This makes the database flexible: you can start writing records with a few fields and add new fields later without a migration step.
How databases fit into Workflows
You read and write database records from Workflows using the four database nodes. Common patterns include:
- Look up a contact record before deciding what message to send.
- Store the result of an API call for use in a downstream step or a later Workflow run.
- Track state across multiple Workflow executions (for example, whether a user has already received an onboarding message).
- Maintain a list of processed IDs to avoid duplicate processing.
The database nodes address tables by name, so renaming a table in the UI will break any Workflow that references it by the old name. Use stable, descriptive table names.
Where databases live
Manage your tables at Databases (app route /databases). From there you can create tables, view records, add rows manually, and delete tables or records.