You know how ChatGPT can remember your entire conversation history? Whether that update left you excited or shaking in your boots, you probably noticed the more helpful responses the chatbot could provide after that memory boost.
Your automated workflows get better with memory, too. And Zaps can, in a way, "remember" your data—within the same workflow or even across Zaps—through Storage by Zapier.
Storage by Zapier is an advanced tool available on Pro plans and higher tiers. Compare Zapier plans on our pricing page.
Table of contents
Zapier is the most connected AI orchestration platform—integrating with thousands of apps from partners like Google, Salesforce, and Microsoft. Use interfaces, data tables, and logic to build secure, automated, AI-powered systems for your business-critical workflows across your organization's technology stack. Learn more.
What is Storage by Zapier?
Storage by Zapier is a built-in tool that lets you save small pieces of data your Zaps can use later on—either within the same Zap or across different Zaps. It's a lightweight database tool that can help you do things like count daily metrics, track customer interactions, rotate team assignments, or share data between workflows.
To create a data store, you first generate a password for it (we call this a "store secret"). Then you create keys for each type of data your store holds. One key might hold customer names, another lead counts, and so on.
For example, let's say you want to track how many daily webinar registrations you received from different sources. You can build a Zap with Storage that triggers every time someone signs up through your website, Facebook ad, or Google ad. Your Zap would then increment the respective counter in Storage—stored under separate keys for website, Facebook, and Google signups. At the end of each day, another Zap could retrieve all three counts and send you a Slack message showing exactly how many signups came from each source, then conveniently reset the counters to zero for the next day.
You could track this in a spreadsheet with auto-calculating formulas or use Zapier Tables to store detailed signup records. But if you only need simple daily totals, Storage offers the fastest solution.
Use this option | If... |
|---|---|
Storage by Zapier | You need a simple way to store small pieces of data—like counters, flags, or values—shared between Zaps. |
Zapier Tables | You want a structured, visual workspace to store and manage records—like customer info, task lists, or signup data—that's powered by AI and easily integrates with other apps. |
A spreadsheet tool | You're already managing data in a tool like Excel or Google Sheets and want to build Zaps within your existing tech stack. |
Note: Storage actions don't count as tasks toward your Zapier plan.
A few considerations to keep in mind: You can store up to 25 KB in each key (if you don't speak byte, that's roughly 25,000 characters), and each Storage account can hold 500 keys. Your store's secret must use UUID formatting, too—a specific format with 32 hexadecimal characters in five groups separated by hyphens. You can create one quickly using a UUID generator tool.
Storage by Zapier features include:
Lightweight data storage: Store single pieces of information, like "Kayla Barnes" (customer names), "121" (lead counts), or "premium" (subscription levels)—or more complex data, like a customer's name, email, and phone number all stored together using child values.
Reliable counting: Set values, increment counters, and manage lists accurately—even when multiple Zaps try to update the same data simultaneously. For example, if two leads arrive at the exact same moment and both try to increment your counter by one, Storage runs and completes one update at a time, so you'll never lose count.
Automatic cleanup: Stored data auto-expires after two months of inactivity, helping you organize your stores without manual maintenance.
Direct API access: Access your stored data at store.zapier.com using REST API requests like GET, POST, PATCH, and DELETE to retrieve, update, or remove keys and values.
What you can do with Storage by Zapier
Here are a few ideas for using Storage:
Limit a promo code to early responders
You're running a giveaway and want to send a promo code to only the first 150 people who fill out your form.
What this might look like:
A customer fills out your Typeform survey.
Storage by Zapier checks the current response count to see how many people have already filled out a form. (The first time, it'll always be zero.)
Filter by Zapier continues the workflow only if the count is less than 150.
If it is, a separate Storage step increments the count by one.
Gmail sends the discount code to qualifying respondents. After 150 responses, the Zap automatically stops sending codes.
Send freelancers reminders on their preferred day
You manage a team of freelancers who each prefer to send their weekly update on a different day. Instead of chasing them down or creating separate workflows, you want a smooth way to send each freelancer a reminder on the day they picked. And—to cut back on tool sprawl—you want it built using only Zapier tools.
What this might look like:
In your first Zap, a freelancer fills out a form in Zapier Interfaces and selects their preferred day to get a reminder.
Storage by Zapier saves their email and chosen day.
In a second Zap, Schedule by Zapier runs every weekday.
Storage pulls the list of saved preferences.
Looping by Zapier runs once (steps 6 through 7 below) for each freelancer.
Filter by Zapier checks whether that freelancer's selected day matches the current day.
If the freelancer's selection is a match, Email by Zapier sends them a reminder.
Validate a return address before updating a support ticket
When a customer submits a return request in your support tool, you need to check their shipping address against saved records in your CRM. If there's a match, you update the ticket with the verified address ID. If not, you leave a note for your support team to follow up.
What this might look like:
A return request is submitted in Zendesk.
A search step in NetSuite finds all saved addresses for the customer's account.
Looping by Zapier runs once (steps 4 through 5 below) for each saved NetSuite address.
AI by Zapier compares the submitted Zendesk address to the current NetSuite address and returns whether it's a match.
Paths by Zapier splits the workflow based on the AI result:
If it's a match, Zendesk updates the support ticket with the verified NetSuite address ID, and Storage by Zapier saves the ticket ID.
If it's not a match, Storage checks whether a match was already recorded. If not, a note is added to the Zendesk ticket asking the support team to verify the address.
Storage deletes the stored ticket ID to reset the workflow for the next return request.
How to get started with Storage by Zapier
To create your first Zap using Storage, log in to Zapier and open the Zap editor. Choose your trigger app and event, connect your account, and customize any necessary fields. Test the step to make sure it's working, then click Continue. If your workflow calls for it, add additional action steps.
When you're ready, add your first Storage by Zapier step. Search for and select Storage as your action app. You can also find it in the Utilities tab on the left-hand panel.
Next, choose the action event that fits your workflow. You'll see a lot of events—but if you're just getting started, you'll probably want to pick either Set Value or Get Value. Choose Set Value if you're storing text, dates, or JSON—or you want to reset a number each time the Zap runs (like resetting it back to zero). Choose Get Value if you're starting a numeric value that you'll increment later.
Then, in the Account field, click Select and then click Connect a new account.
In this step, you'll create a store secret. This is a UUID-formatted code that acts like your Storage account's username and password. When you're done, click Yes, Continue to Storage by Zapier.
Now, configure your action step. If you chose Get Value as your event, be sure to check the box next to Create Storage by Zapier Value if it doesn't exist yet.
If you want to map data from previous steps into a specific field in your Zap, click the + button or type a forward slash (/) within that field, which opens a modal that lets you select and insert values.
When you're done with your Storage action, test it to make sure it's working.
From here, continue building your Zap by adding action steps for other apps based on what you want your workflow to do—and configure and test each step as needed.
If you need to increment a stored value, add another Storage by Zapier step. Use the same store secret from the first Storage step to connect your account. Choose Increment Value as your event and set up the action using the same key from your first Storage step. Be sure to specify the amount you want to increment the value by.
When you're done adding all the action steps you want in your Zap, remember to test your Zap and turn it on.
Note: You can access your stored data through Storage's REST API at store.zapier.com. This gives you direct API access—it's not automated or push-based like webhooks. Use it to run GET, POST, DELETE, and PATCH requests to retrieve, update, or remove your keys and values from any application or script. If you're a non-technical user, no worries—Storage comes with action steps that let you do the same things within Zaps. For a storage alternative, check out Zapier Tables.
As you're setting up your Zap, keep in mind that you don't necessarily need more than one Storage step in a single workflow. For example, you can store something in one Zap, then retrieve it or manipulate it in another. Or you might want to just store values for an audit log, with the option to access them later in the REST API.
Add memory to your workflows with Storage by Zapier
Storage gives your automated workflows the power to remember—whether you're tracking counts, sharing data between workflows, or setting values to reuse later. It's lightweight, flexible, and easy to scale as you build more Zaps.
To explore more ways to use it, check out the Storage by Zapier integration page, visit our help guide, or jump straight into the Zap editor to start building.
