Many automations need memory: what was already processed, a list of approved customers, a status per request.
A Zap forgets everything after each run. When you need to remember things, such as which leads were already contacted, use Zapier Tables: a simple database built into Zapier. A database is just an organised place to store records, like a spreadsheet designed for programs.
A table has fields (columns, each with a type such as text, number, date, true/false, or a link to a record in another table) and records (rows). You can create a table from scratch, import data, or let AI draft one.
Zaps work with tables like with any other app:
- Triggers such as "new record" or "updated record" start Zaps.
- Actions create, update and find records.
Tables add a few handy features:
- Formula fields compute values from other fields, like in a spreadsheet.
- AI fields fill a field using AI, such as a one-line summary of a long note.
- Linked records connect rows across tables, such as orders to customers.
- Deleted records go to a Trash you can restore from.
Tables can also act as a knowledge source for AI steps, so an AI step can look up your product list or policies.
Why not just use Google Sheets? You can, but Tables live inside Zapier, so they connect without extra app connections and work closely with Forms. For very large or business-critical data, a real database or your CRM may still be the right home.
Sharing and permissions are set per table.
Remember
- Tables give Zaps memory: records with typed fields
- Zaps can trigger on, create, update and find table records
- Formula fields, AI fields and linked records add spreadsheet-like power