Automation recipes worth setting up

Concrete flows, written the way you’d build them.

Catch a bad review immediately

Trigger:  Review · created
Condition: rating ≤ 3            → true
  ↓  Notify Team
  ↓  Draft Review Reply
  ↓  Escalate to Team Inbox

The highest-value workflow in the product. Responding in twenty minutes rather than three days changes the outcome for the customer and for everyone who reads the review later.

Draft rather than send, so a person approves the wording.

Thank a happy reviewer

Trigger:  Review · created
Condition: rating ≥ 4            → true
  ↓  Draft Review Reply

Cheap, and it visibly changes how your review profile reads — a page where every review has a reply signals a business that’s present.

Note the automation drafts; it doesn’t post. You still publish each reply on the platform, so budget a few minutes a week for that rather than expecting the profile to fill itself. → Responding to reviews

Post-purchase feedback, timed properly

Trigger:  Shopify · customers create   (or Stripe · charge.succeeded)
  ↓  Wait 5 days
  ↓  Send Survey
  ↓  Survey Response Condition
     ├─ positive  →  Send Email (ask for a public review)
     ├─ negative  →  Notify Team → Escalate to Team Inbox
     ├─ neutral   →  (end)
     └─ default   →  Wait 3 days → Send Email (one reminder)

The Wait is the whole recipe. Survey after delivery, not after checkout.

Churn insight

Trigger:  Stripe · customer.subscription.deleted
  ↓  Wait 1 hour
  ↓  Send Survey  (one question: why did you cancel?)
  ↓  Survey Response Condition
     ├─ negative  →  Escalate to Team Inbox
     └─ default   →  (end)

The best churn data most businesses never collect. Ask at cancellation while the reason is fresh — and keep it to one question.

The short wait avoids the survey landing in the same second as the cancellation email.

Close the loop after a fix

Trigger:  Response · received
Condition: sentiment is negative  → true
  ↓  Escalate to Team Inbox
  ↓  Wait 14 days
  ↓  Send Survey  (did we sort it out?)

The step almost everyone skips. It’s what tells you whether your recovery process is real or theatrical.

Route by location

Trigger:  Review · created
Condition: location = Branch A    → true
  ↓  Notify Team  (Branch A manager)
                                  → false
  ↓  Notify Team  (default recipient)

For multi-site businesses. An alert everyone receives is an alert nobody acts on.

Before enabling any of these

Run a test against yourself first. Every workflow looks right in the builder and reveals its real behaviour the moment live data hits it.

→ Testing and activating