Trigger: An order is paid (WooCommerce)
- Condition: Switch (Logic)
- Action: Send Email (Email)
Flag large orders to your team
Orders over 500 go to someone who can give them extra care. Change the amount to suit your store.
Workflow templates
Every template here ships inside FlowWP. Pick one, fill in the few details only you know, and activate it. Each one is an ordinary workflow you can change.
72 templates
Orders over 500 go to someone who can give them extra care. Change the amount to suit your store.
A paid order posts to your channel with what was bought, what it came to, and a link straight to the order. The one automation nearly every shop wants first.
Every message is read by AI and filed as a question, a complaint or a sales lead, then passed to whoever handles that. Spam is recognised and dropped quietly.
Each submission becomes a contact tagged Enquiry. Uses the your-name and your-email fields of Contact Form 7’s default form.
Three days after a membership expires — not when it is cancelled — invite the member back.
A completed order sends an approved template to the phone number on the order. WhatsApp only allows a template for a message a business starts, so write and submit one in the WhatsApp Manager first — its placeholders are filled in here with their name and the order number.
Send every new account a friendly welcome, addressed by name.
Email someone each time a post is published, with a link to read it.
Email a post’s author whenever someone comments on it.
A personal thank-you email as soon as an order is paid.
Every paid order saves the customer as a contact tagged Customer.
Orders over 200 tag the customer VIP, ready for your VIP emails. Change the amount to suit your store.
Every Elementor Pro form submission goes to someone who can follow it up, with the page it came from.
Each submission becomes a user account, or uses the one that email already has.
A friendly confirmation to the address they gave, so they know it arrived.
Email someone whenever a stored entry changes, so edits do not go unnoticed.
An email the moment a student finishes, with their result.
A friendly email with a link to the course as soon as someone enrolls.
Email each new member of a group, with a link back to it.
A congratulations email whenever someone earns an achievement.
Email members the moment they get a Paid Memberships Pro level.
An email the moment a student completes a Tutor LMS course.
Buying a WooCommerce product enrolls the customer in a Tutor LMS course. The customer needs an account on the site.
When a Tutor LMS quiz is failed, send the student a kind note with their score and a nudge to try again.
A refunded Paid Memberships Pro order takes away the level it paid for, so refunds and access stay in step.
When a Paid Memberships Pro renewal is declined, ask the member to update their card before their access lapses.
When a FluentCRM contact unsubscribes, take them out of your newsletter segment so nothing is sent to them by mistake.
A first order starts a short series: a welcome, a check-in three days later, and a one-time 10% coupon a week after that. Returning customers are just tagged.
An hour after a failed payment, check the order is still unpaid and send the customer a link to pay. If it is still unpaid a day later, tell your team.
Four- and five-star reviewers get a thank-you coupon. Lower ratings go straight to your team, so an unhappy customer hears from a person fast.
Sold out? Your buyer hears at once. Back in stock? A draft “back in stock” post is written for you to publish. On backorder? The team is told.
When a customer’s total spend passes 1,000, tag them VIP, send a personal 15% code, and let your team know who they are. Change the amount to suit your store.
Paid orders over 1,000 go on hold for a person to check; guest orders using a coupon get a note and an alert. Everything else is marked as checked.
Every lead is saved in FluentCRM and gets an instant reply. Then pricing questions go to sales, problems go to support, and the rest to a general inbox. Uses the name and message fields of Elementor’s default form.
Save the enquiry in FluentCRM and confirm it straight away. Two days later, if they have not become a customer, send a friendly follow-up.
Point Zapier, Make, a landing page or any other tool at this workflow’s webhook. Leads with an email are saved in FluentCRM, welcomed, and passed to your team.
A pass earns GamiPress points and a well done. A near miss gets encouragement to retry. A low score alerts the instructor and sends the student back to the lessons.
Finishing a course earns GamiPress points, a shout-out on the BuddyPress activity stream and a congratulations email — then, three days later, a suggestion of what to learn next.
A week after enrolling, check each student’s progress: congratulate finishers, nudge those who have not started, and encourage everyone in between with their percentage.
A new Paid Memberships Pro member is welcomed, saved in FluentCRM, added to your members’ BuddyPress group, then sent tips on day two and a feedback request on day seven.
Ask the member to update their card at once. Three days later, remind anyone still active, or invite back anyone whose membership has lapsed and tag them in FluentCRM.
Reaching a new GamiPress rank earns a personal WooCommerce coupon, a congratulations email and a shout-out on the BuddyPress activity stream.
Each published post is sent to a chat channel through an incoming webhook. If the channel refuses it, you get an email instead of silence. Works with Slack, Discord, Teams and anything else that takes JSON.
Requests a page on a schedule and emails you the moment it answers with an error, including the status code.
When a post goes live, AI writes a two-sentence summary and emails it to whoever writes the newsletter, so they are not summarising it themselves.
An AI agent reads your published content and drafts an answer to the question, then emails the draft to your team. It never replies to the customer itself — a person sends it.
A thank-you email the moment a purchase completes, and a note on the order so your team can see it went out.
When someone buys the download you choose, they join a list and get a tag, so you can write to that group later without building it by hand.
A refunded order is written on the customer record, then a day later the customer is asked what happened — while it is recent but no longer raw.
Every completed donation is thanked — but someone giving for the second time or more gets a letter that says so, and a note goes on their donor record either way.
A gift over 500 — change that to whatever is large for you — reaches a person the same day, with the donor’s history beside it, so it can be acknowledged properly.
When an event is published, AI writes a short announcement from its own details — date, place and description — and it lands with whoever sends the newsletter.
Someone RSVPs, gets a confirmation with the date and the address, and joins a MailPoet list tagged as an attendee so you can write to them before the day.
A day after someone is checked in at the door, they are thanked — and a Groundhogg tag marks them as somebody who comes, not just somebody who registers.
Every RSVP checks what is left. When the event is down to its last few places, someone hears about it while there is still time to add capacity.
Anyone who writes to you becomes a tagged contact, and the message itself is kept as a note on their record — so the next person to speak to them can see it.
A click in one of your emails is the warmest signal you get. This tags the contact and tells your team while they are still reading.
A paid order opens a channel named after it, puts your team in, and posts the details as the first message — so everything about that job is in one place instead of scattered through email.
A failed payment posts to your channel with an @ mention of whoever handles them, so it is someone’s job rather than everyone’s.
Each published post arrives in your server as a card with its title, summary and a link — rather than a bare URL nobody clicks.
Every published post goes to your channel the moment it is live, quietly, so subscribers see it without being pinged.
Checks a page every fifteen minutes. The moment it answers with an error, Telegram reaches a phone and Slack tells the team — because email is the one place nobody looks at two in the morning.
Posts “running”, does the work, then edits that same message to say how it went — so the channel holds one line per night instead of two.
A form where someone hands over their Discord ID gets them the role that opens the members-only channels, a welcome message from the bot, and an invite link if they are not in the server yet.
WhatsApp reports a failure quietly, long after the step that sent it said yes. This catches every one and emails you the number and the code — 131047 is the 24-hour window having closed, 131049 and 131050 are them having opted out, 131026 is a number that cannot receive at all.
Nobody watches a business WhatsApp all day. Each message arrives as an email with the sender’s number and name, so it lands where the rest of your work already is — and replying still needs a person, inside the 24 hours WhatsApp allows.
An AI agent reads what you have published, writes an answer, and replies on WhatsApp inside the 24 hours a reply is allowed. It answers questions your site already covers — anything else it says it cannot help with, rather than inventing something.
A paid order adds the customer to an audience as Pending, so Mailchimp emails them to confirm before it counts them — the compliant way round. If your checkout already asks for consent, change the step to Subscribed.
Anyone who creates an account joins the audience as Pending and is tagged Member, so your list follows your membership without anybody exporting a CSV.
Orders over 200 tag the customer VIP on your audience, ready for a segment of your own. Change the amount to suit your shop.
Mailchimp keeps the new address and forgets the old one. This writes the old one onto their profile as a note, so the next person to open it can still match them to an order, an account or a conversation.
Somebody pressing unsubscribe is ordinary. Somebody marking your campaign as spam is not — enough of them and your sending reputation goes, and Mailchimp will not tell you unprompted. This watches only for those and emails you each one.
How templates work
Templates carry no hidden behaviour: each one is the same kind of workflow you would build yourself.
Start with a template or a blank canvas. Nothing runs until you activate it.