Question on best setup for trigger on MailerLite

[dilbert16588]

Your Workflow URL

https://connect.pabbly.com/workflow/mapping/IjU3NjYwNTY1MDYzZTA0MzY1MjZiNTUzMDUxMzMi_pc

Your Task History ID

https://connect.pabbly.com/task/history?filter_status=applied&filter_by_workflow_id=IjU3NjYwNTY1MDYzZTA0MzY1MjZiNTUzMDUxMzMi_pc

Consent to Access & Modify

I authorize Pabbly Support to log in to my account and make changes to the specified workflow for troubleshooting.

Hi,

I've set up a workflow between MailerLite and MemberVault. The goal is so that whenever a subscriber is added to a specific group on MailerLite, they will be added to my course on MemberVault.

When I first set this up, my MailerLite trigger was "Subscriber Added to Group". After connecting and triggering the specific group I want to get the response, the next step was simply connect it with MemberVault. And after a quick test, it appeared to work fine.

Until someone was added to my course in MemberVault from a DIFFERENT group than the one that I selected - and one who didn't purchase the course. It seemed to be adding any subscriber, if there were added to ANY group in MailerLite!

Thankfully I caught it quickly and tweaked the workflow to add a Pabbly router to avoid this. The first Route uses a Pabbly filter to select only the product's group, then a second step is to simple add them to MemberVault with access to the course. The second route simple uses a Pabbly filter to check if it's any other group, and there is no second step. Effectively the Router only adds subscribers to my MemberVault course ONLY if they are added to the specific group.

It works - but still continues to trigger EVERY TIME someone is added to a MailerLite group. Since Pabbly only counts tasks for connections between platforms, I'm not losing tasks. But since I set up the workflow, I've had one subscriber correctly added to MemberVault with one more task consumed - but 696 workflow executions and over 2000 Pabbly free tasks consumed!


It seems quite excessive! Is there a better way to connect my MailerLite subscriber to MemberVault?


Perhaps it's a change to the MailerLite trigger? I could easily use "Subscriber Triggered Automation" which notes it's should only trigger for specific automations. But couldn't figure out how to actually trigger the correct automation in MailerLite as the MailerLite automation trigger itself is a WooCommerce purchase.

Any help would greatly be appreciated!

 

[Preeti Paryani]

Hello @dilbert16588,

Thanks for sharing the details. Currently, the workflow will trigger for every subscriber added to MailerLite. However, you can control which subscribers are added to MemberVault by structuring your workflow like this:

1. Use the “Subscriber Added to Group” trigger.
2. Immediately add a Filter to check if the subscriber belongs to the specific group you want.
3. Only if the filter passes, execute the MemberVault: Create Subscriber action.

With this setup, the workflow runs for all subscribers, but only those added to the required group will be created in MemberVault, minimizing unnecessary task usage.

 

[dilbert16588]

Hello @dilbert16588,

Thanks for sharing the details. Currently, the workflow will trigger for every subscriber added to MailerLite. However, you can control which subscribers are added to MemberVault by structuring your workflow like this:

1. Use the “Subscriber Added to Group” trigger.
2. Immediately add a Filter to check if the subscriber belongs to the specific group you want.
3. Only if the filter passes, execute the MemberVault: Create Subscriber action.

With this setup, the workflow runs for all subscribers, but only those added to the required group will be created in MemberVault, minimizing unnecessary task usage.

Except adding a filter step instead of a router step (with the filter added into the first route) only reduces the current 3 free tasks per run down to two. It still runs EVERY time a MailerLite subscriber is added to ANY group.

I've got many groups, that trigger multiple automations - including groups that indicate sequences "In Progress" and "Completed". A new subscriber would be added to a minimum of 5 groups within 2-3 weeks after signing up.

I'm looking at how to stop Pabbly from triggering every time that a subscriber is added to a group. As I noted in my initial question, the MailerLite trigger "Subscriber Triggered Automation" might be a possible option - but without trialling it and messing up an otherwise working workflow (or risk duplicating it for those already in the sequence!), I cannot be sure that this different trigger wouldn't result in the same excessive triggers - even if they're free tasks.