I’m testing a new pattern integrating Auth0’s Event Streams (user.updated specifically) with marketing platform Braze via Braze’s Data Transformation functionality to essentially create a webhook pipeline of near real-time customer updates from Auth0 to Braze.
I’ve got it working to a point where Auth0 is hitting the Braze Webhook, and within Braze the Transformation code is transforming the payload received correctly and subsequently processing the data and storing it in Braze as desired. Great so far!
Problem is that on the Auth0 side, every event attempt is coming back as Failed despite it definitely working ok.
If I click on a failed attempt, it says that the message received / response is:
201 - {“message”:“success”}
I’m not sure i’m able to change the response Braze sends back (although I would have thought this would be ok?).
Is there any suggestions to help me fix this without needing to create a middle layer?
Hello,
It sounds like Auth0’s Event Streams might be expecting a specific HTTP status code for success, or perhaps an empty response body, and 201 - {“message”:“success”} isn’t quite what it anticipates. While a 201 status code generally indicates successful creation, some systems are stricter. Unfortunately, without the ability to modify Braze’s webhook response or configure Auth0’s success criteria, a direct fix is challenging. You could explore if Auth0 offers any options to customize success response parsing for event streams, but if not, a small intermediary service (even a serverless function) might be the simplest way to intercept Braze’s response and return what Auth0 expects, thereby avoiding a “failed” status.
Thanks so much for the response, I really appreciate you guys looking into this.
Acknowledge you can’t provide an exact date however do you have any indication of a rough ETA?
Only asking because this pattern is preferred for a piece of work we’re delivering so just need to know whether we need to go back to the drawing board for a new solution if this fix is going to be more than a few days/weeks away.
Hey @tarik_cipher! I’m one of the engineers who works on this feature. I just added support for 201 yesterday, so you should see this start working as the change rolls out. I can’t give an exact ETA but for public cloud environments this shouldn’t be more than a few days. Private cloud environments would be a bit longer.