Question

Trigger a zap when Shopify address changes

  • 4 August 2022
  • 4 replies
  • 44 views

Customers on our Shopify store sometimes change their shipping address prior to the order shipping, this might be the address name, the state, zip code or any combination of the above. 

I am hoping to create a zap that only fires if any of the address variables change. I’ve tried doing this with filters but I can’t see how it’s possible. The zap will need to fire order ID and new address details to Google Sheets. To reiterate I only want this to fire if any of the shipping address labels change. 


This post has been closed for comments. Please create a new post if you need help or have a question about this topic.

4 replies

Userlevel 7
Badge +14

Hi @neslot 

Good question.

Updates for many apps are not triggered on a per field basis.

This may not be easily doable as it can be a challenge to isolate which data point triggered the update as those are often not explicitly indicated, but it is doable.

 

NOTE: The first approach below is Task intensive as it will require at least 2 Tasks each time in order to Filter.

 

Zap steps would look like this:

  1. Trigger: Shopify
  2. Action: GSheet - Lookup Row
    1. By Order ID
  3. Action: Code
    1. Compare NEW vs OLD values
  4. Action: Filter
    1. Only if change detected
  5. Action: GSheet - Update Row
    1. Map the Row ID from step 2

 

Alternatively, you let the Zap be dumb with just update the GSheet Row each time for those address fields.

  1. Trigger: Shopify
  2. Action: GSheet - Lookup Row
    1. By Order ID
  3. Action: GSheet - Update Row
    1. Map Row ID from step 2

Hi @Troy Tessalone, thanks for the response!

I’m having a bit of difficulty setting these up, in either of these options will it cost me a zap for every time an order is updated / filtered? Which means every order that happens on the store will be a zap, as I believe simply fulfilling the order counts as an order update, if so this will sadly be too expensive.

Hopefully there’s a solution for this. 

Userlevel 7
Badge +14

@neslot 

Help article to learn about how Tasks are counted in Zap Runs: https://zapier.com/help/manage/history/learn-about-tasks-in-zapier

Userlevel 7
Badge +12

Hi @neslot

Troy’s solutions will definitely work, but you’re right that each time the order is updated (including fulfillment status), it would trigger the Zap. You could save some tasks by setting up a filter where if the status is ‘fulfilled’ the Zap doesn’t run any other actions. So, any fulfilled orders wouldn’t count against your tasks because the filter would stop them. Are there any other fields or order statuses you could filter on? For example, if the status is cancelled, shipped, or unpaid? 

Do you think that would reduce the tasks enough to make Troy’s solution viable for you?