Define a table, mark what you'll search on, and start using it immediately — right inside your workflows. Fast at any scale, and it can trigger a workflow the moment something changes.
Tables live in younifyd's own storage — nothing else to provision
Define a table's fields — text, numbers, true/false, lists, nested objects, whatever shape you need — and it's ready to use immediately. No separate database to set up, no connection details to manage.
Every record has a clear, unique identifier, so looking one up is instant, even as the table grows to millions of rows.
9 field typesincluding nested objects and lists
Filtering is fast because it's restricted to fields you've actually indexed
Mark up to five fields per table as searchable, and filtering on them stays fast no matter how big the table gets. Filter on something you haven't marked, and we tell you upfront instead of quietly running a slow search that gets worse every month.
Browsing results never gets slower as you page deeper — page 5,000 of a huge table costs exactly the same as page one.
5 indexed fieldsper table — no silent slow searches
Insert, Get, Find, Update, Upsert, Delete, Bulk Upsert — as native steps
A table shows up as a step right inside the workflow builder — drag it in like any other connector. No separate API to call and parse.
Importing a big batch of data? One bad row in ten thousand won't block the rest — it's flagged and skipped, and everything else goes through.
500-row batchesone bad row never blocks the rest
A record change can kick off a workflow automatically
Subscribe a workflow to a table's changes, and it fires the moment something's created, updated, or deleted — automatically retried if something goes wrong downstream, so you never lose an event.
That turns a table into more than storage. Write to a "pending orders" table from anywhere, and a fulfilment workflow can pick it up automatically. No polling, no scheduler to build.
create · update · deleteany of the three can trigger a workflow
Primary-key reads don't need a secondary index at all
Every record's own identifier is built to be the fastest possible way to find it — a direct lookup, not a search.
That matters once a table holds millions of rows. The lookups you do most — "get this customer," "get this order" — stay fast no matter how big the table gets.
instantlookups by ID, at any scale
Define a table, mark what you'll search on, and start using it — right inside your workflows. No database to set up.
Related capabilities
