Open Automations in the left sidebar and pick the Gallery tab, the second one along. A recipe is an automation somebody already built for you: its trigger, its messages and its wiring are all in place, and installing it copies that whole flow into your account. The page says what it is for in one line — Ready-made automations — install one, fill in the blanks, review and publish. Nothing you install is switched on: every recipe arrives as a Draft, and the point of the draft is that you read it before anybody receives anything.
Installing a recipe runs the same import a shared .automation.json file runs. Every internal id is renumbered for your account and anything account-specific is stripped on the way in, which is why the installed copy is yours to rename, rewire and delete like a flow you drew yourself. No link back to the gallery is kept either — a recipe that changes later never changes a copy you already installed.
What the Gallery tab shows
Every recipe is a card: an icon, its category in the top corner, the name, one paragraph describing what it does, and an Install button. Recipes that build more than a single workflow carry a second small badge under the category — that badge is the most useful thing on the card, and the next section explains it.
The categories are Sales, Growth, Retention and Support. They label the card and nothing more: there is no filter and no search on this tab, so the whole catalogue sits on one screen.
Gallery carries no plan check at all — it sits in the tab strip ahead of the tabs that do have one. So you can browse and install on any plan, and what a recipe installs behaves exactly as it would if you had built it by hand: a recipe that installs a sequence leaves a sequence in your account, the same one the Sequences tab would have made.
Installing one
Click Install on the card
A small Install recipe dialog opens, with the card's description at the top so you can re-read what you are about to create.
Name it
Automation name arrives filled with the recipe's own name. Change it to something you will recognise in a list of thirty — the name is what you will search for later. Install stays disabled while the field is empty.
Fill in the blanks
Under the name sit the two or three values only you can supply — a Trigger keyword, a Link to deliver, a Tag to apply. Some arrive with a suggested value; the ones that arrive empty are empty because there is no sensible default. Fill them in, because nothing checks that you did.
Click Install
The recipe is created and you land straight in it: the Workflows editor on the flow it installed, or the Sequences tab for a recipe that only installs a sequence. A toast confirms it — Recipe installed — review it and publish.
The recipe installs as a draft. Open it, pick the channel it runs on, adjust the messages, and publish when ready. Each install runs on one channel — install the recipe again for each additional channel. The last sentence is the one people miss. An automation belongs to one connected account, so one install answers on one channel. If you want the same keyword answering on WhatsApp and on Instagram, install the recipe twice and bind each copy to its own account.
The only field the dialog insists on is the name. Leave a Trigger keyword empty and the installed trigger has no keyword, no intent and no match-all switch — so it matches nothing, ever, and the flow sits Live and silent. Leave a Link to deliver empty and the message goes out with a gap where the link should be. Neither shows an error at install time.
The three kinds of recipe
The badge on a card tells you how many things the install is about to create. This matters more than the category does, because it decides where you go looking for what you just installed.
| Badge | What installs | Where it lands |
|---|---|---|
| No badge | One workflow — a trigger and its chain of nodes. | The Workflows list, opened in the editor. |
| Drip sequence | One sequence, with its steps and its timing already seeded. No workflow at all. | The Sequences tab. It will never appear under Workflows. |
| Flow + sequence | The sequence first, then a workflow whose Enroll in Sequence node already points at it. Wired together at install time, not by you. | Both. The editor opens on the flow; the sequence is on the Sequences tab. |
On a Flow + sequence recipe the name you type goes to the sequence. The workflow is named after it: the pattern is {0} — entry flow, with your name in place of {0}, so the pair sits together when you sort by name. Worth knowing before you go hunting for a workflow under the name you typed and find only the sequence.
What ships in the gallery today
Eleven recipes, in the order the tab shows them. The catalogue moves, so treat this as an orientation rather than a contract — the card in the product is always the current description.
| Recipe | What it installs | What it needs from you |
|---|---|---|
| COD order confirmation · Sales | One flow: a Shopify order is placed → is it cash on delivery? → ask the buyer to confirm → tag them as pending. | The Shopify connector, and a tag name (suggested: cod-pending). |
| Comment-to-DM · Growth | One flow: an Instagram post or reel comment carrying your keyword → a DM with your link → a tag. | An Instagram account, your keyword and the link to deliver. |
| Lead magnet delivery · Growth | One flow carrying three triggers on the same keyword — WhatsApp, Instagram and Messenger → deliver the link → a tag. | Your keyword and link. One install still answers on one channel. |
| Birthday & key dates · Retention | One flow on a date field, firing at 09:00 and repeating every year → a greeting → a tag. | The key of a date field on the contact (suggested: birthday). |
| NPS pulse + detractor rescue · Retention | One flow: a tag starts an AI agent that asks for a 0–10 score, then branches — 0–6 apologises, alerts the team and opens the conversation; 7–8 asks what to improve; 9–10 gets your review link. | Your review link — and the survey tag, which you must pick after installing. See the warning below. |
| Comment triage (complaint rescue) · Support | One flow with an Instagram and a Facebook comment trigger, matched by AI on meaning rather than keywords → a public reply → a private message → the conversation opens in your inbox → the team is alerted. | Nothing to fill in. An Instagram or Facebook account to bind it to. |
| Welcome series · Growth · Flow + sequence | A five-step onboarding sequence, plus the flow that enrols every newly created contact into it. | Nothing to fill in. Each sequence step still needs a sending account. |
| Abandoned cart recovery · Sales · Flow + sequence | Three things, not two — see the next section. | The Shopify connector and the browse pixel. Each sequence step still needs a sending account. |
| Abandoned checkout recovery · Sales · Flow + sequence | Three things — see the next section. | The Shopify connector. Each sequence step still needs a sending account. |
| Browse abandonment nudge · Sales · Flow + sequence | Three things — see the next section. | The Shopify connector and the browse pixel. Each sequence step still needs a sending account. |
| Reactivation drip · Retention · Drip sequence | A four-step email win-back on its own — day 0, then 15, 30 and 45 — with a 30-day cooldown before anyone repeats it. | You decide who enrols, afterwards, from the sequence's own panel or with an Enroll in Sequence node. |
Its own description ends with the instruction: IMPORTANT: after installing, open the trigger and pick the tag that starts the survey. The installed trigger is even named ⚠ Pick your survey tag. Take it literally. A tag trigger with no tag chosen means any tag, so publishing this recipe as it installs would survey every contact who receives any tag at all — including tags your other flows apply automatically. A template cannot carry a tag from someone else's account, which is why this one blank has to be filled by hand.
The store-recovery recipes install three things each
Three Sales recipes win back a Shopify shopper who stopped short of buying, one for each point where people drop off. Their badge says Flow + sequence, but each install actually leaves three drafts in your account.
| Recipe | Starts on | Reminders | Needs |
|---|---|---|---|
| Abandoned cart recovery | Cart abandoned: products added to the cart, checkout never reached | Three on WhatsApp: 1 hour after enrolment, then 1 day later, then 3 days after that. The second and third end with a link that rebuilds the shopper's cart. | The Shopify connector and the browse pixel |
| Abandoned checkout recovery | Checkout abandoned: a checkout started that never became an order | Three on WhatsApp: 1 hour after enrolment, then 1 day later, then 3 days after that. The second and third end with the link to pick the checkout up again. | The Shopify connector (no pixel) |
| Browse abandonment nudge | Product browsed, not bought: a product page viewed with nothing added to the cart | Two on WhatsApp: 2 hours after enrolment, then 2 days later. The second names the product and links back to it. | The Shopify connector and the browse pixel |
- The sequence — the reminders above. Each step needs its sending WhatsApp account (Set platform on the step card): a subscriber who reaches a step without one leaves the sequence and nothing is sent. The first reminder must be an approved WhatsApp template you pick, because these shoppers have usually never written to you and a plain first message can't be delivered outside WhatsApp's 24-hour window. As installed it carries no link, so map one of the template's variables to the recipe's link — {{cf_cart_url}}, {{cf_checkout_url}}, or {{cf_product_url}} and {{cf_product_name}}. The drip pauses if the shopper replies. Nobody is enrolled again while still in it, paused included; after finishing, the same shopper gets in again only once a cooldown has passed: 7 days for cart, 3 for checkout, 14 for browse.
- The entry flow, named <your name> — entry flow — fires on the recipe's store event, removes a
purchasedtag left over from an earlier purchase, saves the link onto the contact (the cart link, the checkout link, or the product's link and name) so the reminders can use it, then enrols them. - Purchased tag (stops the drip) — a separate little flow, triggered by Order paid, whose only job is to put the
purchasedtag on the buyer. That tag is the sequence's goal, so applying it is what makes someone leave the drip the moment they buy.
The third flow keeps its own fixed name rather than yours, so it does not sit next to the other two in an alphabetical list and it is easy to mistake for something stray. Delete it, or leave it as a draft, and nothing ever applies the goal tag — which means a customer who buys after the first reminder still receives the rest. All three pieces have to be Live, both flows need their account picked, and every step of the sequence needs its sending account. Install two or three of these recipes and you get two or three identical copies of the tag flow: keep one Live and delete the other drafts. And if you installed Abandoned cart recovery before the September 2026 update, that copy still starts on Checkout abandoned: installing Abandoned checkout recovery as well would put the same shoppers into two drips, so delete the old copy first.
Before you set any of it live
The same four checks apply to every recipe, and the first one is the one that quietly costs people weeks.
Pick the account it runs on
A recipe installs with no connected account attached, because it cannot know which of yours to use. Choose one from Account on the automation bar — on a store-recovery recipe, in both of the flows it installs; its sequence steps each need a sending account too (Set platform on each step card). Until you do, the flow is invisible to the parts of IcloneU that would run it.
Connect whatever the trigger needs
The COD recipe and the three store-recovery recipes listen to Shopify events, so they need the Shopify connector under Automations → Connectors; the cart and browse recipes also need the browse pixel on your store (Adding the browse pixel to your Shopify store). The gallery does not check: a recipe installs happily whether or not the connector exists, and then waits for an event that never arrives.
Read the messages out loud
Every message in a recipe is a placeholder written by us in your language. It mentions no brand and makes no promise, but it is not your voice yet. This is also where you finish anything the card told you to — the survey tag on the NPS recipe, for one.
Test it, then Set Live
Run the flow against a sample the way the Building your first workflow guide describes, then switch it on. Setting a flow live warns about unconfigured nodes but does not stop you, so the test is the real check.
This is worth repeating on its own, because there is no error and no badge for it. A Live automation with no connected account is skipped outright: the message-driven side never loads it, and the connector-event side logs that it matched and then passed it over. From the outside the flow looks finished and switched on. If a recipe you published has never run once, check the account picker before you check anything else.
Frequently asked
Completely. What lands in your account is an ordinary workflow or sequence with nothing locked and no link back to the gallery — rename it, rewire it, delete nodes, add your own. Most recipes are worth treating as a first draft of the flow you actually want.
A recipe badged Drip sequence installs a sequence and no workflow, so it lives on the Sequences tab and will never appear in the Workflows list. The install takes you there automatically; if you navigated away, go back through the tab.
You now have two independent copies with the same name, and nothing links them. Neither does anything while it is a draft, so delete the one you do not want from the Workflows list before you set anything live.
For Lead magnet delivery (a message-keyword recipe) the trigger rule isn't the cause: its flow sends the message and tags the contact without pausing, and a flow that never pauses starts again on every match. Check that the second message contained the keyword, and whether the person was in the middle of another flow waiting for their reply — a waiting flow takes the message first. The once-per-contact rule only holds back message and referral flows that paused (on a message whose Continue in workflow buttons lead to a next step, a delay longer than 30 seconds, or an AI Agent conversation) and then resumed; turn on Fire every time on those if they should repeat. Tag and store-event triggers start their flows every time instead, and comment triggers are not limited to once per person — so re-applying the NPS survey tag surveys the contact again. On the three recovery recipes, what holds a returning shopper back is the sequence: nobody is enrolled again while still in it, paused included, and a shopper who finished re-enters only once its cooldown has passed — 7 days for cart, 3 for checkout, 14 for browse — which you change on the sequence.
Last updated September 21, 2026 · Automations
