Skip to main content
A table holds rows of data that your flows use as a memory: customers that were already processed, orders waiting for a decision, a list of results. Flows create tables, add and change rows, and start from changes. People work with the same data in the Registry.

​
Tables are Registry object types

The Tables plug works on the Registry. Each automation workspace gets its own Registry schema, named Automation: followed by the name of the workspace. A table is an Object Type in that schema, a field of the table is an attribute, and a row is an Object. Open the Registry to browse and edit them like any other data, with the usual views, search and permissions. A flow always acts with the service account of its workspace. It sees the tables of the schemas that account may read, and it changes only what the account may change.

​
Fields

The first field of a table is its label, the title that the Registry shows for a row. Every other Registry field type reads as text.

​
Work with rows

The Tables plug has actions to create a table and its fields, and to find, read, insert, change and delete rows. Add them in the step list like any other action. The names are listed there. Deleting rows cannot be undone.

​
Start a flow from a row

Choose a trigger of the Tables plug to run a flow when a row is created, updated or deleted. A table can have up to 20 such subscriptions. A run starts only for a row the workspace’s service account may see.
Last modified on October 26, 2026