Hey @benhbell 

from what I know - Currently, Klaviyo doesn't have a built-in feature that allows you to branch a flow directly based on the success or failure of a webhook. This type of conditional logic isn't supported natively within Klaviyo's flow builder. 

however @kaila.lawrence @stephen.trumble can confirm this.

I hope this helps and thank you for being part of this amazing community

Best,
Arpit

In Klaviyo, branching off based on the success or failure of a webhook isn't a built-in feature as of now. However, I understand how useful this would be, especially for automating responses depending on whether a webhook call was successful or not.

Currently, to work around this, you could consider the following approach:

Option 1: Use an External Service
1. Webhook Service: You can use an external service (like Zapier, Integromat, or a custom server) to handle the webhook. This service can process the webhook and then send a response back to Klaviyo.
2. Conditional Logic in External Service: Based on the success or failure of the webhook call, the external service can trigger different actions (like sending data to different Klaviyo lists or triggering different flows).
3. Back to Klaviyo: The external service can then make a new request to Klaviyo to trigger the appropriate follow-up actions.

Option 2: Manual Tagging & Segmenting
1. Manual Check: If the webhook has a way to update Klaviyo with its status (e.g., success or failure), you can manually tag users or update profile properties based on that status.
2. Flow Branching: Once the profiles are updated with this status, you can create branches in your flow based on the tag or profile property.

Option 3: Feature Request
If these workarounds don't suit your needs, I would recommend submitting this as a feature request to Klaviyo’s team. They are always looking for ways to improve the platform, and your suggestion could help enhance their flow-building capabilities.

I hope, this will helpful for you.

Hi @benhbell 

To add to the comments above, Webhooks do create profile events, which can be used to trigger a flow. 

I’ve checked my flow webhooks and I don’t have any that have failed. However, the successful ones capture the metric ‘Webhook Send Successful’ and its dimensions.  I suspect it also captures a similar event when it’s not successful.

So, with this approach, although you won’t be branching within the flow where the webhook is fired, you can use it to trigger separate flows(s)

Hope that helps with your use case.

Andy