Skip to main content

Hi there,

I've a bigcommerce integration and I’m setting up an additional condition besides inventory to trigger the Back in Stock (BIS) flow.
I need the emails to be sent only if the variant has a specific additional attribute, besides the inventory.
However, the options I’m being shown are only top-level attributes, not additional variant attributes — like VariantId, for example.
How can I, if possible, add an additional attribute to use as a condition in the BIS flow?

Example:

Color: blue

How can I filter in the flow to trigger only if the color is blue, in addition to inventory?

I'm using this endpoint:
https://developers.klaviyo.com/en/reference/create_client_back_in_stock_subscription

Thank you.

This is what I'm sennding:
 


I didn't see that option to send meta or any other attribute in this endpoint, however, I tried a lot of things.
 

The result:
 

 

 

The product section where I wanted to get the info to use in the flow condition:
 



Where I wanted to see that attribute:
 

 

Color attribute is just an example*

 

Hey phgdl,

I haven’t used that API endpoint before, but I notice that nowhere within that page does it suggest that you can send through custom event properties or set profile properties to store the same data. Having worked with other API endpoints, the option to build a payload on the documentation pages with custom properties is usually present.

The alternative approach would therefore be to setup your own custom “Back In Stock” metric (event). Is that something you have access and the skillset to do? As you’re sharing JSON payload examples I would assume that it’s a possibility, and you’ve got the structure right. If you could do this, you could include any data from BigCommerce within the payload and create an alternative Flow that triggers off your custom event.

If that sounds complex, one thought that comes to mind is to use a middleware platform, such as Zapier. You could connect your BigCommerce account and when the Back In Stock event happens there, trigger a “Zap” that creates the custom event with the necessary data as described in the previous paragraph.

Let me know what you think!

Ross 


Reply


OSZAR »