Table Operations
Workflows work with tables through the Table block. Everything the block can do starts from its Operation dropdown, and every operation follows the same shape: you describe it in the panel, run the block, and read the result in the table.
What you will learn
Filters shape a query
A query is built from conditions, column, operator, value. Conditions stack, and each one narrows the match.
A query only reads
Running a query selects the matching rows and leaves the table untouched. Change one operator and the same run selects the opposite rows.
Writes take the same shape
Delete Rows by Filter uses the same filter. Insert Row swaps the filter for row data, and every key in the payload lands as a cell.
Update combines both
Update Rows by Filter pairs a filter with row data: the filter picks the rows, the data changes them in place.
Here is the block from the video, configured for the first query:
One shape for every operation
The panel describes what you mean: an operation, a table, and, depending on the operation, a filter, row data, or both. A filter is conditions stacked together (priority equals high, and status equals open), each one narrowing the match. Queries read without touching the table; Delete Rows by Filter removes what matches; Insert Row lands a payload as a new row; Update Rows by Filter picks rows and changes them in place.
Reading the result
The live table answers every run: matched rows highlight, deleted rows leave, inserted rows land, and updated cells flip where they sit. The block's output carries the same result back into the workflow for the next block to use.