Shopify and Klaviyo: Back-In-Stock Notify Template

On a schedule, check Shopify inventory and fire a Klaviyo back-in-stock event for products that have just been restocked.

What It Builds

This template uses a Schedule trigger to read inventory levels from Shopify on a recurring cron, compares them against the previous run to find products that went from zero to in-stock, and creates a back-in-stock event in Klaviyo for each one. A Condition node keeps the run quiet when nothing has been restocked, so Klaviyo only receives an event when stock genuinely returns. The Klaviyo event is what kicks off your existing back-in-stock flow to email or text waiting customers.

The Prompt

Paste this into Miraxa and it builds the workflow, connecting the tools for you:

Build a workflow that runs every 30 minutes, reads current Shopify inventory levels, and for each product that has just gone from out of stock to back in stock, creates a Klaviyo "Back In Stock" event with the product title and variant so my Klaviyo back-in-stock flow notifies waiting customers. Skip the run quietly if nothing was restocked.

Connectors Used

  • Schedule trigger - runs the check on a recurring cron (for example every 30 minutes in your timezone).
  • Shopify - reads inventory levels via the get-inventory-levels tool.
  • Klaviyo - records the restock with the create-event tool.

Customize It

Change the cron frequency to match how fast your stock moves, swap the event name to match the metric your Klaviyo flow listens for, or add the product handle and price to the event payload so your emails can deep-link straight to the product page.

Tips

  • Use Direct mode on both Connector nodes so each call is deterministic and spends no AI credits.
  • Give the Shopify connection read access to products and inventory, and the Klaviyo connection permission to create events.
  • Run it on a tight loop only if your catalog is small: a 30 to 60 minute cadence keeps you inside API rate limits.

Related

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.