We have a need to build a webhook on Retool Workflow which takes POST instead of GET.
Cannot find relevant resources anywhere. Shall you point us in the right direction if it is possible?
Is this what you're looking for? in short, if you set a workflow to run from a webhook it already accepts POST requests w application/json as the body
Unfortunately it doesn't work:
curl -X POST https://retool.com/webhook_url
-H "Content-Type: application/json" -d '{"username":"xyz","password":"xyz"}'
Hey @Kwun_Ng, as @bobthebear mentioned, this definitely should work. Just tested this out and was able to log the data passed in via cURL.
When you grab the webhook url, can you try to copy as cURL and then add the data in?
Hi joeBumbaca,
Indeed it works when using the normal webhook url with X-Workflow-Api-Key. But it doesn't work as expected when using the alias public url - it only logs the "Test JSON parameter" but not the real data input there.
1 Like
oh wow that's interesting. @joeBumbaca if you delete the test json data, deploy, then send the public alias webhook url the post request including all the required parameters. the workflow will fail claiming none of the parameters exist.
1 Like
Understood, yes this does look like a bug on our end with the Public Alias enabled. I've submitted a report to the workflows engineering team and will update you both here when I have any information on an ETA for a fix here.
2 Likes
@joeBumbaca would love to follow up as it is blocking us from moving forward. Thanks!
@Kwun_Ng Unfortunately, I don't have any updates right now. I'll ping this thread as soon as I have any additional information to share.
I'm using alias endpoint for the workflow trigger, when I send to request to this endpoint the data is empty but when I send to request to the base endpoint it works fine. Is this a bug?
Hey everyone this should be resolved on cloud, edge release 3.73 and stable release 3.52.11. Have a great day!