tr Skip to content
Black Friday FlowMattic for life, 12 payments of $33.25 Or $399 once. Nothing added for splitting Ends in --Days --Hrs --Min --Sec See the deal

When a campaign is sent, after a week, get all the contacts not opened the email and add them to a new list

A week after a FluentCRM campaign finishes sending, FlowMattic fetches the contacts who didn’t open it, creates a new FluentCRM list and adds each of those contacts to it for a follow-up send.

FluentCRM Delay Iterator

6 steps Setup ~12 min Used on 720 sites Free to import

The When a campaign is sent, after a week, get all the contacts not opened the email and add them to a new list workflow on the FlowMattic canvas, with 6 steps across FluentCRM, Delay, Iterator
The workflow as it appears in the builder after import. Each step opens for editing.

What this workflow does

Plenty of people miss a campaign the first time: it lands on a busy day or gets buried. Sending a second version only to those who didn't open the first means building a segment by hand after every send. This workflow builds it for you, one week after each campaign goes out.

The FluentCRM Campaign Sent trigger fires when a campaign has finished sending all its emails and is archived. A Delay then waits one week, giving recipients time to open it. Next, a FluentCRM step fetches the contacts who did not open an email from that campaign, using the campaign's ID from the trigger.

A Create List step then makes a new FluentCRM list. It ships unmapped, so after import you set how the list is named, for example by mapping in the campaign's title so each list is easy to recognise later. An Iterator loops through the non-openers one by one, and an Add Lists to Contact step adds each one, by email, to the list just created. These people are already FluentCRM contacts, so the step has someone to add.

Every campaign you send creates one new list, so expect the list count to grow. Opens in FluentCRM depend on tracking, and some email apps block it, so the list may include people who did read the email.

Resend with a new subject line

A newsletter writer sends the same issue a week later with a different subject, only to the contacts on that campaign's non-opener list.

Event invitation follow-up

An events team mails a second invitation to people who never opened the first, without having to build a segment after every campaign.

Cleaning out inactive contacts

A store reviews the non-opener lists from several campaigns to spot contacts who haven't opened anything in months.

How this workflow runs

What happens at each step once the workflow is on, and what you need before you import it.

  1. Step 1Trigger
    FluentCRM Campaign Sent

    Fires when a FluentCRM campaign has finished sending all its emails and is archived. The campaign's ID and details are passed to the later steps.

  2. Step 2Logic
    Delay Delay For

    Waits one week after the campaign finishes, so recipients have had time to open it before the check.

  3. Step 3Action
    FluentCRM Get Contacts Who Did Not Open Email

    Fetches the contacts who did not open an email from this campaign, using the campaign ID from the trigger.

  4. Step 4Action
    FluentCRM Create List

    Creates a new contact list in FluentCRM. The step ships unmapped: set the list's name, for example from the campaign title, so you can tell the lists apart.

  5. Step 5Logic
    Iterator Loop Through Array

    Goes through the non-openers one at a time and runs the next step for each contact.

  6. Step 6Action
    FluentCRM Add Lists to Contact

    Adds the current contact, matched by email, to the list created in the earlier step. It runs once per non-opener.

What you need

  • FlowMatticCore
  • FluentCRM PluginPlugin

After importing, map your own data. To keep the template universal, not every step is pre-filled. Open each step in the builder and connect your accounts and fields (channels, lists, sheets, recipients) before you switch the workflow on.

Make it yours

Changes worth making after you import it.

  • Map the campaign title and the send date into the Create List name, so each non-opener list says which campaign it belongs to.
  • Change the Delay to fit how fast your readers usually open. Shorten it to a few days if campaigns are time-sensitive.
  • Add FluentCRM's Add Tags to Contact action after Add Lists to Contact, inside the loop, if you also want to tag each non-opener for long-term tracking.
  • Delete old non-opener lists in FluentCRM once you've used them, since every campaign adds a new one.

Questions about this workflow

Does this workflow send the follow-up campaign too?

No. It builds the list of non-openers. You then create the follow-up campaign in FluentCRM and send it to that list.

Will every FluentCRM campaign get its own non-opener list?

Yes. Each finished campaign starts a run, and each run creates one new list. If you only want this for some campaigns, add a Filter on the campaign title between the trigger and the Delay.

Why might someone who read the email end up on the list?

FluentCRM counts an open when its tracking registers one. Email apps that block images or tracking can hide real opens, so treat the list as an approximation.

Can I change the one-week wait after a FluentCRM campaign?

Yes. Open the Delay step and set any number of days or weeks. The non-opener check runs as soon as the Delay ends.

Import this workflow into your WordPress site

Download the JSON, import it from the Workflows screen and connect your accounts. Every run stays on your server, with no per-task fees.

30-day money-back guarantee Unlimited workflows and runs Self-hosted

Customers who run it every day

Rated 4.8 out of 5 by customers
Read more reviews

An excellent replacement to Zapier with unlimited tasks and full control over data. Customer service is fantastic! Have had hands-on support from owner who is ultra helpful and they have even been integrating new SAAS options continuously.

Brad

It's an exceptional product. Works great and extremely valuable. I saved thousands of dollard on Zapier, as Flowmattic makes me able to host the automation myself. And very deeply integrates with the products I need.