Did you know that you can use Zapier’s built-in features to create advanced zaps between your apps and Flodesk?
In this article, we’re going to explain four popular Zapier features with examples of how you can use them with Flodesk. ⚡️
Note: Using some of these features may require a paid subscription with Zapier. Refer to Zapier’s pricing guide for more information.
A single-step zap only includes one Trigger step and one Action step. In a multi-step zap, you can have more than one action or use a Zapier feature like Filters, Paths, or Searches for example.
Use single-step zaps when you want all your subscribers from one app to be added to one segment in Flodesk.
For example, students who opt-in on an online course landing page can be added to one Flodesk segment using a single-step zap.
Use a multi-step zap when you need subscribers from one app to go to specific segments based on their behavior in the Trigger app.
If you have an online quiz, for example, you can filter subscribers into specific segments based on their quiz results.
Filters by Zapier
Filters allow zaps to only perform actions on the items you want. Think of Filters as a set of rules within your zap that must be met in order for the zap to continue. In order for Filters to work, you must have a Trigger created first.
For example, you can use a filter when you connect a quiz builder like Interact or Typeform to Flodesk. Without a filter, all the subscribers who complete the quiz will be added to one segment in your Flodesk audience.
Using a filter can separate each quiz result into a different Flodesk segment.
The filter might be case-sensitive, depending on the filtering rule that you’re using.
Not case-sensitive rules:
Does not contain
Is in list
Is not in list
Setting up the zap with a filter would look like this:
Paths by Zapier
Path rules function just like Filters do. The biggest difference between Zapier’s Paths and Filters is that you’ll need to create separate filters for each condition. With Paths, you can create one Path with multiple condition steps.
Paths are great because you can use fewer tasks in Zapier to achieve your automation.
The other difference is that you can set a condition for one path while other parts of your Path get their own conditions that determine when they run.
Here’s an example when connecting a Typeform Quiz to Flodesk using Paths by Zapier. In the example below, each of the four quiz results has its own condition.
This means that you can set up the zap to separate quiz results into their own segments in Flodesk, right from the paths you build. The screenshot below shows you that.
Here are a few things you want to keep in mind about Paths by Zapier:
You need at least two paths in order for the zap to work. If you only have one path, use Filters by Zapier instead.
Since each Path will have its own action, you can only add a Paths by Zapier step at the end of your zap.
You need a Professional plan or higher in Zapier to access Paths. You can read more about this on Zapier’s pricing page.
Delay by Zapier
Delay by Zapier is a feature that lets you set a specific amount of time before the next action happens in that zap. Your zap will still trigger each time an event happens, but the action will not happen until the delay is complete.
This feature can be very useful when you’re setting up a daily summary of new subscribers. By default, Zapier will send you a digest of new subscribers at midnight. You can use Delay by Zapier to delay the notification until 9:00 am (or another time of your choosing).
Note: If you change any part of your Zap during a delay, your Zap will not continue once the Zap resumes. This includes adding, changing, or removing actions. You can read more about troubleshooting Delay by Zapier in this article.
Let’s sum it up
Zapier has several built-in features that allow you to create advanced zaps. Some of these features require a paid Zapier plan and you can read more about their pricing here.
For instance, you can separate a subscriber’s quiz results into separate Flodesk segments. You can also send yourself a daily summary of how many subscribers you collected from the previous day.
More to learn:
We'd love to hear about your recent experience when searching for solutions to issues in the Flodesk Help Center. With your feedback, we can improve our knowledge base with new and better ways to help you succeed!
Please do not submit support tickets and feature requests via this feedback form.
If you couldn't find a solution for your issue in the Help center, please send us a note to firstname.lastname@example.org mentioning your Flodesk account login email with a detailed description of your problem.
Do you have an idea for a feature that will help improve Flodesk for you and other members? Our Product team would love to hear from you.