Has anybody tried to use a webhook action to trigger a webhook workflow?
I suppose / hope I’m not the only one.
Perhaps it’s not meant to be used that way since otherwise Glide would have launched the same functionality in regular workflows?
However I have been bending my mind over one workflow for a day now (which is triggered in a similar manner) and sometimes (starting from the same data in the data editor) it behaves as expected, and sometimes it seems it uses old data.
Is this workflow thing properly debugged for these purposes, or am I doing something wrong here?
Here’s a video of what I’m trying to build + at the end how it messes up
The webhook workflow runs server side, whereas your button workflow runs client side.
It’s most likely that when you set your values and call the webhook, that data has not had a chance to sync back to the server before the server processing runs. I would guess that you maybe need to put a Wait action into your workflow somewhere.
You could add a Wait into your button workflow to wait a number of seconds before calling the webhook, but there would be no guarantee that your data has synced yet before the webhook is executed.
Instead I would probably put a Wait For Condition into the webhook workflow that is called. Set the wait condition to only proceed with the rest of the workflow if all of the needed values are set in the table.
Hey Jeff, thanks for thinking along.
I assume indeed that it’s timing related.
I don’t think the wait for condition is available in the new workflows.
Perhaps I should try to send more data via the webhook itself.
In fact I don’t see why it wouldn’t work just because it’s an internal webhook since I’m not doing anything else in the app apart from monitoring the progress…
Disclaimer: I don’t have access to the new workflows, so I don’t know what’s available or not.
You could try adding a 5 second Wait in the button action before calling the webhook. I don’t really see that as a long term solution though, but it would be interesting to see if everything else works more consistently.
But yeah, if the webhook can do the set column values itself, and the only thing the button does is call the webhook, then that probably would work best.
The insight in the syncing of the backend with frontend seems to do the trick.
I hope it keeps working
Perhaps I overdesigned the wait times a bit but the automated action is worth the wait.
