Before you start. You need a verified sending domain and Shopify connected to Brew. Each event below has an automation trigger in Brew. Shopify sends a topic only after you add its webhook in Shopify Admin.Selling app subscriptions instead? The same patterns work with RevenueCat or custom events from your own checkout.
New Shopper
Someone created an account or bought for the first time. Engagement will never be higher, so say hello while they’re still looking at the confirmation page. Send one email. Welcome them and set expectations for what you’ll send. Give them one reason to come back, such as a bestseller, a guide, or a first-order perk. Build this as an automation triggered bycustomers/create. Add a Filter step that lets through only customers who opted in to marketing.
Order Placed
Customers open the order confirmation to check that the order went through. Make that answer clear. Send it onorders/create (or orders/paid if you only want to confirm captured payment). Include the order number, total, and payment status from the trigger payload. Order triggers declare no line items.
Build this as a single-email automation. If the receipt must also reach unsubscribed customers, send it from a domain with a transactional sending purpose.
Transactional-purpose sends skip the unsubscribe footer and deliver to unsubscribed contacts. On a marketing-purpose domain, the same automation respects unsubscribes.
{{ orderNumber }}, {{ totalPrice }}, {{ financialStatus }}. See the Shopify integration for the full variable list, and Merge Tags for the syntax and fallbacks.
Abandoned Cart
Most carts don’t convert. A reminder within a day reaches shoppers while they still remember the cart. Send a 2 to 3 email flow starting about an hour after the checkout is created. Lead with the reminder and a link back, not a discount. Build this as a marketing flow triggered bycheckouts/create. Add a Filter step that lets through only customers who opted in to marketing.
Shipped and Delivered
People open shipping emails to check tracking, often more than once. Delivery is also the right moment to ask for a review, while the box is still on the counter. Send a shipment notification onfulfillments/create with the tracking link. Send the review request on the same event after a Wait of about a week. No Shopify event says the box arrived.
Trigger the review request from fulfillments/create, not fulfillments/update. Each event starts its own run. So if an update arrives more than once for a fulfillment, a customer could get several review requests.
Build these as two separate automations. The shipment notice follows the same unsubscribe caveat as the order confirmation. The review request is marketing, so give it the same opt-in Filter as the welcome email.
Winning Back Lapsed Customers
Customers who bought once and went quiet aren’t gone. They haven’t had a reason to come back yet. If your contacts carry a last-order date, such asshopifyLastOrderAt, filter on it with a fixed date. For example, use a last order before a date 90 days ago. The date doesn’t roll forward, so move it each time you run the win-back.
Save that audience, limited to customers who opted in to marketing, then send a win-back. Use a one-off Email. If you want a follow-up stage for non-openers, use a one-off flow run against the saved audience instead.
Where to Start
If you’re building store emails for the first time, do them in this order:- Order placed: table stakes; every customer sees it
- Abandoned cart: the fastest revenue recovery you can ship
- Shipped and delivered: highest engagement, sets up the review
- New shopper: compounds as your store grows
- Winning back lapsed customers: run it quarterly once the rest are live
From an Agent or Code
Connecting Shopify is app-only. An agent can confirm the connection, and over the APIGET /v1/integrations does the same. Each prompt on this page then works as a message to an agent over MCP:
- The agent makes each design first. It then saves the flow on the Shopify event. Each send node is pinned to one design and a verified domain.
- It can test the flow to one address, and publishing sets it live.
- It can tell you whether Brew has received a given Shopify topic yet.
- For the win-back, it saves an audience filtered on the last-order date and the opt-in field. Over the API,
POST /v1/audiencessaves the same filter. - It then sends the one-off Email to that audience. For a follow-up flow, it points the flow’s manual-audience trigger at the audience and launches the run.
“Has Brew received a Shopify checkouts/create event yet?”
Related
- Shopify: the events, the payload fields each declares (such as
orderNumberandtrackingUrl), and consent. - Transactional Email: receipts and shipping notices that must reach unsubscribed customers.
- Run a One-Off Flow: a win-back with a follow-up stage.
- Merge Tags: the syntax and fallbacks for payload fields.
- Lifecycle Emails for SaaS and B2B: the same approach for software.
Need Help?
Our team is ready to support you at every step of your journey with Brew. Choose the option that works best for you:- Self-Service Tools
- Talk to Our Team
Search Documentation
Type in the “Ask any question” search bar at the top left to instantly find relevant documentation pages.
Ask ChatGPT or Claude
Click here to open the Copy page menu at the top of this page, then send the page to ChatGPT, Claude, or your editor.