Hello Lee Busch: thank you for the feedback! If adding tags to existing subscribers could trigger additional automations, could you share an example how you would use them in your operations?

Tautvidas In reply about use cases:

An existing customer buys a new course. They receive a Tag related to that course, and an Automation containing 12 weeks of course-related emails begins to run.

I do not use Woocommerce.

In my case, the payment is via StudioCart, the system control is via Wishlist Member, which has its own integrations/automations. WLM is able to assign clients to MP Lists.

But I can't see a way, currently, for an existing customer to be added to an Automation programmatically and have it trigger. Am I wrong?

I've had to use a totally different email system which DOES support correct triggering based on tags.

Lee Busch I have just added them to a new list that starts the automation when they are added to the wishlist level. However this launches the automation immediately and maybe they don't start the course directly.

Now I offer them to subscribe to the new list when they start the course instead.

This is a workaround, I would like it to be more smooth, like when they click a link they are added to the automation (if logged in).

Jonas Höglund Thank you Jonas. My solution was to use a different email platform completely. One that 1) doesn't rely on double-opt-in, so that the students are assured of getting what they paid for, and 2) one that actually triggers correctly, for a seamless user experience.

Perhaps one day MailPoet will be ready for professional use.

Lee Busch that's great. What platform if my ask? I tried some out but their ui for creating emails was horrible so Mailpoet won sofar, even if they lack some features and have really crappy helpdesk.

Jonas Höglund Certainly. I bought Acumbamail when they were having a launch deal. They are not perfect, but they do more of what I need. I've also done deep research into the major competitors, and would choose MailerLite for best price/quality, or ConvertKit if budget is no concern.

TBH I think I've got more than one foot out the door on MailPoet at this point. There are many better options, and although I have a large investment in this platform, it's taking years to progress inches.

David Rotter

This option is needed to make MailPoet more powerful in automations. Tautvidas do you guys plan to allow Bulk Added Tags to trigger automations?

Ján Mikláš: Hi Jan, great last update on Automations with the IF/Else option, the plugin did a huge step. I would like to know where to publish new requests for automations, should we use this thread? For example, would be great on the Abandon Cart triggers be able to filter and use the IF/Else conditions based on cart amount. Thanks keep pushing!

Ivan Martinez: we do plan to release a couple more improvement before we remove the "beta" badge, at which point I'll close this request so we can better track each individual automation-related request separately. Feel free to already create a new request for cart amount filter (I'll share, that this is on our roadmap, hopefully by the end of this year, but likely only after out-of-beta).

Ján Mikláš could you please also update the documentation as it's not always obvious how different triggers work

Hello Jonas Höglund: thank you for the feedback! Do you by any chance recall one or two example triggers that weren't clear?

It would help further inform our approach.

Tautvidas number of clicks could be "number of clicked links".

But I think the list is updated since my complaint so it's more obvious now

Anthony Boes exactly that

Anthony Boes yes. We need the ability to 1) clone an automation, including the emails within it. 2) open any email in an automation and make it a template for re-use. 3) save out and import automations and templates within the Automations edit experience, just as we can save and import emails in other areas of the app. This is functionality that should be carried over from the core features.

Hi Carlos Divas, thanks for the feedback, we really appreciate it!

Yes, this is planned! As a next major upgrade we plan to start working on supporting conditional logic branching in automations. This would enable customers to exit the drip campaign early if they've completed a purchase, and not get any subsequent emails. E.g. after sending the first email the system could check if the customer purchased any/specific product, stop the automation if they did, or send a follow-up email if they didn't.

Would that fit your needs?

Unfortunately, I don't yet have an ETA, but we're currently getting close to releasing trigger filters, which will enable you to run campaigns for first time or repeat customers, and will explore branching next.

Tautvidas: Hey! Thank for the reply. This sounds amazing and exciting. Knowing this is planned makes it cool, even if there is no ETA yet.

I think it does fits my needs yes, at least partially.

In the plan you got, what conditions have you thought about exploring in the initial stages? I ask because it would be great if those conditional branches are able to check if the user has another automation in the processing stage. For example, the user has joined the Prospects automation feed, then buys the service in question and starts the Onboarding automation feed. At this stage, he should not get any remaining Prospects feed emails, as it is not required anymore. Hope this is included hehe.

I would even take it one step further and allow admins to manually terminate an automation for a specific client.... but this can wait a bit longer haha.

Thank you!

Tautvidas: Hi! Do you have now more clear ETA for conditional logic? I think its the only thing that its missing on automations to start a robust tool and start working more in advance with it. Good job!

Ivan Martinez: we aim for October-November.