Conditional Dispatch Zaps

Answered

January 17, 2019 12:22

I have apps built that dispatch additional GoCanvas Apps based upon conditions in the app. Eg. Do you want to dispatch a corrective actions report? Yes No. The only way I have figred out to only trigger the zap when the Yes is answered is to re-create all the necessary fields as mirrors on conditional screens. The additional screens are hidden from the mobile user. Upon submission of the app, if the user selects yes, the mirror fields zap to a google sheet and create a row which triggers the conditional dispatch. If the user answers no, the conditional screens/fields stay conditionally hidden so no information is sent to the spreadsheet therefore no dispatch is created. The major drawback to this is the fact that I essentially have to build the app twice. Build the app, then build it again as mirrors. Looking for some advice/methods to trigger a conditional dispatch without all the mirror fields. As I'm typing this, I think I came up with a solution in my head.. Use two google sheets with a second zap triggered by the "yes" column. Any how, if anyone knows a way to trigger the conditional dispatch using a simpler method, please share. Thanks.

Comments

3 comments

Nathan H

January 17, 2019 14:24
I would recommend using a filter within the zap itself and set it to "only continue if..." then reference the field in question and provide the expected value for it to continue. We have some zaps like this that work well.
1

Comment actions Permalink
Sara Kaplow, Community Manager

February 04, 2019 14:22
Agree with Nathan on this one - having the condition on the Zap side would be a good solution. You could do it with the filtering, or you could use Google Sheets and set the trigger column to that field:
1

Comment actions Permalink
Keith McQuait

February 08, 2019 12:20
Took me a while to get back to this.

I never noticed the options under the "add action" in Zapier. This is definitely good info, there are a lot of other useful items down there as well.

Lesson learned: always scroll to the bottom and read everything before determining your next move. Same could be said for those using gocanvas apps. I add instructions and find that people don't bother to read them before moving forward.

My apps continue to evolve and get more complex as I try to build in safeguards that prevent people from making the wrong choices.

Thank you both. You're assistance and advice is always greatly appreciated!
1

Comment actions Permalink

Please sign in to leave a comment.