Storage by Zapier is a very handy tool for me, especially when used in conjunction with zaps that involve automatic loops that result from arrays returned from webhooks.
But it would really be great if you’d add to Storage by Zapier one of the functions you have for Sheets, the ability to trigger on a storage update.
Could I have a show of hands from anyone who would find this a helpful trigger? Imagine a gmail trigger that sets a storage value, and setting that value launches one or more zaps? This would be a handy workaround for the new gmail data restrictions, and a lot simpler than setting up sheets which could be inadvertently changed/damaged by anyone with access to a shared google drive.
Best answer by SamBBest answer by SamB
Hi folks! 👋
Just popping by with a quick update to share that the team have decided not to pursue this feature request at this time.
For anyone who comes across this thread and also wants to a “New or Updated Value or Child Value” trigger to be added to the Storage by Zapier app, I’d recommend trying out either of the workarounds suggested here previously, that I’ll list details of below:
Workaround from BenPeter:
If you’re interested, here’s a workaround/alternative option - use the Webhook polling trigger to watch for a specific key/value to change.
For example, in Zapier Storage, I have an object, which contains a field called lastUpdate which I update whenever my external code/system/Zap writes new data into Zapier Storage, like this: {"foo":"bar","lastUpdate":"2020-06-24T14:28:00.000Z"}'
I setup a Webhook polling Zap that watches for that key/value:
In that trigger setup, it also needs to set the header X-Secret to specify my super confidential storage key:
When that Zap is turned on, it will trigger every time it sees a new value for the lastUpdate key. In the Zap, the second step uses another Webhook step (or code step), to retrieve the current value/object/data from Zapier Storage.
One (possibly huge) limitation is that multiple updates/changes to the object (within Zapier Storage) during the Zap’s polling cycle results in only the last (most recent) change being noticed by the Zap. In these situations, a better approach is adding (pushing/appending) values to an array/list within the Zapier Storage key, then having the Zap read (and clear-out) that list of accumulated data from Storage (or using a code-step to perform all that work).
We have a feature request for a trigger that would run if a new value was added onto a list. The ‘push value onto list’ supports line items, so I feel like that’s the one that you’d need if you want to use storage instead of Google Sheets for that line items to single item trigger workaround. Is that what you’re looking for here, or were you thinking more along the lines of using the ‘value set’ trigger as opposed to ‘value added to list’?
I believe you misunderstand both my request and the potential benefits.
What I’m looking for is a set of triggers for Storage that are similar to those you currently support for Sheets.
Sheets can trigger on:
New Spreadsheet Row
New or Updated Row
New Spreadsheet
New Worksheet
I’m looking for Storage to trigger on
New Key
New or Updated Value or Child Value
Value Push / Pop
Because storage is a local function - that is, it’s presumably on Zapier’s servers, triggers should be far faster than an API call to Google. Also, the overhead of dealing with Sheets, which are also subject to change outside of Zapier, is tedious and risky.
As far as the need I mentioned is concerned, my interest in triggers would open up options for at least 3 of my production zaps. Now that webhooks have become so slow to fire in some environments, and now that Google doesn’t allow gmail data to be used in many non-Google situations, sending values to storage which would then trigger zaps would be of great assistance.
Totally agree these triggers would be super helpful within the Zapier Storage integration!
If you’re interested, here’s a workaround/alternative option - use the Webhook polling trigger to watch for a specific key/value to change.
For example, in Zapier Storage, I have an object, which contains a field called lastUpdate which I update whenever my external code/system/Zap writes new data into Zapier Storage, like this: {"foo":"bar","lastUpdate":"2020-06-24T14:28:00.000Z"}'
I setup a Webhook polling Zap that watches for that key/value:
In that trigger setup, it also needs to set the header X-Secret to specify my super confidential storage key:
When that Zap is turned on, it will trigger every time it sees a new value for the lastUpdate key. In the Zap, the second step uses another Webhook step (or code step), to retrieve the current value/object/data from Zapier Storage.
One (possibly huge) limitation is that multiple updates/changes to the object (within Zapier Storage) during the Zap’s polling cycle results in only the last (most recent) change being noticed by the Zap. In these situations, a better approach is adding (pushing/appending) values to an array/list within the Zapier Storage key, then having the Zap read (and clear-out) that list of accumulated data from Storage (or using a code-step to perform all that work).
It looks very interesting. My environment is such that I cannot employ Zaps which are not yet approved by Zapier. But the functionality you have added looks like it would work nicely for us as soon as they do approve it. Thanks.
Just popping by with a quick update to share that the team have decided not to pursue this feature request at this time.
For anyone who comes across this thread and also wants to a “New or Updated Value or Child Value” trigger to be added to the Storage by Zapier app, I’d recommend trying out either of the workarounds suggested here previously, that I’ll list details of below:
Workaround from BenPeter:
If you’re interested, here’s a workaround/alternative option - use the Webhook polling trigger to watch for a specific key/value to change.
For example, in Zapier Storage, I have an object, which contains a field called lastUpdate which I update whenever my external code/system/Zap writes new data into Zapier Storage, like this: {"foo":"bar","lastUpdate":"2020-06-24T14:28:00.000Z"}'
I setup a Webhook polling Zap that watches for that key/value:
In that trigger setup, it also needs to set the header X-Secret to specify my super confidential storage key:
When that Zap is turned on, it will trigger every time it sees a new value for the lastUpdate key. In the Zap, the second step uses another Webhook step (or code step), to retrieve the current value/object/data from Zapier Storage.
One (possibly huge) limitation is that multiple updates/changes to the object (within Zapier Storage) during the Zap’s polling cycle results in only the last (most recent) change being noticed by the Zap. In these situations, a better approach is adding (pushing/appending) values to an array/list within the Zapier Storage key, then having the Zap read (and clear-out) that list of accumulated data from Storage (or using a code-step to perform all that work).
When you visit any website, it may store or retrieve information on your browser, mostly in the form of cookies. This information might be about you, your preferences or your device and is mostly used to make the site work as you expect it to. The information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies. Click on the different category headings to find out more and change our default settings. However, blocking some types of cookies may impact your experience of the site and the services we are able to offer.
More about cookies
Customize which cookies to allow
Marketing cookies
These cookies may be set through our site by our advertising partners. They may be used by those companies to build a profile of your interests and show you relevant adverts on other sites. They do not store directly personal information, but are based on uniquely identifying your browser and internet device. If you do not allow these cookies, you will experience less targeted advertising.
Social media cookies
label
These cookies are set by a range of social media services that we have added to the site to enable you to share our content with your friends and networks. They are capable of tracking your browser across other sites and building up a profile of your interests. This may impact the content and messages you see on other websites you visit. If you do not allow these cookies you may not be able to use or see these sharing tools.
Analytics/performance cookies
These cookies enable the website to provide enhanced functionality and personalization, and allow us to count visits and traffic sources so we can measure and improve the performance of our site. They help us to know which pages are the most and least popular and see how visitors move around the site. These cookies may be set by us or by third party providers whose services we have added to our pages. If you do not allow these cookies then some or all of these services may not function properly and we will not know how you are using our site.
Functional cookies
label
These cookies enable the website to provide enhanced functionality and personalisation. They may be set by us or by third party providers whose services we have added to our pages. If you do not allow these cookies then some or all of these services may not function properly.
Essential cookies
Always active
These cookies are necessary for the website to function and cannot be switched off in our systems. They are usually only set in response to actions made by you which amount to a request for services, such as setting your privacy preferences, logging in or filling in forms. You can set your browser to block or alert you about these cookies, but some parts of the site will not then work. These cookies do not store any personally identifiable information.