Storage by Zapier

Normally a Zap forgets everything once a run ends. Storage lets it save a value under a key, like a ClickUp task ID, and read it back in a later run or a different Zap.

It can set, get and remove values, add one to a counter, keep a simple list and only set a value if it's still what you expect. That makes it handy for counting, remembering what's already been done and passing small bits of data between Zaps.

Storage steps use no tasks. It's available on Professional, Team and Enterprise. Keys can be up to 32 characters, values up to 1 MB, and each Storage account holds up to 500 keys. Keys that aren't used for 2 months are deleted.

My main use is stopping duplicates. Some apps send the same webhook twice, so on one client build I used Storage to add one to a counter for each ClickUp task, then a Filter only lets the Zap carry on when the count is 1. The templated email only ever goes out once.

I use the same idea on a meeting notes Zap. Storage checks whether a note has already been handled, so the Zap only comments once per note. Because of the 500 key limit and the 2 month clean up, I keep keys short lived, and anything that needs a permanent record goes in a Zapier Table instead.

1. Trigger ClickUp sends a webhook when a task changes status 0 tasks
2. Storage Increment Value, using the task ID as the key 0 tasks
3. Filter Only carry on if the value is 1 0 tasks
4. Action Send the templated email 1 task