2.0 Beta

Smootify 2.0 is in public beta. Your 1.x store keeps working. Move when you want.

What changed
Alerts

Price drop alert

A shopper asks to be told when a variant costs less, and Shopify tells them when it does.

How it runs.

A Webflow form writes a metaobject; Shopify Flow takes it from there.

Workflow 1When the alert is saved

  1. TriggerMetaobject entry created

    For the alert, type price_drop.

  2. Action 1

    Find the customer with the alert’s email, or create them when new (“Send Admin API request”: customerCreate)

  3. Action 2

    Write into the alert the variant’s price of that moment and the customer (metaobjectUpdate)

Workflow 2Every day

  1. TriggerScheduled time

    Once a day: Shopify Flow has no trigger for a price change.

  2. ConditionCheck if
    • For each price_drop alert not sent yet: its variant costs less now than the price saved in it

    Otherwise the workflow stops here.

  3. Action 1

    Get metaobject entries: the alerts, up to 100 per run

  4. Action 2

    Send the email to the alert’s customer, with the old and the new price (the file sends it with a “Send HTTP request” to Resend)

  5. Action 3

    Mark the alert as sent (“Send Admin API request”: metaobjectUpdate)

What you need, and how to install it.

What you need
  • Shopify Flow, free in Shopify
  • Plan: Server
  • Add-on: Metaobject creator
  • Element: metaobject-creator with data-type=alert
  • Metaobject definition alert, private
  • An app that sends emails from Flow, such as Workflow Email, or Flow’s “Send HTTP request” to a service such as Resend (Grow plan and above)

Settings › Custom data › Metaobjects › Alert

AlertMetaobject definition
Typealert
EmailemailSingle line text
TypetypeSingle line textback_in_stock, price_drop, waitlist
ProductproductProduct reference
VariantvariantVariant reference
Accepts marketingaccepts_marketingTrue or falsethe customer’s consent to emails
DatedateDate
SentsentTrue or false
PricepriceDecimalsaved by workflow 1
CustomercustomerCustomer referencesaved by workflow 1
Active-draft status not needed
Storefronts access not needed: the site never shows them

Each field's key is the Name of a field in the Webflow form, written exactly the same.

How to install
  1. Install Shopify Flow from the Shopify App Store. It is free in Shopify, but it is a separate app.
  2. In Shopify, create the metaobject definition alert with the fields below.
  3. Switch on the Metaobject creator add-on in the Smootify dashboard.
  4. Place the Smootify element in Webflow: metaobject-creator with data-type=alert.
  5. Download the .flow file and import it in Shopify Flow.
  6. Add the price and customer fields to the alert definition. Only the workflows write them: the form does not send them.
  7. Import the two workflows: the one on “Metaobject entry created”, then the scheduled one. Both files are below.
  8. In workflow 1, open the trigger and pick your alert definition again: the file names the definition of the store it was made on.
  9. In workflow 2, set the time and the time zone of the schedule (the file runs every day at 9:00, Rome time).
  10. To test, lower the price of a variant with an alert and set the schedule to every hour until the email arrives.
  11. Test it once with a real submission or order, then turn the flow on.

Where people get stuck.

  1. 01

    Remove the tag, or mark the alert as sent, in the same workflow. Otherwise the next run sends the same email again.

  2. 02

    You are collecting an email. The form has to say what you will do with it, and if alerts become a marketing channel, tie them to the customer’s marketing preferences.

  3. 03

    The form needs the Server plan: Smootify’s server creates the entry, not the browser. The definition needs no Storefront access, since the site never shows the alerts.

  4. 04

    Input names must match the metaobject keys exactly. Webflow renames fields when you copy a form, and a wrong name fails without an error.

  5. 05

    The price is compared with the one saved when the customer asked. An alert sends one email: after it, it is marked as sent.

  6. 06

    Each run reads the first 100 alerts, sent ones and other types included: past 100, new alerts are never read. Delete the alerts already sent, or set the query of “Get metaobject entries” to the price_drop alerts not sent yet (turn on filtering for the type and sent fields in the definition).

  7. 07

    The first workflow creates the customer, waits a minute and finds them again to save them in the alert: a new customer is not in Shopify’s search the moment they are created.

Get the .flow file.

In Shopify Flow, choose Import and pick the file. The workflow opens turned off: check that it reads your metaobject definition and its field keys, then turn it on.

Workflow 2 sends the email through Resend with a “Send HTTP request”. In that step, replace RESEND_API_KEY with your Resend API key, set a sender on a domain you verified in Resend instead of alerts@example.com, put your currency symbol in place of €, and in the “Run code” step point the link to your Webflow site instead of www.example.com. To send it with another app, such as Workflow Email, replace the step with that app’s action.

Shopify plan. This file sends its email with Flow’s “Send HTTP request”, which runs only on the Grow, Advanced and Plus plans. On Basic, replace that step with the action of an app that sends transactional emails from Shopify Flow, such as Workflow Email: the rest of the workflow stays as it is.

Related.

Webflow writes.
Shopify reacts.

Forms that write to Shopify are on the Server plan, and Shopify Flow is free in Shopify. One Shopify app, billed on the store’s Shopify invoice.

  • One app on the Shopify bill, not ten
  • Free to build, pay only when you go live
  • Works on Basic, Grow and Advanced
  • Your 1.x store keeps working
  • Every element stays yours to change
  • Docs indexed in llms.txt