A practical field guide from Automation Ace.
How to use this list
Storage by Zapier remembers small values between Zap runs, and Zapier Tables stores records your Zaps and your team can work with. These ten use cases show which tool fits each job and how to build it reliably.
If you are deciding between the two, start with Storage by Zapier vs Zapier Tables.
1. Generate sequential invoice or ticket numbers
Tool: Storage (Increment Value)
Each new invoice or ticket increments a counter and uses the result as its number, such as INV-1043.
Build tip: Increment in one step rather than reading and writing separately, to avoid duplicate numbers when runs overlap.
2. Round-robin lead assignment
Tool: Storage + Zapier Tables
Tables holds the list of reps and whether each is active; Storage holds the current position. Each lead goes to the next active rep.
Build tip: See round-robin in Code steps and lead routing.
3. Remember where a sync left off
Tool: Storage
A scheduled Zap stores the last processed ID or timestamp so the next run fetches only newer records.
Build tip: Update the cursor only after processing succeeds. See push vs pull automation.
4. Pause many Zaps with one switch
Tool: Storage
Every Zap checks a maintenance_mode value and stops if it is on, so you can pause a whole system during a migration.
Build tip: Document the key so it is not forgotten; see Zapier points of failure.
5. Maintain editable lookup tables
Tool: Zapier Tables
Territories, price tiers, or owner assignments live in a table that sales ops edits; Zaps use Find Record to look them up.
Build tip: See Zapier Tables as a lookup table.
6. Log Zap runs for auditing
Tool: Zapier Tables
Each important Zap writes a row with the source ID, outcome, and timestamp, giving you a searchable audit trail.
Build tip: See Zap run logs with Sub-Zaps and Tables and finding which automation changed a record.
7. Deduplicate webhook events
Tool: Zapier Tables
Store each event ID; before processing, check whether it exists and skip it if so.
Build tip: See webhook deduplication and why webhooks fire twice.
8. Queue work and process it in order
Tool: Zapier Tables
Incoming items are written as rows with a status; a separate Zap processes the oldest pending row and marks it done.
Build tip: See sequential queues with Zapier Tables.
9. Accumulate items for a daily digest
Tool: Storage or Zapier Tables
Throughout the day, Zaps add items; a scheduled Zap sends the digest and clears them. Use Tables if items have several fields or there are many.
Build tip: Keep Storage values under the size limit, or switch to Tables for longer lists.
10. Track approvals and statuses with buttons
Tool: Zapier Tables
Requests land in a table with a status column; a button field or status change triggers the next step, such as sending an approval or notifying the requester.
Build tip: Pair with Human in the Loop for inline approvals, or the approval workflow guide for multi-stage flows.
Patterns across every use case
- Values in Storage, records in Tables. See key-value vs tables.
- Design for concurrency. Overlapping runs can collide; use atomic increments, unique keys, and status fields.
- Write state only after success, so a failed run can be retried safely. See safe reprocessing.
- Share deliberately. Document which Zaps read and write each key or table. See sharing data between Zaps.
- Know when to graduate to Airtable or a real database; see Storage vs Tables vs external databases.
Build your first one with Storage by Zapier or Zapier Tables.
Frequently asked questions
What is Storage by Zapier used for?
Common uses include sequential numbering with Increment Value, round-robin positions, sync cursors that remember the last processed item, kill switches that pause many Zaps, and small shared settings.
What is Zapier Tables used for?
Common uses include editable lookup tables, Zap run logs, webhook deduplication lists, processing queues, and approval or status tracking with buttons and record triggers.
How do I generate sequential numbers in Zapier?
Use Storage by Zapier Increment Value on a counter key and use the returned value as the next number. Incrementing in one step avoids duplicates when runs overlap.
How do I deduplicate webhooks in Zapier?
Store each event ID in a Zapier Table, check for it before processing, and skip events you have already seen.
Disclaimer: Zapier features, plan availability, and settings can change. Confirm current details in Zapier's help documentation and Zapier's Storage and Tables usage-limit pages before relying on a specific setting. This article may include links to apps, products, or services; some links may be affiliate links, which means Automation Ace may earn a commission at no extra cost to you.