Notify Me! sends your back-in-stock events straight into Shopify Flow, so you can automate what happens when a shopper subscribes, when an alert goes out, or when someone buys after getting one. This article lists every event, shows the data each one carries, and walks you through building your first workflow.
The integration is always on. There is nothing to connect and nothing to switch on in Notify Me! — as soon as your store has Shopify Flow, the triggers are there. Each event starts flowing the moment you build a workflow on it and turn that workflow on, and stops when you turn it off. Until then we send nothing, so an event you have no workflow for costs you nothing.
Before you start
Your store needs a Shopify plan that includes Flow: Basic, Shopify, Advanced, or Plus. Shopify Starter does not support Flow workflows.
The Shopify Flow app must be installed on your store. It is free from the Shopify App Store.
You need the Notify Me! Back in Stock feature in use — the triggers fire from real subscriber activity, so a store with no subscribers will not see anything fire yet.
Where to find the triggers
In Notify Me!, go to Settings > Integrations and find the Shopify Flow card. It shows a Connected badge. Click Manage.
The page lists every event we expose to Flow under a BACK IN STOCK heading, with the data fields each one carries underneath it. The list is read-only — it is a reference, not a set of switches. You choose which events to use inside Flow itself.
Click Open Shopify Flow in the top right to jump straight into the Flow editor.
The five back-in-stock triggers
Trigger | When it fires |
Back in stock subscription created | A shopper subscribes from your storefront for an out-of-stock product. Imported subscribers do not fire it. |
Back in stock subscription created (Identified customers) | Same, but only when the shopper was signed in to their customer account. |
Back in stock first alert notification sent | The first back-in-stock alert goes out to a subscriber, on any channel. Fires once per subscriber. Reminders do not fire it. |
Back in stock first alert notification sent (Identified customers) | Same, but only when the subscriber was signed in. |
Back in stock order created | A customer orders a product after receiving a back-in-stock alert for it. Fires once per restocked product on the order. |
Two things worth knowing before you build anything on these:
The alert triggers fire once per subscriber, not once per channel. If a subscriber gets both an email and an SMS for the same restock, "first alert notification sent" fires once.
Notification channeltells you which channel carried it first."Back in stock order created" fires once per restocked product. If a customer orders two products they were alerted about, it fires twice — once for each.
What each trigger sends to Flow
Every trigger carries Shop domain and Event timestamp. The rest varies by event.
The Variable column is what you actually pick in Flow. Shopify namespaces the fields when it exposes them: ours come through as partner::<name> and the references Shopify resolves itself come through as shopify::<resource>_id. The names are lower-case with underscores, so the Subscriber count for variant field is partner::subscriber_count_for_variant.
Back in stock subscription created
Field | Variable in Flow | Type |
| Text | |
Phone |
| Text |
Shopify customer id |
| Text |
Product |
| Product reference |
Variant id |
| Text |
Variant title |
| Text |
Variant SKU |
| Text |
Shop domain |
| Text |
Event timestamp |
| Text |
Back in stock subscription created (Identified customers)
Field | Variable in Flow | Type |
Customer |
| Customer reference |
| Text | |
Phone |
| Text |
Product |
| Product reference |
Variant id |
| Text |
Variant title |
| Text |
Variant SKU |
| Text |
Shop domain |
| Text |
Event timestamp |
| Text |
Back in stock first alert notification sent
Field | Variable in Flow | Type |
| Text | |
Phone |
| Text |
Shopify customer id |
| Text |
Product |
| Product reference |
Variant id |
| Text |
Notification channel |
| Text |
Subscriber count for variant |
| Number |
Shop domain |
| Text |
Event timestamp |
| Text |
Back in stock first alert notification sent (Identified customers)
Field | Variable in Flow | Type |
Customer |
| Customer reference |
| Text | |
Phone |
| Text |
Product |
| Product reference |
Variant id |
| Text |
Notification channel |
| Text |
Subscriber count for variant |
| Number |
Shop domain |
| Text |
Event timestamp |
| Text |
Back in stock order created
Field | Variable in Flow | Type |
Order |
| Order reference |
Order name |
| Text |
Product |
| Product reference |
Shop domain |
| Text |
Event timestamp |
| Text |
The Product is the restocked one the customer was alerted about. Everything else about the order — the other line items, the customer, the totals — comes off the Order reference, which Flow resolves for you.
Why there are two of each
The subscription and alert events come in a plain version and an (Identified customers) version. The difference is the shopper, not the event — both fire for the same underlying activity.
The plain version fires for every subscriber, signed in or not. It carries the shopper's email, phone and a
Shopify customer idas plain text.The (Identified customers) version fires only when the shopper was signed in to their customer account. Instead of a text id, it carries a real Shopify Customer reference.
That reference is the whole point. With it, Flow can use customer conditions — tags, order count, lifetime spend, marketing consent — and customer actions like adding a tag. With only a text id, it cannot.
So: use the plain version when you want to catch every subscriber, and the (Identified customers) version when your workflow needs to read or change the customer record. If you build both for the same event, put a condition on one of them or you will run two workflows for every signed-in shopper.
Build your first workflow
In Notify Me!, open Settings > Integrations > Shopify Flow and click Open Shopify Flow. Or open the Flow app from your Shopify admin.
Click Create workflow, then Select a trigger. Search for "back in stock" and pick the Notify Me! trigger you want.
Add your action. The trigger's fields are available as variables anywhere Flow accepts them.
Turn the workflow on. It only runs on events that happen after you enable it — earlier activity will not be replayed.
A few things merchants build with these:
Tag a product high demand when its subscriber count passes a threshold, using
Subscriber count for varianton the alert trigger.Tag a customer waited for restock when they order after an alert, so you can segment them later.
Post to Slack when a subscription comes in for a product you have discontinued.
Add signed-in subscribers to a customer segment, using the (Identified customers) trigger.
Tips
Workflows are not retroactive. Turn the workflow on before the activity you want to catch.
Reminder alerts do not fire the notification trigger — only the first alert for a subscriber does.
Subscriber count for variantis the count at the moment the alert was sent, not the count now.Nothing in Notify Me! needs enabling for a trigger to work — the Connected badge is not a switch, and there is no per-trigger control to find. Turning a Flow workflow on or off is what starts and stops that event.
Turning a workflow off never affects your back-in-stock alerts themselves. Your subscribers keep getting notified exactly as before; only the automation stops.
Troubleshooting
I cannot find the Notify Me! triggers in Flow — check your Shopify plan first. Flow is not available on Shopify Starter, and the Notify Me! Shopify Flow page will tell you if that is the case. If you are on a supported plan, confirm the Shopify Flow app is installed.
My workflow never runs — open the workflow in Flow and check its run history. If there are no runs at all, the event has not happened yet since you turned it on: create a test subscription from your storefront on an out-of-stock product, and check again.
It ran once but the shopper got two messages — that is expected. A subscriber who gave both an email and a phone is alerted on both channels, but the trigger fires once for them.
Notification channelnames the channel that went first."Back in stock order created" ran twice for one order — the customer ordered two products they had been alerted about, and the trigger fires once per restocked product. If you only want one action per order, add a condition on the Order so the workflow acts once.
It runs twice for one signed-in shopper — you have both the plain and the (Identified customers) version of the same event switched on. Disable one, or add a condition.
The customer conditions are greyed out — you are on the plain version of the trigger, which carries a text id rather than a Customer reference. Switch the workflow to the (Identified customers) version.
An order did not fire "Back in stock order created" — we could not tie that order back to an alert we sent. Orders placed with contact details that differ from the ones the shopper subscribed with will not be matched.
Need help?
If a trigger is not firing the way you expect, contact us at [email protected] with your store domain, the workflow name, and roughly when you expected it to run.






