How to Let Subscribers Repeat a Workflow in Flodesk
Want to allow subscribers to go through the same workflow more than once—like redownloading a freebie or retaking a mini-course? With Flodesk’s “Allow repeat subscribers” feature, you can make it happen.
What This Feature Does
By default, subscribers can only go through a workflow once. But when you enable Allow repeat subscribers, they can re-enter the same workflow again and again, giving you more flexibility to:
Deliver freebies on demand
Re-send onboarding or sales sequences
How to Turn On “Allow Repeat Subscribers”
Open or create a workflow
Click Settings in the top right corner
Toggle “Allow repeat subscribers” ON
Set a "Wait time before repeating"
Click the X to close the modal
Finish editing your workflow and click Publish
Once enabled, subscribers can re-enter the workflow if they meet the trigger criteria again—as long as they’re no longer active in the workflow.
Important Notes
1. Allowing Subscribers to Repeat a Workflow
Subscribers who have already completed a workflow can go through it again if the "Allow repeat subscribers" setting is turned on.
A subscriber is marked as
completed
when they reach the Exit step at the end of the workflow.If the workflow doesn't have an Exit step and the subscriber reaches the “evergreen” state (held at the end of the workflow), they are still considered
active
and cannot be added again via the "Allow repeat subscribers" setting.
2. Re-adding Active or Completed Subscribers
Subscribers who are currently active
in a workflow will not trigger it again. They must either:
Complete the workflow by reaching the Exit step, or
Once removed or completed, they can be re-added through:
Link Actions → Add to workflow
Zapier → Add to workflow
Form submission (if the form is the workflow trigger)
Manual action → “Add subscribers” menu
3. Trigger Segments and Repeat Workflows
If a subscriber is already in the trigger segment, adding them to that same segment again will not trigger the workflow again—regardless of whether "Allow repeat subscribers" is on or off.
Examples that will not trigger a repeat workflow:
Re-adding to a segment they are currently in via CSV import
Re-adding to a segment they are currently in via form completion
Re-adding to a segment they are currently in via Zapier “Add to segment” action
These won’t restart the workflow if the subscriber is already part of the segment.
4. Making Repeat Workflows Possible with Trigger Segment Management
If you want subscribers to re-enter a workflow via a trigger segment, you need to remove them from the segment after their first run.
You can do this by:
Using an Action step in the workflow to remove them from the segment
Setting up a Zapier automation to remove them from the segment
Once they’ve been removed from the segment and have completed the workflow (via Exit step), you can re-add them using:
Form submission (when trigger is segment)
CSV import
Zapier “Add to segment” action
Poll blocks
Link actions, etc.
Let’s look at an example.
Segment 1 is the trigger step of Workflow 1. When a subscriber is added to Segment 1, they will start the workflow and complete it.
Now, if the same subscriber submits Form 1 sometime later, which adds them to Segment 1, they will not trigger the workflow again, because the subscriber is already in Segment 1.
If you want to allow the subscriber to go through this workflow again, you need to
Turn on “Allow repeat subscribers” AND
Add the Form as an additional trigger for the workflow.
Best Use Cases for Repeat Workflows
Let subscribers redownload a freebie they lost
Re-engage subscribers with a refresher series
Trigger a replay of webinar reminders
Let customers retake a challenge or campaign
Summary
To allow subscribers to repeat a workflow:
Enable “Allow repeat subscribers” in workflow settings
Make sure they’ve either:
Reached the Exit step, or
Been removed manually from the workflow
Re-trigger them through:
Form submissions
Link actions
Zapier/Pabbly
Manual actions
If using a segment-based trigger, remove and re-add them to the segment
Or better yet, use a form as a trigger instead