Best approach for subscription plans with Fluent CRM automations
I'm setting up subscription plans using Fluent Cart and managing automations with FluentCRM. I have three main membership plans: Basic, Standard, and PRO. Each of these can be purchased as either a Monthly or Annual subscription.
Currently, I've set this up as one Fluent Cart product with variations (Basic/Standard/PRO, and then Monthly/Annual variations under each).
My challenge is: How can I trigger specific FluentCRM automations based on the exact membership plan variation purchased through Fluent Cart?
For example, when a user buys the "PRO - Monthly" variation, I need to trigger a specific "PRO Member Onboarding" automation in FluentCRM. I'm not seeing a clear way to select these specific product variations directly within FluentCRM's automation triggers.
My questions are:
- Is there a clear method within FluentCRM's automation triggers to identify which specific Fluent Cart product variation was purchased (e.g., "PRO" vs. "Standard")?
- If not, would the recommended approach be to set up three separate Fluent Cart products (one for Basic, one for Standard, one for PRO), with Monthly/Annual as variations within each of those products?
- If I go with separate products (Question 2), what is the best practice for managing upgrade/downgrade paths between these distinct products in Fluent Cart, and how would that interact with FluentCRM automations? Would this become a manual process?
I'm looking for guidance from anyone with experience in setting up subscription plans with Fluent Cart (or Woo....)
and FluentCRM automations.
Thank you!
Shahjahan Jewel , Could you possibly give me a hint on the best approach for this please?
Could anyone who uses sure cart or even woo, chime in here and let me know. Im new to this, and any help would be greatly appriciated!
Luke HubCo at the moment my way would be to go with 3 separate products and their associated automations for "subscription created" and "subscription cancelled"....in the first automation i would have 1 action "add tag" and 2 actions "remove tag" (in case they already have a tag because of an other subscription they are already in). The second automation (cancelled) would take care that every access gets removed when the subscription is cancelled.
e.g. PRO: Product PRO is bought > FCRM Trigger "Subscription created" (PRO) > add TAG Pro > remove TAG Basic/ Standard (in case they have it - all their previous access gets removed) > give access to everything that comes with PRO
As i'm writing this: The only downside of my workaround at the moment is, that i don't see a subscription cancelled trigger at the moment in FCRM either.
Which means: Shahjahan Jewel please give us a "subscription cancelled" trigger and maybe also give us the possibility to choose certain variations of a product as a trigger of an automation and not only the product as a whole
Manuel Müller Thanks Manuel, yeah was thinking its the only solution. Will go over the tag setup and try it out. Thank you very much for your reply!