Following up – the permanent fix for this issue has been deployed. The root cause was a server-side auth wrapper that was incorrectly validating webhook API keys as session tokens before the webhook’s own auth handler could process them. This has been corrected.
@redefinered-cc @Feier , thanks for confirming it’s working on your end!
@Tomas_Gregovsky, this is the same issue. Please regenerate your auth header using “Generate auth header” on the Automations page and retry with the new token. The fix is live, so it should work now.
If anyone is still seeing 401s after regenerating their token, reply here, and I’ll investigate.