I’m having trouble with an automated workflow where new email subscribers should be automatically registered in my membership platform (Digital Access Pass). The setup uses a webhook POST request to connect the automation service with the membership system.
The strange part is that the automation platform shows successful webhook delivery in their logs, but the membership system isn’t receiving anything. The membership support team confirmed their script isn’t being triggered since nothing appears in their server logs.
However, when I manually paste the webhook URL directly into a browser, it works perfectly and the data shows up in the membership system logs.
This suggests the webhook URL is correct, but something about how the automation platform sends the POST request isn’t working properly. Has anyone encountered similar issues with webhook deliveries showing as successful but not actually reaching the destination?
sounds like a user agent problem. Membership platforms often block requests with generic or missing user agent headers - they flag anything that looks bot-like. when you paste the URL in a browser, it sends normal headers, but automation tools usually send generic ones that get blocked. check if your automation platform lets you set custom user agent strings in the webhook settings.
Had this exact problem six months ago with a similar setup. Turned out to be the Content-Type header. The automation platform was sending the webhook fine, but wasn’t setting the right Content-Type header that my receiving script needed. Most automation platforms default to application/x-www-form-urlencoded, but membership systems usually expect application/json. Check if your platform lets you customize headers in the webhook config. If not, you’ll need to modify your receiving script to handle different content types, or throw a middleware service like Zapier or Make in between to format the request properly.