Skip to main content

Integrating EasyWebinar with Flodesk using Zapier

Updated over 2 weeks ago

Step 1: Set Up the Zap Trigger in Zapier

  1. Log into your Zapier account.

  2. Create a new Zap and set the trigger app to EasyWebinar.

  3. Select the event “New Webinar Registration”.

  4. Choose the specific webinar you want to track.

  5. Run a test to make sure Zapier can pull registration data from EasyWebinar.

Step 2: Configure the Action as Flodesk

  1. For the action app, select Flodesk.

  2. Choose the event “Create or Update Subscriber”.

  3. Connect your Flodesk account to Zapier.

  4. Once connected, configure the fields you want to send (e.g., name, email).

  5. Select the appropriate segment in Flodesk—such as “Webinar Registered”.

Note: Flodesk does not support traditional tags like many other CRMs. Instead, segmentation is handled through segments.

Step 3: Create Custom Segments in Flodesk

Before proceeding, make sure to create separate segments in Flodesk for different webinar actions, such as:

  • Webinar Registered

  • Webinar Attended

  • Webinar Missed

Each segment will serve as a container for users based on their interaction with your webinar.

Step 4: Push Custom Fields (Optional)

If you want to send additional information such as the webinar join link or replay link, you’ll need to:

  1. Create custom fields inside Flodesk under a subscriber profile.

  2. Once custom fields are created, they will appear in Zapier when mapping fields in the action step.

  3. Map these fields from EasyWebinar accordingly.

Step 5: Create a Zap for Webinar Attendance

To track who attended the webinar:

  1. Set the trigger app to EasyWebinar again.

  2. Choose the appropriate tag for attendees.

  3. In the action step, select Flodesk and Create or Update Subscriber.

  4. Assign this data to the Webinar Attended segment in Flodesk.

Repeat the same process to create zaps for other interactions, such as:

  • Webinar Missed

  • Replay Watched

  • Left Early

Each interaction should be pushed to its respective segment within Flodesk.

Did this answer your question?