Hi @Robwicks1
For us to have more info about the error, post screenshots showing how your Zap step API request is configured in the CONFIGURE tab while in EDIT mode with the field mappings visible.
Also, include the link to the API endpoint documentation you used to configure the API request.
Same problem here. previous zaps are still working, but see “webhook by zapier (1.0.22).
While newly created webhook are “Webhook by zapier * Pro”. These last ones don’t work anymore
it’s a pain in the ass, but only workaround I found is duplicating an existing zap, preciously keep the webhook older version and build around. Enjoy!
This was driving me crazy for long.
On PowerAutomate, after the “http request”, add a “response” step with 200 and body {"status": "Accepted"} so Zapier understands it has to stop trying (in my case it tried twice, so even if it actually well receives data, zapier doesn’t know) Seems by default powerautomate sends a null response
Awesome work, @DavidFed! Thanks so much for sharing how you managed to solve it—really appreciate you giving back to the community here! 🤗
@Robwicks1, hopefully adding a response step as DavidFed mentioned will work for you as well. 🤞 Keep us posted on how it goes, want to make sure this gets sorted!
note that with the response step, without the body “status:accepted” made Zapier to try the call 2 - so creating duplicates on the other end
Hey @Robwicks1, just checking in—did DavidFed’s suggestion help to get things sorted on your end?