Skip to content
FlowWP logo
Menu

WordPress Email Automation

Send the right email when something happens on your site: a purchase, a sign-up, a form, a finished course. Built visually, sent through your site’s own mailer, and recorded step by step.

Get FlowWPSee example workflows

Works with

Example workflow

Follow up on Contact Form 7 enquiries

  1. Contact Form 7 logoTrigger · Contact Form 7A Contact Form 7 form is submitted
  2. FluentCRM logoAction · FluentCRMAdd or update a FluentCRM contact
  3. Action · EmailSend Email
  4. Action · DelayDelay
  5. FluentCRM logoCondition · FluentCRMA FluentCRM contact has a tag
  6. Branch: False
    Action · EmailSend Email
Open this template

The problem

What makes this slow by hand

  • Emails that depend on someone remembering

    A welcome, a thank-you or a follow-up only goes out if a person notices the order or the form and writes it.

  • Every plugin has its own email settings

    WooCommerce, your form plugin and your LMS each send their own messages, configured in different places.

  • Follow-ups need timing

    “Two days later, if they have not bought” is hard to do by hand and easy to forget.

  • No record of what went out

    When a customer says they never got it, there is nothing to check.

How FlowWP handles it

The same work, as workflows on your own site

  • Triggered by real eventsStart from an order being paid, a user signing up, a form submission, a finished course, a donation or an RSVP.
  • Personal, not genericTokens put the customer’s name, order number or course into the subject and body, and If and Switch send different emails to different people.
  • Sequences with delaysWait hours or days between messages, and check again before the next one goes out. Delays run in the background, so nobody waits on them.
  • Sent through your siteThe Send Email step uses the site’s configured mailer, as plain text or HTML. Nothing passes through a FlowWP server.
  • Tested without sendingA test run shows the email a step would send instead of sending it.
  • Every send on recordRun history shows who each email went to and what the step was given, and a sent message is never retried for you.

Built on

Example workflows

Ready-made workflows to start from

Browse all templates
    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. WordPress logoTrigger: A user is created (WordPress)
    2. Action: Send Email (Email)
    WordPressFree

    Welcome new users by email

    Send every new account a friendly welcome, addressed by name.

    2 stepsBeginner
    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. Contact Form 7 logoTrigger: A Contact Form 7 form is submitted (Contact Form 7)
    2. FluentCRM logoAction: Add or update a FluentCRM contact (FluentCRM)
    3. Action: Send Email (Email)
    4. Action: Delay (Delay)
    5. FluentCRM logoCondition: A FluentCRM contact has a tag (FluentCRM)
    6. +1 more steps
    CRMPersonal plan

    Follow up on Contact Form 7 enquiries

    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.

    6 stepsIntermediate
    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. GiveWP logoTrigger: A donation is completed (GiveWP)
    2. GiveWP logoCondition: The donor has given before (GiveWP)
    3. Action: Send Email (Email)
    4. GiveWP logoAction: Add a note to a donor (GiveWP)
    5. +1 more steps
    DonationsBusiness plan

    Thank donors, and thank regulars differently

    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.

    5 stepsIntermediate

Use cases

Worked through, step by step

All use cases

Integrations

The plugins and apps involved

Before you start

  • Deliverability is your site’s mail setup. FlowWP sends through WordPress’ own mailer. If your site’s emails land in spam today, set up an SMTP or transactional email plugin first; FlowWP’s emails go through it like every other email the site sends.
  • A failed send is recorded, not lost. When WordPress cannot send, the step fails with “WordPress could not send the email. Check the site’s mail configuration.” and the run history shows exactly where.
  • Which plan you need. The Send Email step and WordPress’ own triggers, such as a new user, are on every plan including Free. Delays, which follow-up sequences need, start on Personal. Each integration page lists which plan includes each of its steps.
  • Newsletters belong in your email tool. For campaigns, use FlowWP to put people on the right MailPoet, Mailchimp or FluentCRM list or tag at the right moment, and let that tool send.

Other solutions

Build your WordPress workflow visually.

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

Get FlowWPExplore Workflows