Not every request is immediate thigh, also you get an ID, so you don’t have to poll. (It’s really just a choice) Zach H.
Kinda... An ID means you still have to poll to get the URL since the URL is really what I'm looking for. A URL would mean that you don't have to poll.
Polling is optional, when you have the ID, it can be saved somewhere. Polling in automations are actually never recommended. It would actually be better for gamma to add a web hook functionality so it can just be sent somewhere when it's finished. But the point I’m trying to make is a URL is literally not generated on every response so there’s no way that could happen at this moment. Zach H. There is no reason to continually poll and waste resources for no reason. I’m not sure how much API work you do, but that’s why most platforms don’t do that anyway .
Yes that would be helpful too Chowderr M..
Providing another input called callbackURL so that when the request is completed, a webhook is sent to that request.
But I disagree that a URL shouldn't be sent back. I can't think of a single scenario where I don't need a URL returned to me.
I mean, I am mostly a builder and API are my specialty so I can say I might be looking at it the wrong way, but knowing how most platforms are built when you don’t get a URL on every generation, there’s a reason. I’m not sure what you’re generated with gamma but I can guarantee that every request does not send a URL and some do it’s probably because of how much can be generated instantly at one time or how small it is some of mine I don’t need to go grab and the ID at all, I already have one. Zach H. web book thing was the first thing I mentioned that Gamma should have hopefully they implement it. I’m not sure what you’re building in but if you need a different perspective, I’d be happy to give you one, but you definitely should not be just polling. That is not something you do and automations in general, it's a serious waste.
