Database nodes
Workflow nodes for querying, inserting, and updating database tables.
EzFlow provides four dedicated nodes for reading and writing data in your workspace tables from inside a Workflow. Each node maps to one of the four standard data operations.
Overview
| Node | Operation | Addresses table by |
|---|---|---|
| SEARCH_DATABASE_RECORD | Find records matching filters | Table name |
| ADD_DATABASE_RECORD | Insert a new record | Table name |
| UPDATE_DATABASE_RECORD | Patch an existing record | Record ID |
| REMOVE_DATABASE_RECORD | Delete a record | Record ID |
SEARCH_DATABASE_RECORD
Finds records in a table that match a set of filter conditions.
You specify the table name and a map of key-value filters. The node checks each filter against the record's data JSON field using exact equality on each key. All filters must match (AND logic). Records are returned newest-first, up to the configured page size.
If no records match the filters, the node returns an empty list rather than an error.
Common uses:
- Look up a contact by email address before deciding what to send.
- Check whether a record for a given ID already exists.
- Retrieve configuration or reference data stored in a table.
SEARCH_DATABASE_RECORD node reference →
ADD_DATABASE_RECORD
Inserts a new record into a table.
You specify the table name and the data to store as a JSON object. The node creates a new record with a unique ID. The output includes the created record's id, which you can pass to downstream nodes that need it.
Common uses:
- Save the result of an API call for later use.
- Append an entry to a log table.
- Record that a Workflow reached a particular step for a given contact.
ADD_DATABASE_RECORD node reference →
UPDATE_DATABASE_RECORD
Updates an existing record by its ID.
You specify the record ID (typically from a previous SEARCH or ADD node output) and the fields to update as a JSON object. The node merges the new values into the existing data — keys you omit are preserved, and keys you include are overwritten.
Common uses:
- Mark a record as processed after a Workflow step completes.
- Append a timestamp or status field to an existing record.
- Update a counter or flag on a contact record.
UPDATE_DATABASE_RECORD node reference →
REMOVE_DATABASE_RECORD
Permanently deletes a record by its ID.
You specify the record ID to delete. Deletion is immediate and permanent — there is no soft-delete or undo for individual records.
Common uses:
- Remove a temporary record after it has been processed.
- Clean up an entry from a queue table once a job is done.
REMOVE_DATABASE_RECORD node reference →
Addressing tables by name
SEARCH and ADD nodes look up the target table by name, not by ID. This means that if you rename a table in the Databases UI, any Workflow that references it by the old name will fail. Use stable, descriptive table names and update Workflows if a rename is needed.
UPDATE and REMOVE nodes address records by ID, so they are not affected by table renames.