- Trigger automations from Shopify events. Welcome flows, receipts, abandoned-cart drips, shipping notifications.
- Auto-sync customers into your audience. Every Shopify event upserts the shopper into Brew with
shopify-prefixed custom fields (such asshopifyCustomerId,shopifyTags,shopifyAccountStatus,shopifyLastOrderId,shopifyLastOrderTotal,shopifyLastOrderAtandshopifyLastFulfillmentStatus) you can filter and segment on. - Personalize with order context. Reference order totals, financial status, and tracking info inside emails. Order events don’t carry line items.
- Stop maintaining Liquid notifications. Author the same lifecycle flows on the Brew canvas instead.
How It Works
Shopify works like every other event source. Brew gives you a webhook URL and verifies each delivery. Each verified event starts the matching Live automations and upserts the shopper into your audience withshopify-prefixed fields.
Connected-Source Events has the full model.
Two things are Shopify-specific. You create one webhook per topic, all pointing at the same Brew URL. And Brew checks each webhook’s X-Shopify-Shop-Domain header against the domain you registered, so no other store can impersonate your connection.
Setup
This setup uses Shopify Admin webhooks, not a Shopify app. You don’t need a client ID, client secret or OAuth app.1
Generate your Brew webhook URL
In Brew, open Integrations, click the Shopify card, open the Setup tab, and click Generate webhook URL. Copy the URL.
2
Enter your myshopify.com shop domain
In Brew, enter the canonical
myshopify.com host (for example acme.myshopify.com), not your custom storefront domain. Brew matches it against every webhook’s X-Shopify-Shop-Domain header.3
Create a webhook for each topic in Shopify Admin
In Shopify Admin, click Settings (gear icon, bottom-left), then Notifications, and scroll to Webhooks. Shopify sends a topic only to a webhook created for it. A trigger fires only for the topics you add here.For each topic, click Create webhook. Set Event to its name from Supported Events, for example Order payment for
orders/paid. Set Format to JSON, paste the Brew URL, pick the latest API version, and Save.Don’t add Cart update (carts/update): its payload has no recipient email.4
Copy the per-shop signing secret
At the bottom of the Webhooks section, copy the long secret under “Your webhooks will be signed with…”. The same secret signs every webhook on this shop.
5
Paste the signing secret into Brew
Paste the secret and click Connect. Brew verifies every webhook with HMAC-SHA-256 (base64) against the
X-Shopify-Hmac-SHA256 header.6
Send a test from each webhook
Back in Settings → Notifications → Webhooks, open the … menu on each webhook you created and click Send test. Shopify signs it automatically.The first test moves the Shopify integration page in Brew from Waiting for test event to Connected. Each test marks its topic as received in the Shopify events list.A test only verifies the webhook. Brew adds no contact and starts no automation, and Manage → Recent events shows it as Test event.If the page doesn’t connect, recheck the signing secret and the canonical
myshopify.com domain, then reconnect as below.To reconnect after a mismatch or a rotated signing secret, click Disconnect on the Shopify integration page. Then repeat steps 1, 2 and 5.If step 1 shows a different URL from your webhooks, update each webhook. Then send a test (step 6).Reconnecting starts the Shopify events list over.
Supported Events
Connecting provisions every topic below as a trigger in the automation builder. There is no per-topic enable step. A topic fires when it has a Shopify webhook and the bound automation is Live. The Manage tab shows:- Webhook URL: the URL your Shopify webhooks point at
- Shopify events: how many topics Brew has received, and each topic’s status
- Recent events: up to 25 of the newest deliveries that passed the signature check
customers/create(Customer creation)customers/update(Customer update)customers/delete(Customer deletion)customers/enable(Customer enable)customers/disable(Customer disable)
orders/create(Order creation)orders/paid(Order payment)orders/cancelled(Order cancellation)orders/fulfilled(Order fulfillment)
checkouts/create(Checkout creation)checkouts/update(Checkout update)
fulfillments/create(Fulfillment creation)fulfillments/update(Fulfillment update)
Common Patterns
A storefront sign-up, from the account page or Shopify Forms, firescustomers/create and then customers/update about a second later. So welcome new shoppers from customers/create, not customers/update.
Kind follows What You Can Send. Send transactional email, a direct response to something the person did, from a transactional-purpose domain. Marketing email needs the contact’s opt-in, and being synced from Shopify isn’t consent.
Both means the confirmation is transactional and the follow-up is marketing.
checkouts/update and fulfillments/update can fire several times for one checkout or fulfillment. Each fire starts its own run. So start a flow from the create topic and use Waits for the later steps.
Personalization
These resolve as merge tags in the email body, subject line, and preview text. Use a fallback wherever an empty value would read badly, like{{ firstName | there }}. The trigger. prefix reads the same field, so {{ trigger.firstName }} and {{ firstName }} resolve alike; see Namespaces.
Each event declares its own fields, and an automation won’t publish with a tag its trigger doesn’t declare. Use only the variables listed for your event.
Troubleshooting
Shopify sends a topic only to a webhook made for it. To check delivery, usecheck_trigger over MCP. Its delivery.status is one of:
received: Brew has seen the topicnever_received: Brew hasn’t seen itnone_recent: no event in the last 90 dayswaiting_for_test_event: the shop hasn’t sent its first signed delivery
received, delivery.message names the setup step to check. A Send test from the topic’s webhook counts as received. Publishing an automation on a topic Brew has never received still works, with a TRIGGER_EVENT_NOT_RECEIVED warning.
An event arrived but no automation fired
An event arrived but no automation fired
Confirm at least one automation bound to this topic is Live (not Draft). Manage → Recent events confirms the webhook is arriving. A Test event row runs nothing.If the event isn’t there, check the topic has a webhook in Shopify Admin. Also check that the shop domains match.If a real event is there but no email went out, check the automation is published. Then check the contact isn’t unsubscribed or suppressed.From an agent,
check_trigger lists what blocks the trigger, and list_trigger_events shows each event’s match state and its runs.Brew rejects every webhook after you entered a custom domain
Brew rejects every webhook after you entered a custom domain
The shop domain you entered doesn’t match the
X-Shopify-Shop-Domain header on the webhook, so Brew answers every delivery with 401. Reconnect as described under Setup, with your canonical *.myshopify.com host.orders/* emails have empty firstName / lastName
orders/* emails have empty firstName / lastName
Shopify’s January 2025 slim-down removed the inline customer object from some
orders/* payloads. Subscribe to customers/create so the contact sync saves the name, which later order events for the same email reuse. Or trigger on a later lifecycle webhook (orders/paid, orders/fulfilled) that still carries customer fields.Either way, give the tag a fallback ({{ firstName | there }}) for when neither source has a name yet.I want to test before going live
I want to test before going live
Send test only verifies the webhook.Build your automation as a Draft, run a test send from the email editor, then publish it to Live.On an order topic, place a
$0.01 order to your own email through Shopify’s Test payment gateway. It runs the whole flow. The delivery appears in Manage → Recent events within seconds.From an Agent or Code
Connecting Shopify, creating the webhooks in Shopify Admin, and pasting the signing secret are app-only. From an agent or code, the rest is readable and buildable:list_integrationsorGET /v1/integrationsconfirms Shopify is connected to the brand.check_triggerorGET /v1/automations/triggers/{triggerEventId}/readinessshows whether Brew has received an event and which Live automations consume it.list_trigger_eventslists recent deliveries, their match state, and the runs they started.save_automationorPOST /v1/automationsbuilds an automation on any event above, andtest_automationruns it to one address.
fire_trigger_event isn’t used here. A topic reads never_received until a webhook exists for it in Shopify Admin.
Requirements
- A Shopify store on any paid plan
- Admin access to add webhooks under Settings → Notifications
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.