Show & Tell
ive been using tinytable less like a spreadsheet and more like a database. storing workflow execution logs, customer records, inventory levels etc. basically anything that my workflows need to read from or write to
some tips from what ive learned so far:
- create a status column and use table views filtered by status. makes it easy to see pending, completed, failed records at a glance
- timestamps are your friend. always add a created_at and updated_at column so you can sort and filter by time
- dont put everything in one table. split into related tables like you would in a database. customer table + orders table + products table, not one mega table
curious what other patterns people are using
been doing the same thing. a few more patterns i use:
- unique ID column: always add a column with a unique identifier (we use a formula that generates a uuid). makes it easy to reference specific records in workflows
- archive dont delete: instead of deleting old records add an "archived" boolean column and filter your views to hide archived rows. that way you always have history
- changelog table: for important tables i have a separate changelog table where workflows write a row every time the main table gets updated. who changed what and when
the status column + filtered views approach is exactly how we manage our project pipeline. we have views for each stage: "new leads", "in progress", "pending review", "completed". its basically a kanban board but in table form
the changelog table idea is great. we had a situation where someone accidentally overwrote data and we had no way to know what the original values were. adding this to all our critical tables now
one pattern ill add: use a table as a configuration store. we have a "config" table with key-value pairs like "max_retries = 3", "notification_email = ops@company.com", "daily_limit = 500"
our workflows read from this table instead of having magic numbers hardcoded in nodes. when we need to change a setting we update one cell in the table, no workflow editing required
great tips all around. the config table pattern is something we use heavily. especially useful when you have non-technical team members who need to adjust settings without touching the workflow
this thread is gold. saving it
Community