Hi all,
Our Glide app is sending out messages to clients (SMS, email, etc.). We’d like to have an option to integrate quick one-click responses from clients. For example, if we send a meeting reminder, the client would have an option to click on one element to confirm, or another element request a reschedule. What is the best way to go about this?
My novice and non-coder brain has came up with this workflow:
Create a Google Form in which we’ll log the client responses.
In the message to the client, we’ll include pre-filled and direct-submit links. The pre-pilled parameters will be something like clientID, response type, etc.
In Integromat, we’ll watch for new form submissions. Once a new submissions is logged, we’ll start the required actions.
I’m sure this is very primitive solution, inefficient and prone to errors. I’d be happy to hear your thoughts.
I had a thought about this weeks ago, but with emails. Apparently you can put parameters to a webhook URL (for Zapier/Integromat) and clicking a button directed to that URL means a form submission, just that the resulting screen after clicking that message might be weird for the end user.
Our friends at Integromat Support have provided with this perfect solution (webhook to webhook response):
You can create a new scenario with a webhook and set up a 303 redirect response with the Webhook Response module. Here I used a Set variable module as example, but you can add however many and whatever modules you want:
This scenario will redirect the user to google.com after processing all the data. You can also map a variable as the Location value, so if the WhatsApp link is created in another scenario, you’ll need to either pass it on the Query String as well or use the data store modules to save and get it across scenarios.
Do note that if your scenario takes some time to run, the client will see a blank page until it actually finishes. If you need to use multiple modules in your scenario, you can instead divide it into two scenarios, and use an HTTP module to send the data received from the first webhook to another webhook to process the data in another scenario. The first scenario will respond quickly while the second processes the data “in the background”:
