Database Nodes
Database nodes let you interact with external databases from your workflows. Each supported database type provides four operations: Query, Insert, Update, and Delete.
Unlike the built-in DataStore, database nodes require a connection to be configured first. Connections store encrypted credentials and can be reused across multiple nodes and workflows.
Supported Databases
| Database | Nodes | Connection Setup |
|---|---|---|
| MySQL | Query, Insert, Update, Delete | MySQL Connection |
| PostgreSQL | Query, Insert, Update, Delete | PostgreSQL Connection |
| Supabase | Query, Insert, Update, Delete | Supabase Connection |
Common Features
All database nodes share the same set of operations and configuration fields. The differences between MySQL, PostgreSQL, and Supabase are:
- MySQL uses backtick quoting for identifiers.
- PostgreSQL and Supabase use double-quote quoting and add a Schema field (defaults to
public). - PostgreSQL and Supabase Query nodes include a Show Query Plan (EXPLAIN) option for debugging slow queries.
Getting Started
- Create a connection for your database type in the Connections section.
- Add a database node to your workflow (e.g., MySQL Query).
- Select your connection in the node configuration.
- Choose a table and configure the operation.
TIP
You can use different connections of the same type within the same workflow. For example, read data from a production PostgreSQL database and write it to a staging one.
Streaming Support
Insert, Update, and Delete nodes support piped execution mode. When receiving a stream of items from an upstream node, operations are executed per item and results are passed downstream immediately. Insert nodes use batching for optimal performance with large datasets.