Tag notify-me signups by the product they want
Notify-me requests create a Kit subscriber tagged with the product, ready for a single restock broadcast.
New "notify me" form submitted
Add the subscriber to a Kit form and apply a product-specific tag
One-directional. A submission triggers the action — nothing is written back into your form.
A sold-out product page collects intent that expires. Someone wants the navy version back in stock; two weeks later they have bought it somewhere else. A product tag is what lets you email them on the day it returns instead of burying the news in a monthly newsletter.
Small shops and digital sellers use this for restocks, new colours and release dates. One list, many tags: each broadcast reaches only the people who asked about that item, and everyone else is left alone.
Setting it up
- 1
Publish the pre-order form on the sold-out product page, cut back to Full Name, Email Address, Product or Variant, Quantity and Notifications. Shipping details can wait until the item is actually back.
- 2
Make Product or Variant a fixed list of options rather than a free-text box. The tag names in Kit have to match something predictable, and typed answers will not.
- 3
In Kit, create one tag per product, named the same way as the dropdown options — notify-navy-tote, notify-print-run-two — so the mapping stays readable a year from now.
- 4
In Zapier, set the New Submission trigger to this form and pull a sample submission.
- 5
Add Kit's Add Subscriber to Form action, choose the shop's Kit form, and map Email Address to the subscriber email with Full Name to first name.
- 6
Add a Zapier path or lookup table that turns each Product or Variant answer into the matching Kit tag, then a second Kit action, Add Tag to Subscriber, reading that value.
- 7
Map Quantity and Notifications to Kit custom fields so an unusually large request is visible before you write the restock email. Keep this as an interest form, or add hosted checkout if the stock is ready to sell.
- 8
Submit one request for each product option, check every tag landed on the right subscriber record, then switch the Zap on.
What maps where
Using the Pre-Order Form as the starting point. These are its real fields — swap in your own and the mapping works the same way.
| Form field | Kit (ConvertKit) |
|---|---|
| Full Name | Kit subscriber first name |
| Email Address | Kit subscriber email address |
| Product or Variant | Kit tag for that product, chosen by a Zapier path or lookup table |
| Quantity | Kit custom field: quantity_wanted |
| Notifications | Kit custom field: notify_preference |
Variations worth knowing
Apply a general notify-me tag beside the product tag. The product tag drives the restock email; the general tag tells you how many people are waiting on anything at all, which is the number worth looking at before placing a reorder.
Kit has no view of who bought. Once the broadcast has gone out, bulk-remove the product tag in Kit so the next restock does not email the same people twice, and keep the general tag on the ones who never came back.
If something isn't arriving
The Kit action was given a fixed tag instead of the mapped value. Check the path or lookup step actually outputs a tag name, and that Add Tag to Subscriber reads from that step's output rather than from the dropdown default.
Free-text answers in Product or Variant fall through the lookup into whatever catch-all you set. Change the field to a fixed list of options, then correct the affected subscribers using the original answers in the responses view.
Frequently asked questions
Can shoppers pay to reserve the item on this form?
Yes. Add products and priced options to the form, then collect payment through secure hosted checkout with Stripe, PayPal, or Square. Payment status is tracked alongside the response.
How many product tags is too many?
Kit imposes no practical limit, but a tag for every variant becomes unmanageable quickly. Tag at the level you would actually write an email about — a product line or a release — and keep the exact size or colour in a custom field.
Does the tag come off when the product is back?
Not by itself. Nothing is written back from Kit into the form, and Kit cannot see your stock levels. Remove the tag in bulk after the restock broadcast, or leave it in place as a record of who asked and roughly when.
Related automations
- Add newsletter signups as tagged Kit subscribers
A signup on your site lands in the Kit form you chose, carrying a newsletter tag and the topics the reader picked.
- Deliver a lead magnet with a Kit sequence
An ebook request drops the reader into a Kit sequence that sends the download link and nurtures from there.
- Send webinar registrants into a Kit reminder sequence
Registrants land in a Kit sequence that confirms the booking and sends reminders before the session starts.
- Tag course waitlist signups in Kit
Waitlist signups arrive in Kit tagged course-waitlist, ready to email as one segment on launch day.
- Tag customers who opt in when leaving feedback
Feedback submissions with the follow-up box ticked add the customer to Kit with a left-feedback tag.
- Add buyers to a customers list after each order
Each order form submission adds the buyer to a Customers list in Constant Contact for updates and repeat-purchase emails.
Build the form first
The automation needs somewhere to fire from. Publish a form, connect it once, and every submission from then on runs this flow.
Start free