Hey @emmanuel, I want to revive this thought and see if it’s something you guys can easily add…
Can we add the ability to “get data from URL” within the API Workflows area?
One use case is the original question in this post, but from what I understand his payload was fully sent in the URL, so there were workarounds. I have another use case when retrieving a webhook from an external shopping cart service. The issue is that the webhook payload does not include user account info, so we have no way of knowing whose data is coming in.
If we can have our users set up their webhook configuration with the endpoint plus an identifying parameter that contains their Bubble unique id (or something), we can then read that parameter as well and know whose shopping cart the data is coming from.
Part of this issue is the limited webhook data and the fact that the service itself has no API to begin with. Seeing as "get data from URL " inside API workflows would solve this issue for us completely (not to mention provide @thomas.schijf a much cleaner solution for his original question), it might be worth adding? If possible…?