- Home
- Resources
- Integrations
- Notify Me!
Notify Me! Zapier integrationAutomate Notify Me! with Zapier.
Notify Me! on Zapier: 1 trigger, 0 actions, 0 searches. The Notify Me! Zapier integration picks up every shopper who asks to hear when a product is back in stock, and hands that signup to the rest of your tools. Notify Me! starts the Zap; other apps do the work.
Beta app Zapier still marks this integration as beta.
Verified Trustpilot reviews · AI, automation & growth agency
Why connect Notify Me! to Zapier
The Notify Me! Zapier integration turns each back-in-stock request in your store into a starting point for an automation. A Zap (the automation you build on Zapier: one starting event, then one or more steps that run each time) waits for a new signup, then sends it wherever you need it.
Three things you can get from that one trigger. A live demand log: every signup becomes a row in a sheet, so your buyer sees which sold-out products people keep asking for. A heads-up for the team: a message in your chat tool each time a shopper joins a waitlist, useful when a restock decision is pending. And a cleaner CRM: the shopper's details go to your email or CRM tool, ready for your own follow-up.
What Zapier can't do with Notify Me!, since the listing won't tell you. There is no action, so a Zap can't create a waitlist, send the back-in-stock email or change a signup: that stays inside Notify Me!. There is no search either. The single trigger also works by polling, so signups reach your other tools after a short wait, not the second they happen. And Zapier lists the app as a beta.
Still weighing platforms? The n8n vs Zapier comparison sets out the criteria (hosting, pricing model, how much code you want) without a verdict.
Zapier vocabulary in one minute
Seven words come back on this page. Here they are once, in plain English.
- Zap
- The automation itself: one starting event, then one or more steps that run every single time that event happens.
- Trigger
- The event in an app that starts the Zap. Once the Zap is on, Zapier waits for it. Here: a new back-in-stock signup.
- Action
- What the Zap does once it has started: the step that writes, sends or moves something for you, in another app here.
- Task
- The unit Zapier bills: one action your Zap completes successfully. Your plan's monthly number counts exactly those.
- Polling trigger
- A trigger Zapier checks on a timer: it asks the app for new items at a fixed interval and keeps only the unseen ones.
- Instant trigger
- A trigger the app itself reports to Zapier the moment the event happens. Notify Me! has none, so the timer applies.
- Multi-step Zap
- Any Zap beyond one trigger and one action. A second action, a filter or a search makes it one, and it needs a paid plan.
What it really costs
Notify Me! is not a premium app, so it runs on the free plan. And since it only starts Zaps, it never costs a task by itself.
- Premium appNo, free plan works
- Free plan100 tasks a month
- Free plan Zap size2 steps: 1 trigger, 1 action
- Cost of the trigger0 tasks
The New Back in Stock Subscription trigger is free, however often Zapier checks for new signups. What counts is each action that succeeds in the other apps: one row added, one task. A failed action counts for nothing. The free plan gives you 100 tasks a month, two-step Zaps only, and a check every 15 minutes. Log the signup and ping the team in the same Zap, and that's a multi-step Zap on a paid plan, with two tasks per signup.
Connect your Notify Me! account
- 01
Open Apps
In Zapier, go to Apps and click + Add connection. A connection is your Notify Me! account linked to Zapier once, then reused by every Zap that starts from it.
- 02
Pick Notify Me!
Search for Notify Me! in the dialog, select it, then click Add connection. You need an active Notify Me! account on your store before you start, since Zapier can't create one.
- 03
Sign in and grant access
A tab opens on Notify Me!. Sign in and grant Zapier access to the account. If the store belongs to someone else, make sure your login can see its waitlists.
Your first Zap: log demand and alert the team
GoalEvery back-in-stock signup lands in a sheet and pings the team in Slack.
- 01
Pick the trigger
Create a Zap, choose Notify Me! and New Back in Stock Subscription, then pick your connection.
Nothing else to set at this stage.
- 02
Test the trigger
Run the test: Zapier brings back the three most recent signups. Pick a real one, not an empty sample, so the next steps map onto real values.
- 03
Log the signup
Add Google Sheets and choose to create a row. Map the details of the signup into your columns. That's one task per signup.
- 04
Alert the team
Add a Slack step that posts each new signup in your buying channel. A second action makes this a multi-step Zap, so it needs a paid plan.
- 05
Publish
Test each step, read what came back, then click Publish. Only signups made after this moment go through; older ones stay where they are.
The Notify Me! trigger on Zapier
1 event starts a Zap when something happens in Notify Me!. Zapier checks for them at the interval your plan allows.
New Back in Stock Subscription
Polling triggerIn Zapier“Triggers when a customer signs up to be notified when a product is back in stock.”
Starts your Zap each time a shopper asks to be told when a sold-out product returns, carrying that request into the next steps so another app can log it, count it or pass it to your team.
When it breaks
Zapier ties no help article to Notify Me!, so the known failure points are the ones every Zap shares.
Four of them matter for a waitlist Zap. If one stops you, the Zapier troubleshooting guide walks through the fixes, and the Zapier review puts the tool in context.
Existing waitlists aren't imported
A Zap only reacts to signups made after you switch it on. Everyone already on a waitlist stays out of your sheet; moving that backlog is a separate job.A loop that drains tasks
If a later step writes back into the place your trigger watches, the Zap keeps setting itself off and eats tasks fast. Keep the output elsewhere.A rush of signups held back
When a viral product sells out and the trigger suddenly returns a huge batch, Zapier's flood protection can hold it back instead of running every one.Each signup counted once
Zapier remembers which signups it has already seen on this polling trigger, so the same request never starts the Zap twice.
Need help automating Notify Me! with Zapier?
A person reads every message.



