Not 110. It would be 2 or 4 tasks per day, depending on how you construct it.  If using the “delay” trigger to run twice a day, you’d need a task to read the data in excel row and a task to write the data in sheets.  If the trigger is “new row in excel”, then the row data is in that payload (no task consumed), and then one task would be used to write the data in sheets.

Hi thanks for your help however we have tried the demo and each cell did count as a task (unbelieveably) so doing this twice a day is working out expensive - i did double check on the chat and zapier confirmed - but thanks for your help

Ah, that’s using the Transfer feature of Zapier.  I was approaching it from a different angle...

sorry unsure what you mean - this is the first time we have used Zapier

Hi there @jill2308,

I’m jumping in to see if I can help!

If building a Zap it sounds like it would trigger when there's a new row in Excel then adding a copy of that row into Google Sheets, is that correct? If so, then the Zap would consists of one trigger and one action so it would just be one task incurred per run of the Zap. A task is only incurred each time an action is run - not when the each cell is updated or when a Zap is triggered. You can learn more about how tasks are counted here: https://help.zapier.com/hc/en-us/articles/8496196837261

If using Transfer, each record (or row in this case) you move with Transfer by Zapier counts as a task. You wouldn't incur a task for each cell that is updated just every row that is copied to Google Sheets. When setting up the transfer you'll be shown exactly how many tasks will be used, for example:

(view larger)

I also want to share this blog post explaining Transfers: https://zapier.com/blog/zapier-transfer-guide/

Hope that clears things up!