Hi! Can't you send the user status as a custom attribute on their Braze profile? That would be the easiest solution. Then, conditional statements take care of the rest.
You can make an API call using the following code:
{% connected_content YOURENDPOINT :save data %}Replace the endpoint and add this to the email template within the canvas. "data" will be an object that contains the response of the API call. If the response is the status, then you can do operations using "data". Otherwise, if the response is a user object, you can say "data.status" to get the variable you need from the object, and so on.
Using conditional statements, you can define what the user sees based on the value of the variable from the API response.
Let me know if this helps.
Hey Ashleedolan! Agreeing with Arso on this one that making a connected content call would be the best option.
For the Canvas setup, you could start with a 2-hour delay after entry. Then, add a user update step that pulls a value from a connected content call. If that value exists, you’d write it to the user’s profile as a custom attribute. From there, you can add a decision split step or audience path step looking for does the custom attribute = X? If yes, they go down Path 1; if no, they follow Path 2.
Thank you. There will actually be a few separate values that we are checking for - could I replace the decision split here with an audience path based on those custom attributes? For example:
AshleedolanYes, absolutely! This will work!
PeytonAllanHeoFNMin the user update step, the docs say tokens/keys arent needed and shouldn't be added. Our endpoint currently requires the users JWT before accessing- can we still dynamically pass this in the header? It says not needed, but also doesn't clarify if you can still pass it if its required so I just want to be clear.
The user update step doesn’t actually need headers. It’s basically a more efficient version of a webhook that sends data directly to Braze using their endpoints. I’d imagine that since it’s specifically designed to send requests to Braze endpoints only, either authentication is built-in, or it functions in a way that doesn’t require it.
Authenticating your backend is a different story, you can handle that within the connected content call instead. Braze has some examples on how to do this—here’s a link that walks through using basic authentication: Braze Docs.
In theory, you would start by making a Connected Content call to authenticate your backend, retrieve the data, and store it in variables if necessary. Then, you would have the JSON object through the advanced JSON editor to update user profiles. Here’s a general example.
Might even be worth throwing the connected content authentication aspect in a content block and then just calling the content block before the JSON.
AllanHeoFNMany other ideas in terms of an approach?
