Hello,
I am trying to follow this article:
I am trying to get this to work by following the code step described in the above post, I feel like I have it set up correctly but its still triggering twice.
Heres some screenshots of how I have the Zap set up and the Zap runs history.
Have I done something wrong?
Regards
+14
Hi
Good question.
Perhaps try a different approach that doesn’t involve code.
Use a GSheet to log the submission IDs.
Use the GSheet Lookup Row (else Create Row) logic.
If an existing row was found, then the Filter step would not pass.
hi Troy,
I now have my Zaps set up in this way however they are still triggering twice. I wondered if you can have a look at my set up for me ?
I have attached screenshots of how the zap is set up, and also the 2 duplicated triggered Zap runs. They are both looking for the same uuid in the spreadsheet however they both return “_zap_data_was_found: false”. If this was working correctly the second zap run should return “_zap_data_was_found: true” and then not continue, as my next zap step is a filter step to only continue if “_zap_data_was_found: false”
Thanks
+14
The screenshots did not load.
+14
If the Zap is triggering twice, then that’s due to the ServiceM8.
Try changing the Delay in Step 2 from a FOR to a AFTER QUEUE.
Thanks Troy, will try this out I have now changed them all to “After Que”
Hi Troy,
I have tried changing it to Delay After Que as suggested howver im still getting the same issue. Oddly enough one Zap triggered 3 times.
Heres the screenshots
+14
Can you show screenshots of the DATA IN/OUT for the first 4 steps from each Zap Run?
Make sure to include the timestamps for each Zap step.
Zap Run 1
Zap Run 2
Zap Run 3
Hi Troy see attached in order of runs (first run at the top). Hope this is easy to understand
Regards
+14
Can you post screenshots with how your Delay step is configured?
Doesn’t look like your Delay step has been configured as Delay After Queue.
That is because the Zap Runs only show 2 inputs, rather than 3.
Hi Troy,
Please see attached
Regards
+14
You need to add a Queue Title
You need to add a Queue Title
Hi Troy, thanks will do. Do you think this is what has been causing the issue?
+14
Probably.
When in doubt, test it out.
Probably.
When in doubt, test it out.
Unfortunately not :(
+14
We would need to see updated screenshots for the Zap Runs DATA IN/OUT.
We would need to see updated screenshots for the Zap Runs DATA IN/OUT.
Here we go in order
Zap Run 1
Zap Run 2
Zap Run 3
Regards
+14
Try changing the Queue title, as per the field description which has a max of 32 characters.
Try changing the Queue title, as per the field description which has a max of 32 characters.
Hi Troy,
Still getting the same error unfortunately
Zap Run 1
Zap Run 2
Zap Run 3
Thanks
+14
Looks like the data were the same for Zap Runs 1&2 but different for Zap Run 3, which would help explain some of this.
Can you show a screenshot with how your Zap Filter step is configured?
Looks like the data were the same for Zap Runs 1&2 but different for Zap Run 3, which would help explain some of this.
Can you show a screenshot with how your Zap Filter step is configured?
Apologies I provided incorrect screenshots on Zap run 3. This was a seperate Zap trigger, I will amend them now to the correct ones. Heres how the filter is set up anyway
+14
You may want to try reaching out to ServiceM8 Support, who likely created and manages their Zap app integration, about their Zap webhook trigger issue where it fires multiple times.
Otherwise, you may want to look into using a different approach for the Zap trigger.
Possibly using the ServiceM8 API: https://developer.servicem8.com/reference/get-formresponse-all
Hi Troy,
I initially raised the issue with them when I originally created this post many months ago, and still haven’t had a response. So unfortunately I’m on my own when it comes to resolving this as Servicem8 just don’t care.
The proposed workaround does not involve Servicem8 but instead uses google sheets as you obviously know so a fix should in theory be possible because of this. I just don’t understand why the lookup/create row step is returning false when there is in fact a row which contains the uuid when I manually search for it in the sheet. This is an issue with Zapier/sheets rather than servicem8 right?
+14
Can you post a screenshot with how your Zap step is configured?
If the Zaps are all processing at the same time, then none with find the search value, unless it already exists.
Another option to try instead of GSheets is Airtable as the lookup table.
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
