Skip to content
FlowWP logo
Menu

Automation for Online Stores

Thank customers when they pay, rescue failed payments, turn first orders into repeat ones and keep the team and your stock in view — for WooCommerce and Easy Digital Downloads stores.

Get FlowWPSee example workflows

Works with

Example workflow

Stay on top of stock changes

  1. WooCommerce logoTrigger · WooCommerceA product’s stock status changes
  2. Condition · LogicSwitch
    1. Branch: Sold out
      1. Action · EmailSend Email
    2. Branch: Back in stock
      1. WordPress logoAction · WordPressCreate a post
      2. Action · EmailSend Email
    3. Branch: On backorder
      1. Action · EmailSend Email
Open this template

The problem

What makes this slow by hand

  • Every order checked by hand

    Someone opens each order to thank the customer, tell the team or spot the one that looks wrong.

  • Failed payments are lost sales

    A declined card leaves an unpaid order nobody follows up on.

  • One order, then silence

    First-time buyers hear nothing after the receipt, so few of them come back.

  • Stock surprises

    You find out a product ran out when a customer complains.

How FlowWP handles it

The same work, as workflows on your own site

  • Every order, handled as it happensAn order being placed or paid starts a workflow on every plan, so thanking, routing and noting it no longer waits for someone to look.
  • Recover failed paymentsWhen a payment fails, wait, check the order again and only email the customer if it is still unpaid.
  • Turn first orders into repeat onesFollow up after a first purchase with a series of emails and a coupon code generated for that customer.
  • Hold the risky onesCheck an order’s total, payment method or coupon and put it on hold for a quick look before it ships.
  • Customers in your CRMAdd buyers to FluentCRM or Mailchimp as they pay, and reward the ones whose lifetime spend passes an amount.
  • Digital products tooEasy Digital Downloads purchases, refunds and new customers are triggers, with the same builder and run history.

Built on

Example workflows

Ready-made workflows to start from

Browse all templates
    1. WooCommerce logoTrigger: An order is paid (WooCommerce)
    2. Action: Send Email (Email)
    WooCommercePersonal plan

    Thank customers after they pay

    A personal thank-you email as soon as an order is paid.

    2 stepsBeginner
    1. WooCommerce logoTrigger: A payment fails on an order (WooCommerce)
    2. Action: Delay (Delay)
    3. WooCommerce logoAction: Get an order’s details (WooCommerce)
    4. Condition: If / Else (Logic)
    5. Action: Send Email (Email)
    6. +5 more steps
    WooCommercePersonal plan

    Recover orders whose payment failed

    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.

    10 stepsAdvanced
    1. WooCommerce logoTrigger: An order is paid (WooCommerce)
    2. FluentCRM logoCondition: A FluentCRM contact has a tag (FluentCRM)
    3. FluentCRM logoAction: Add tags to a FluentCRM contact (FluentCRM)
    4. +7 more steps
    WooCommercePersonal plan

    Turn first-time buyers into repeat customers

    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.

    10 stepsAdvanced
    1. WooCommerce logoTrigger: An order is paid (WooCommerce)
    2. Condition: Switch (Logic)
    3. WooCommerce logoAction: Set an order’s status (WooCommerce)
    4. Action: Send Email (Email)
    5. +3 more steps
    WooCommercePersonal plan

    Hold risky orders for a quick check

    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.

    7 stepsAdvanced
    1. WooCommerce logoTrigger: A product’s stock status changes (WooCommerce)
    2. Condition: Switch (Logic)
    3. Action: Send Email (Email)
    4. +3 more steps
    WooCommercePersonal plan

    Stay on top of stock changes

    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.

    6 stepsIntermediate
    1. Easy Digital Downloads logoTrigger: An order is refunded (Easy Digital Downloads)
    2. Easy Digital Downloads logoAction: Add a note to an order or customer (Easy Digital Downloads)
    3. Action: Delay (Delay)
    4. Action: Send Email (Email)
    DownloadsPersonal plan

    Ask what went wrong after a refund

    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.

    4 stepsIntermediate

Use cases

Worked through, step by step

All use cases

Integrations

The plugins and apps involved

Before you start

  • Which plan you need. An order being placed or paid, an order reaching a status and adding a note to an order are on every plan, including Free. Payment failures, refunds, stock, coupons, lifetime spend and the order actions, such as setting a status or generating a coupon, start on Personal. Each integration page lists the plan for every step.
  • Test without touching real orders. A test run uses sample data and rehearses steps that would change something, so you can check a workflow before a real customer meets it.
  • Messages to customers. Emails go through your site’s own mailer. WhatsApp messages need a WhatsApp Business connection and an approved template for the first message to a customer.
  • Your CRM and newsletter tool keep their own lists. FlowWP adds and tags customers at the right moment; campaigns are still sent from FluentCRM, Mailchimp or MailPoet.

Other solutions

Build your WordPress workflow visually.

Start with a template or a blank canvas. Nothing runs until you activate it.

Get FlowWPExplore Workflows