That’s exactly it. The context is large, or even limitless. I’d like to use a webhook to a Make scenario.
The idea is based on the Google Sheets add-on from Integromat.
The Fetch column will be based on a Construct URL column, which in turn will bundle all the required parameters from USC and computed columns.
Basic columns, visible to Google Sheets, can be easily handled with the a.m. add-on.
How would it be triggered?
If it’s triggered as a result of a user action, then why not just use a Trigger Webhook action?
It will not be triggered per-se.
Exactly like in the GS add-on, the column would send data to Make and get back results (=response).
In a nutshell:
do this:
By using this:
Between these two modules, the sky is the limit 
hmm, I still don’t think it’s possible, but I could be wrong.
Might leave this one for @ThinhDinh or @Robert_Petitto. Either of them might have a better idea.
I’m trying to play around with something like this:
https://hook.eu1.make.com/1ja4byoq7pkdsuma68gl27s4o9dq2xsg?go=true¶m1=1¶m2=1
It’s a simple scenario:
Assuming “go” is true, it’ll return the sum of param1 and param2.
The scenario is working, but Glide returns no values in the Fetch column.
I don’t recommend this way as it will cost you a lot of operation and this will apply on every user on every refresh which is not feasible over time
3 Likes
Now we’re talking.
We can send anything to Make and it’ll return its magic. For example: create Zoom meetings, schedule events and send back their ID, etc.
Yes, I agree. That’s why I was trying to slightly reduce the cost by setting the “go” parameter.
Can you think of any other way?
I’m still struggling to grasp the point of this.
What would cause your go parameter to change to true?
Limitless…
For example, change to true when we have all the information we need to create a calendar event. Then, Make will send us back whatever info we need on this event, such as it’s ID, URL link to it, etc.
Same idea with anything else. We want to Make scenario to run only when we’re ready. It’s true that the webhook will fire every time we update/refresh the app on Glide (“go” parameter being false). I still don’t know how to avoid or throttle this.
See, this is where I’m getting confused. It’s like I’m asking you what the time is, and you’re replying with “roast potatoes” 
Let me try and pose the question in a different way. The way I see it, if you have a column that can either be true or false, there are only two things that could cause the value to toggle between the two states. Either:
- a user changes a value somewhere, or
- time passes
So is it either (or both) of those, or something else that hasn’t occurred to me?
My thinking was to based true/false on an ITE column.
I agree with this. I still don’t get the overall point of this approach, will need to get a better context to potentially propose a different solution
Okay, but if-then-else what?
What has to change for the if-then-else to change?
Again, it should boil down to one of two things: a user does something, or time passes, or both.
So which?
There is a reason I won’t let go of this, and I’ll explain once I manage to get an answer
If you insist, I guess it’s this option.
ITE will check that all parameters are there for this scenario to run as planned. Yes, it does mean that a user changed (many) things but these things might not be directly connected to this ITE (i.e. another ITE down the line).
I’ll try to elaborate with an example:
A custom form is used to schedule a meeting. Among many other questions, we ask the user if the meeting will be on Zoom. If it is on Zoon, I’d like to present to them the Zoom links (Host and Join) directly on that form. Sure, we can send them this information later on, after they submit the form. The approach I’m talking about here is meant to provide the user with maximum insight while still filling in the form.
Finally.
Okay, so it’s based on user interaction. That’s what I needed to know.
Now my next question is - why have you decided that this somewhat unconventional approach is going to be better than the usual approach of using a Trigger Webhook action, and then writing the result back to Glide via the API?
Here’s one example:
This will happen without asking the user to do anything (click a button, action text, etc.). The data will appear on the screen once it is available.
Okay, fair enough. Well, I’ll be interested to hear how it works out.
Speaking of Fetch:
I find it that sometimes it doesn’t return a result, even when the URL does return a result upon simply following it.
I cannot share an example here as this mainly happens (or so I think) when there’s an API key involved. Open API seem to work flawlessly.
Has anyone faced this?