Forum Discussion
GET call to backend API in canvas?
PeytonFNMPerfect. I will let you know if I have any other questions on this piece.
On another piece, users enter a canvas through the user_clicked event, decision split determines if they have the event property value "success", and sends them to a webhook endpoint /community-mgmt/{communityId}/bot .
The communityId is an event property linked to the user_clicked event. It's not currently a user attribute since they can have multiple communityIds -- however I need to be able to bring that communityId into the webhook itself. I tried filtering the segment on the event / event property is not null, but adding property filters here is not an option.
Would this be another user update step requirement prior to the webhook? OR if I specify the canvas action trigger user_clicked event where eventValues.community_id is not blank - how do I specify eventValues.community_id in the webhook?
Hi Ashleedolan ! Tag-teaming with my partner PeytonFNM on this one :)
You are absolutely correct about the User Update approach. Unfortunately, it's not possible to split users based on the Canvas Entry Property (the Braze community is looking forward to this becoming a feature one day), so the solution would be to log the Entry Property as a Custom Attribute, then you can split the users using the Audience Path afterwards.
We actually have a Youtube video on how to do exactly this: check it out here!
It also sounds like you'll be using some Liquid to create conditional logic based on what your GET request returns from your BE. The Connected Content approach is correct here. Also happy to take a look if you have some more details/examples!
- Ashleedolan2 months agoCollaborator
Thanks AllanHeoFNM ! Since the event property is being sent to Amplitude-->Braze as eventValues.community_id and the BE endpoint is referencing {communityId} - will there be a discrepancy in mapping the values if they don't match?
Since I have not added the user update step yet- I did attempt to alter the value with liquid in the webhook itself, but that did not work as I expected it would not.- AllanHeoFNM2 months agoVisionary
My guess is that as long as you're referencing using the correct field name when requesting your BE, that should work fine? So if you're requesting from your BE, sounds like you should look for communityId.
Do you mind sharing your Liquid code here?
- Ashleedolan2 months agoCollaborator
Disregard - I got it to work 😅
{{event_properties.${eventValues.community_id}}
Related Content
- 12 months ago
- 3 days ago