Hi ​@danielle879235 

Help links for using Storage: https://zapier.com/apps/storage/integrations#help

For us to have more context, post screenshots showing how your Zaps steps are configured in EDIT mode with the field mappings visible.

Hi Troy

Regarding field mapping, this is more related to removing values in my storage account. For example, this key was a mistake. I want to delete it.. how can i?

Regarding the fuzzy match. These should have all been 1 key, but due to the spacing, zapier thought it was a new key. 

Here is how the step looks like. So if there was an erroneous white space, the create storage if not found would yield a true, EVEN THOUGH its not truly a newer entry, so my question is if there is some type of fuzzy match

​@danielle879235 

Storage does exact matching for keys.

Zap action: Storage - Remove Value

You can configure a temp Zap and manually configure a Zap step to remove the desired values.

There is also the Storage API: 

Help links for using Storage: https://zapier.com/apps/storage/integrations#help

​@danielle879235 

If you want better visibility and pretty much the same functionality, then instead of using Storage, use Zapier Tables, which gives you an interface to use for the database and the records in the database.

Zapier Tables Zap app: 

https://zapier.com/apps/zapier-tables/integrations#triggers-and-actions

https://zapier.com/apps/zapier-tables/integrations#help

Zapier Tables help: https://help.zapier.com/hc/en-us/categories/13398036609933-Tables

Thank you Troy.

You said “

Storage does exact matching for keys.

Zap action: Storage - Remove Value

You can configure a temp Zap and manually configure a Zap step to remove the desired values.”

This has also been an issue for me.. The key= fist part which is basically constant values. BUT, the step you sited says remove value.. Am i removing the value or the key? In this case, i want to remove both, but sometimes its the just the value (and not the key). Is there a differentiation in zapier?

Further, using zapier tables was a thought, but my whole purpose of this step is to try and overcome google sheets issue limitations when someone adds a row in the middle of the sheet. So the flow is does this exist person/DOB (key)=status, phone # (value). If not, create it

Thank you Troy.

You said “

Storage does exact matching for keys.

Zap action: Storage - Remove Value

You can configure a temp Zap and manually configure a Zap step to remove the desired values.”

This has also been an issue for me.. The key= fist part which is basically constant values. BUT, the step you sited says remove value.. Am i removing the value or the key? In this case, i want to remove both, but sometimes its the just the value (and not the key). Is there a differentiation in zapier?

Further, using zapier tables was a thought, but my whole purpose of this step is to try and overcome google sheets issue limitations when someone adds a row in the middle of the sheet. So the flow is does this exist person/DOB (key)=status, phone # (value). If not, create it

Would zapier tables being able to address this? From what i know in the past, if we add a row in sheets, it will mimic whats going on in tables

​@danielle879235 
Help links to reference for using Storage: https://zapier.com/apps/storage/integrations#help

If you remove the Storage key, then you also remove the key value.

​@danielle879235 

Zapier Tables is a database.

GSheets is a spreadsheet.

There are fundamental differences in how data is structured and handled.

If you are trying to use Storage in place of GSheets, then you probably want to try using Zapier Tables instead of GSheets.

Plus, you can configure a Zap that sets the Zapier Tables Record ID in a field on the Zapier Table record, that way when you run the Zap and it finds a Record, you can troubleshoot by manually checking the returned Record ID in the Zap Run against the Zapier Table to find the Record by ID that was used in the Zap Run.

Why not do a quick proof of concept to test the functionality?

Thank you Troy. I set up a zap and will see how it works

But, in general, we must use googlesheets for any workflow since the entire team uses it (unfortunately). 

I really have 2 use cases for using storage, and please let me know if you think using tables can override the storage issue

1. As you know, when rows get added mid sheet, it shifts all the rows down and therefore, creates “new records.” Since we need to use sheets, what happens when someone adds a row mid sheet, does it create “new records” over and over again? 
2.  We have Gsheet-Gsheet zap set up for whenever the name in column G changes, a log is created, BUT, due to the sheets limitation listed in #1, we were getting a lot of duplicates that werent changes, just rows.… we were using storage to see IF the name in column G is the same as in storage, then do nothing. So, my question is will i be able to set up a zap/adjust the one I created to ONLY trigger a record when something changed rather than false entries? If so, how would i do that? I’m guessing with a filter and adding a step for Find records??? Please assist
3. What happens when someone adds a row in row 3 and over 500 lines now “crated new records.” It will timeout the zap… Can tables handle that?

Meanwhile, what is storage used for, if tables provides a bigger benefit?

​@danielle879235 

Help links for using GSheets in Zaps that covers many of the things to be aware of: https://zapier.com/apps/google-sheets/integrations#help

1. Depends on how the GSheet is used in the Zaps and how the GSheet is configured
   1. It’s more nuanced than a simple answer
2. GSheet Zap triggers are either:
   1. New Row
   2. New or Update Row
      1. This triggers for new rows AND triggers for updated rows
         1. You can specify a GSheet column to watch for changes
            1. But new rows will still trigger the Zap
3. Tables does not have that issue
   1. A new record doesn’t impact the other records in the Table

Storage is an older Zap App integration with no UI, so you can only interact with data via the Zaps or an API.

Tables is a new Zap app integration with a UI, so you can see and edit your data.

There are some data structure differences with the field types between Storage and Tables, but that’s getting into more advanced automation concepts with arrays and objects, etc.

I recommend reviewing the available resources for using these apps in Zaps.

Tables

• Triggers/Actions: https://zapier.com/apps/zapier-tables/integrations#triggers-and-actions
• Help: https://zapier.com/apps/zapier-tables/integrations#help

Storage

• Triggers/Actions: https://zapier.com/apps/storage/integrations#triggers-and-actions
• Help: https://zapier.com/apps/storage/integrations#help

Thank you Troy. As always, so helpful

Back to #2: GSheet-- we use new/updated row. Are you saying that still when i add a row in the middle of the sheet, it will still trigger new zaps, even when i specify changes to a specific column. Basically, if i add a row between 2 &3 and my trigger is an update to column A, A3 becomes, A4, A4 becomes A5, etc… Would that still trigger all the zaps?

Is there no workaround for this limitation? I always thought check if i can first somehow see if the record exists (storage) and if not, then create a record and the zap continues. Any advice?

​@danielle879235 

Zap trigger: GSheets - New or Updated Spreadsheet Row

Description: Triggers when a new row is added OR modified in a spreadsheet.

Meaning: Triggers when a new row is added AND when a row is modified in a spreadsheet worksheet, even if you have a trigger column specified. (In short, all new rows will trigger the Zap to run.)

Workaround include making sure Zap step logic is added to properly Filter for only rows that meet the conditions you want to process.

That may also involve advanced approaches using other apps to help you do deduplication.

Other workarounds include using different apps:

• Zapier Tables
• Airtable
• etc.

Hey ​@danielle879235 👋 Did Troy help you to get this solved?

Want to make sure you’re all set, so please keep us posted on your progress! 🙂

Hey Sam..

Sort of, not really lol

As for my original question regarding storage? Yes, resolved

But, then he opened a can of works using tables, which definately improved the idea of my flow HOWEVER i am getting the same issue with zaps breaking when a row is added in the middle of a spreadsheet.. so frustrating with google

I wonder if google’s API calls will improve that… Any insight or flows to recommend?

I’m so sorry for the delay in my reply, ​@danielle879235. Really glad Troy was able to help with your Storage question, thanks ​@Troy Tessalone! 🤗 

As for the unnecessary triggering of the Zap, even if you were to use Google’s API directly you’d still end up running into a similar issue as it doesn’t provide unique ID’s for each row. Google Sheets uses the row number as the ID for each row, so when a new row is added to the middle, all the rows below it then have their row ID number increased by one, causing the Zap to trigger.  

The only way to prevent the Zap from triggering when a new row is added to the middle of a Google Sheets spreadsheet would be to turn the Zap off, add the row, then turn the Zap back on. 

Not an ideal solution I know, but hopefully it helps to prevent the Zaps triggering unnecessarily.