Emails & Shopify Flow
These are two separate systems, and they are easy to mix up. The short version:
- To change what an email says, who it comes from, or how it looks, use Listify. Go to Settings → Emails & notifications.
- To make something else happen when a registry event occurs, use Shopify Flow.
Shopify Flow does not edit the registry emails. It has no screen for changing their wording. Flow runs alongside those emails, reacting to registry and wishlist events so it can tag a customer, add them to a segment, post to Slack, or send the details to another service.
Customising the registry emails
Everything here lives under Settings → Emails & notifications.
| Page | What it controls |
|---|---|
| Templates | The subject line and body copy of each individual email. |
| Branding | Your logo, colours, and the overall layout. |
| Sender identity | The name your emails arrive from. |
| Notifications | Which emails send at all. Turn individual ones off. |
The emails we send
| When it sends | |
|---|---|
| Registry created | A shopper creates a registry |
| Purchase notification | An item is bought off the registry |
| Closing reminder | Shortly before the event date |
| Event closed + summary | A wrap-up after the event ends |
| Weekly digest | A weekly activity summary for the owner |
| Inactivity nudge | Re-engages owners with stale registries |
| Guest invitation | Invites guests to view a registry |
| Co-registrant invite | Invites a partner to co-manage the registry |
| Access request | Someone requests access to a registry |
| Verification code | A one-time code for signing in |
The first six go to the registry owner, the next three relate to sharing, and the last one is a security code.
Sending the guest invitation, co-registrant invite and access request from your own tool
On Pro, three of these emails can be switched off so your own email tool, such as Klaviyo, sends them instead: Guest invitation, Co-registrant invite and Access request. Switch them off on the Notifications page, or with Send this email in the template's side panel; both are the same switch. Below Pro the switch is locked and Listify always sends all three.
Off means off. While one of them is off, Listify never sends that email, and nothing is sent later when you switch it back on. Each invitation or request still goes to your webhooks and Shopify Flow, which is where your tool picks it up:
| Webhook topic | Shopify Flow trigger | |
|---|---|---|
| Guest invitation | registry.guest_invited | Registry guest invited |
| Co-registrant invite | registry.co_registrant_invited | Registry co-registrant invited |
| Access request | registry.access_requested | Registry access requested |
The Notifications page tells you whether a webhook or a turned-on Flow workflow receives each one. If neither does, switching the email off asks you to confirm first, because until you set one up those invitations or requests reach nobody.
A guest invitation arrives once for each guest, with the guest's email (guest_invite.email on the webhook, Guest email in Flow), the email the registrant sent it from (guest_invite.sender_email, Sender email), their personal message (guest_invite.message, null when they wrote none; Personal message, empty), and whether the registrant sent it to their own address (guest_invite.is_self_send, Is self send). Its link is guest_invite.url on the webhook and Guest URL in Flow: the same registry link our email carries. Send the guest that link, never the registry's share_url: share_url opens a password-protected registry without its password, while the guest link asks for it, as our email does.
The limits on our email hold with it off too: at most 10 guests per send, and 25 invitations per registry, 100 per sender email and 2,000 per store in any 24 hours. Registry shared still fires once per share, however many guests it went to, whether or not the email is on. It does not fire when the registrant only sent the invitation to their own address: that reached no guest. Registry guest invited still fires for it, with Is self send true.
A co-registrant invite carries the co-registrant's email and name (co_registrant.email and co_registrant.name on the webhook), and two links:
- Manage URL (
co_registrant.manage_urlon the webhook, Manage URL in Flow): opens the registry and asks the co-registrant to sign in. Signing in with the invited email accepts the invitation. - Accept URL (
co_registrant.accept_url, Accept URL in Flow): empty (nullon the webhook). It would sign the co-registrant in without a code, so we fill it in only for a store that asks us to turn on sign-in links. If you need it, write to support.
A co-registrant who signs in to your store with the invited email, by email code or with their customer account, is recognised as co-registrant whether or not an invitation reached them. The same address is invited once per registry; the registrant can resend a pending invitation from their registry.
An access request carries the email the guest entered (access_request.requester_email on the webhook, Requester email in Flow), and a link that opens the registry without its password: the registry's share_url on the webhook, Unlock URL in Flow. Send that link only to the registrant.
Anyone with a registry's link can submit the request form, so access requests reaching your webhooks and Flow are limited: once per guest per registry an hour, and at most 10 per registry an hour, whoever asks. With the email on, Listify still sends its email for every request. With it off, a guest's repeat within the hour is not passed on again, and once a registry has had 10 requests in the hour, further guests are told their request did not go through.
What Shopify Flow is
Shopify Flow is an automation app made by Shopify. Every workflow is the same three-part sentence:
- Trigger — the event that starts it. This is where Listify plugs in.
- Condition — an optional rule deciding whether to continue, such as only when an order is over a certain value.
- Action — what actually happens. Tag the customer, add a note, send a message, call an API.
Flow is free and available on any paid Shopify plan, but it is not installed by default. If you have never used it, install it from the Shopify App Store first. Until it is installed, none of the Listify triggers below will appear anywhere.
Connecting Listify to Flow
There is nothing to pair, authorise, or switch on inside Listify. Once both apps are installed, our triggers appear in Flow on their own.
- Install Shopify Flow from the Shopify App Store, if you do not already have it.
- In your Shopify admin, open Apps → Flow, then Create workflow.
- Click Select a trigger and search for
Listify. - Pick the trigger you want from the list below.
- Add a condition if you need one. Skip it and the workflow runs every time.
- Add your action.
- Turn the workflow on. It stays off while you build it, and switching it on is also what tells Listify to start sending that event. A workflow left off will never fire.
Available triggers
Registry
| Trigger | Fires when |
|---|---|
| Registry created | A registrant creates a new registry. |
| Registry gift purchased | A gifter purchases an item from a registry. |
| Registry gift refunded | A gift purchase on a registry is refunded. |
| Registry event upcoming | A registry's event date is approaching. |
| Registry milestone reached | A registry crosses a funding threshold of 50%, 80%, or 100%. |
| Registry items changed | Items are added to or removed from a registry. |
| Registry shared | A registrant shares their registry by email: once per share, however many guests it went to. Not when they only emailed it to themselves. |
| Registry guest invited | Once for each guest a registrant invites to their registry by email, with that guest's details, their own address included (Is self send true). |
| Registry co-registrant added | A co-registrant email is set on a registry for the first time. |
| Registry co-registrant invited | A co-registrant invitation is sent or would be sent: a co-registrant is added or changed, or the invite is resent. |
| Registry access requested | A guest asks to see a password-protected registry. |
| Registry settings changed | A registrant updates their registry settings. |
| Registry closed | A registry is closed after its event date. |
| Registry re-opened | A closed registry is re-opened. |
| Registry deleted | A registry is deleted. |
| Registrant identified | A registrant signs in and their registries are linked to a Shopify customer. |
Every registry trigger also sends the registry's Event type, Event date and Registry URL, a link to the registry page.
They also send Is private and Is password protected, each true or false. A private registry is hidden from registry search, but anyone with its link can still open it. The password itself is never sent, and the Registry URL never skips it. One field does: the Unlock URL of Registry access requested opens a password-protected registry without the password, so send it only to the registrant.
Wishlist
| Trigger | Fires when |
|---|---|
| Wishlist created | A customer creates a new wishlist. |
| Wishlist item added | A customer adds an item to their wishlist. |
| Wishlist item purchased | An item from a wishlist is purchased. |
| Wishlist deleted | A customer deletes their wishlist. |
| Wishlist owner identified | A wishlist owner signs in and their wishlists are linked to a Shopify customer. |
Every trigger, registry and wishlist alike, also sends Is test: true when the event comes from test data, false when it comes from a real shopper. See the next section.
Test data and the Is test field
Listify runs your workflows for test registries and wishlists too, the same as for real ones, and marks them with Is test set to true. Earlier, test data did not run workflows at all, so a workflow tested with your own registry showed no runs.
Is test is true on a registry trigger when any of these apply:
- The registry's email is the email address on your Shopify account.
- The registry's email is on your store's domain: your
myshopify.comaddress or your own custom domain. - The registry's email is a Listify team address, used when our team tests something on your store.
- The registry was created in the 48 hours after you last installed Listify. A registry created before a reinstall counts as real.
Registry gift purchased and Registry gift refunded are also true when the gift's order matches: the gifter's email meets one of the email rules above, or the order was placed in the 48 hours after you last installed Listify.
On a wishlist trigger, only the email rules apply, checked against the wishlist owner's email. The 48-hour rule does not apply to wishlists, and Wishlist item purchased does not look at the buyer.
To keep test data out of a workflow, add the condition Is test is false. Everything else then runs only for real shoppers.
Sending a test event
You can run your workflows without creating a registry or placing an order. Go to Settings → API & Shopify Flow → Shopify Flow and click Send test event on the trigger you want. Every Listify trigger, registry and wishlist, has its own button.
- Any workflow on that trigger that is turned on runs for real, with sample data and Is test set to
true. Check the result in the workflow's run history in Shopify Flow. - The sample uses
example.comemail addresses, so a workflow that emails the registrant, gifter or owner reaches nobody. - Triggers that point at a product, order or customer use a real one from your store, because Flow looks those up in your store and cannot use a made-up one. An action on that product, order or customer, such as tagging the customer, acts on the real record. Add Is test is false to those workflows before you send a test.
Which triggers need what:
| Trigger | Uses |
|---|---|
| Registry gift purchased, Registry gift refunded, Wishlist item purchased | Your newest registry order (or wishlist order, if you have no registry orders) and the newest product added to a registry (or wishlist) |
| Wishlist item added | The newest product added to a registry (or wishlist) |
| Registrant identified, Wishlist owner identified | A recent registrant (or wishlist owner) who has signed in and is linked to a Shopify customer |
If your store has nothing to use yet, nothing is sent and the page tells you what is missing:
- "This trigger needs a real product. Add a product to a registry or wishlist first."
- "This trigger needs a real order. Send it once a gift has been bought from a registry or wishlist."
- "This trigger needs a real customer. Send it once a registrant or wishlist owner has signed in."
If Shopify Flow refuses the event, the page says so, with Flow's reason when it gives one.
Guests, and why some actions need care
Registries and wishlists can be created without a customer account, so a lot of the people your workflows run for are not Shopify customers at all.
Because of that, every trigger sends the owner's email address and name rather than a Shopify customer, and workflows run for those shoppers exactly as they do for signed-in ones.
The email is empty when the registry or wishlist has none, for example one created in the Listify admin or imported, and the workflow still runs. The one exception is Wishlist created, which does not run for a wishlist with no email and no linked customer.
Each trigger also sends a Customer id. It is 0 when no Shopify customer is linked, so a condition of "Customer id is greater than 0" separates signed-in shoppers from guests.
Actions that act on a customer record, such as adding a tag or adding someone to a segment, need a real customer, which a guest does not have. Build those on Registrant identified or Wishlist owner identified instead. Both fire the moment a shopper signs in and their registries or wishlists are linked to a customer.
To turn more shoppers into customers, turn on "Create a Shopify customer record when a shopper signs in by email" in Settings → Store → Customer accounts, and grant the permission it asks for.
What your plan includes
| Plan | Included |
|---|---|
| Starter and above | Turn individual emails on and off, except the guest invitation, co-registrant invite and access request |
| Growth and above | Edit email content, branding, and sender name |
| Pro | Everything in Growth, plus the Shopify Flow triggers, API access, and switching off the guest invitation, co-registrant invite and access request |