# Ready-Made Workflow Templates

> Source: https://primemoq.app/help/automations/workflow-templates
> Collection: Automations
> Updated: 2026-08-26

Four pre-built Shopify Flow chains for the most common reactions to a blocked order, ready to install, adapt, or use as a starting point.

**Short answer.** The Automations page lists four ready-made workflow templates, each drawn as a trigger, condition and action chain. Two ship with a workflow file you import into Flow in about a minute, and two link straight into Flow so you can build the chain yourself. After importing, you must set the action's Rule ID by hand, because the field takes an ID and not a rule name.

## Key takeaways

- Every template's chain is visible on all plans. Only clicking Install needs Pro.
- Installing is a download and an import, because Shopify has no API for an app to add a workflow directly.
- The action step targets a rule by ID, never by name. Set it after importing.
- An imported Flow workflow is off until you turn it on, and the send toggle is separate again.

## Before you start

- Shopify Flow installed on your store.
- Event sending turned on from the Automations page, or nothing reaches the workflow.

## The four templates

| Template | Chain | Best for |
| --- | --- | --- |
| Low stock tightens the maximum | Inventory changed, below 10, set rule maximum to 2 | Protecting thin stock without watching it by hand |
| Oversized cart becomes a freight quote | Order limit blocked, weight limit, email the freight team | Turning a freight-blocked cart into a conversation rather than a lost order |
| Near-miss carts become leads | Order limit blocked, over 60 percent of the minimum, tag the customer and notify a rep | Catching wholesale-curious shoppers who fall just short |
| Repeat buyer worth a look | Repurchase limit reached, tag the customer, message Slack | Flagging accounts that keep hitting an anti-hoarding limit |

Every template is a starting point. Once imported it is an ordinary Flow
workflow, and you can add, remove and reorder steps like any other.

## Set the rule by ID, not by name

This is the single most common reason an imported template does nothing.

The action step has a **Rule ID** field. It is not a rule name field, because two
rules are allowed to share a name and an action that guessed between them would
be worse than one that refused. After importing, open the action step and paste
the exact ID copied from that rule's edit page. See
[Finding a rule's ID for Shopify Flow](https://primemoq.app/help/automations/rule-id-for-flow).

If the imported file arrives with a placeholder or a rule name already sitting in
that field, replace it with the real ID before turning the workflow on.

## Install a template that ships with a file

Both "Low stock tightens the maximum" and "Oversized cart becomes a freight
quote" work this way.

**Click Install on the template.** A walkthrough opens.

**Click Download workflow file.**

**Open Shopify Flow,** from the button or from your Shopify admin.

**Import the file.** In Flow's editor, open the overflow menu and choose Import,
then pick the file you downloaded.

**Set the Rule ID** on the action step, as above.

**Turn the workflow on.** Flow workflows are off after import, and this step is
easy to miss.

## Build a template that links into Flow

"Near-miss carts become leads" and "Repeat buyer worth a look" have no bundled
file yet.

**Click Install,** or the direct Flow link on the template card.

**Build the chain shown on the card** in Flow's own editor, using its trigger,
condition and action pickers.

**Save and turn the workflow on.**

## Adapting each template

**Low stock tightens the maximum.** Change the inventory threshold and the
tightened maximum to match your own stock levels. The template only ships the
tightening direction, so if you want the cap to loosen again after a restock,
build a second workflow with the condition flipped and the action setting your
normal maximum back. You can also point it at a different bound entirely, such as
tightening a case-pack multiple instead of a maximum.

**Oversized cart becomes a freight quote.** Change the recipient, subject and
body to match how your freight team actually works, or swap the email for a Slack
message or a helpdesk task. Two limits are worth knowing: the message body
references a cart total field that Prime MOQ does not populate yet, so that line
arrives empty, and despite what the chain badge says the shipped file does not
create a draft order. Add that step yourself in Flow if you want one.

**Near-miss carts become leads.** Adjust the 60 percent threshold to match how
you define a near miss. Guests have no customer record, so add a condition
filtering them out before the tag step, described in
[the Order limit blocked trigger](https://primemoq.app/help/automations/trigger-order-limit-blocked).

**Repeat buyer worth a look.** Swap the Slack message for an email or a CRM task,
and pair it with a second workflow using
[Reset repurchase counter](https://primemoq.app/help/automations/action-reset-repurchase-counter) so
your team can clear a flagged customer once they have reviewed the account.

## Common mistakes

- Expecting a one-click install. Shopify has no API letting an app add a
workflow to your Flow directly. Download and import is the shortest path that
exists.

- Setting the rule by name. The field takes an ID.

- Importing and never turning the workflow on. It is off by default.

- Expecting the freight template to create a draft order. The chain badge
says so, the shipped file does not. Treat the email as your cue.

- Expecting the cart total line in the freight email to be filled in. That
field is not populated yet. Everything else in the message works.

## FAQ

### Can I customise a template after installing it?

Yes. Once imported it is a normal Flow workflow, so you can add, remove and reorder steps exactly as you would on one you built yourself.

### Do I need a template to use Automations at all?

No. Templates are a shortcut. You can build any workflow in Flow from Prime MOQ's triggers and actions without touching one, and the companion articles on each trigger and action carry more scenarios.

### Why do only two templates ship with a downloadable file?

The other two are newer and have no bundled file yet. Install takes you straight into Flow to build the chain shown on the card instead.

### Does installing a template turn on event sending for me?

No. Those are separate steps. Turn on the send toggle from the Automations page as well, or the imported workflow sits there with nothing arriving.

### Can I install the same template twice?

Yes, and it is a reasonable thing to do when two rules need the same reaction. Each import is an independent workflow, so give each one its own Rule ID.

**Best for:** Getting a working automation live in minutes rather than building a Flow chain from an empty canvas.

**Applies to:** Pro plan for installing, All plans to view the templates