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 

Hey ​@phgdl 

Just wondered if my advice above helped at all - were you able to achive what you wanted?

Thanks,

Ross

Creating a custom event could pull in the attributes that are needed, but ​@ross_hopkins how do you obtain the Delay When back in stock action from a custom flow? I only see that it is available from a Notify When Back in Stock flow template. 

Hi ross_hopkins,

I tried to create a custom event/metric for it, and I was able to send custom data like the color, but I found some issues:

1 - The attribute only was displayed in the Trigger section, Which is not the ideal, since I want to accept all the emails into the list, and wait until we match the criteria to trigger the emails, I believe the ideal should be having these conditions after adding the emails in a waiting list.

2 - Like mathicks mentioned, if it's not a back-in-stock out-of-the-box, we don't have the Timing "Back in stock delay" option, so we were not able to set a proper waiting list/trigger.

3 - I believe that passing the product ID or variant, is could not be linked to the product, I tried in different ways.

To add more context: 
As we sync the catalog, the ideal should be to compare the value with the attribute of the product in klavyio.
Ex: product has color green and 10 in stock.
It should trigger the BIS only if the color is blue and there are 10 in stock.
This "color" is just an example.

Thanks

Hi ​@phgdl,

I just read over this thread, and I wanted to take minute to clarify the expected behavior our endpoints and the back in stock flow. Unfortunately, I don’t have a workaround or solution to provide - apologies in advance for this. That being said, I wanted to make sure your questions were answered.

1. You mention that the custom data, like color, was only displayed in the trigger section. I’m assuming you’re referring to trigger filters, correct? If it’s showing up in the trigger filters, I’d imagine that it would also show up in trigger splits, when you add them into the flow below the trigger. Is this not happening?
2. You’re correct about this. For a flow to have a back in stock delay in it, it either needs to be triggered by Klaviyo’s native Back In Stock feature, or by API, via the Create/Create Client Back In Stock Subscription event. Unfortunately, a regular event can’t trigger a flow with the back in stock delay in it.
3. When you say that the product ID or variant can’t be linked to the product, what are you referring to? If you’re using a custom event to pass data into Klaviyo, you can pull the product ID or variant ID from the product page, and have that pass through in the event data. Let me know if I’m misunderstanding your question here!

Again, I recognize that this isn’t exactly a solution, but I did want to help provide some concrete info regarding what you’re working on. Let me know if you have any questions, and best of luck!

-Byrne