I understand subscribers can manage their own subscription status such as by using the links at the bottom of email campaigns. And I can manually change the status of contacts or do it in bulk. But there should be an action in Automations that allows me to automatically unsubscribe contacts. For example, if a contact's WP User role changes, I might want to unsubscribe them.
Hello guys.
I tried to create a custom payload at http module un automations. I needed {{order.id}} but it doesn't exist.
Can you Include it?
It is also include using segments as triggers?
Keep the great work, guys.
I am thinking about using FluentCRM for my E-Mail-Marketing since I use FluentCart and FluentCommunity as well. But I am a little bit worried if my current shared-hosting can handle that without slowing my website down... I don't sent that much mails atm (~150 subscribers), but of course I want my list to grow steadily.
What would be the recommended specifications for the hosting to run smoothly without having an impact on speed and stability?
I've visited the docs and am trying to figure out the right kinds of workflows to manage the SMS Subscribed status. Everywhere there's bulk management of Status it doesn't specify if its the SMS or email status - How do I manage that via bulk actions AND via automations?
Hi everyone!
I want to move from Brevo to FluentCRM, but I can't find a way to replicate this kind of nested Conditional Actions.
The Conditional Actions in FluentCRM have a common endpoint for both the Yes and No paths. I need separate paths where I can keep adding Conditional Actions to each path independently.
Shahjahan JewelΒ Ashim ShilΒ Is this a limitation of FluentCRM, or is there a way to set up Conditional Actions like this?
Thanks in advance!

FluentCRM is a fantastic product. The feature set and maturity, like all Fluent / WPManageNinja apps (even when in beta which amazes me). But...it is really not a CRM. To get to that point, I think you really need these functions: Lead Management, Opportunity Management, Sales Pipeline Tracking, Forecasting, Lead Scoring, NBD assignments, Sales team assignments, etc etc
Reporting & Dashboards. Any insights as to when these critical functions come live to move the product from a Marketing Automation Platform to CRM?
Hello everyone. I have a question that might sound dumb.
If I schedule a campaign including a list which include for eg. 50 people, but then in the meantime other 10 people subscribe to that list, the campaign is sent to the fist 50 or also to the new subscribed ones, so 60 in total?
What is the worldwide state of dark mode "compatibility" in email campaigns? Is it (even) possible (yet) using FluentCRM's Gutenberg email builder (which I like), to create campaigns that honor the user's device "system dark mode" setting? (white background turns dark, darker fonts turn light)
I understand this likely isn't a fluentCRM-specific issue and more of an email HTML limitation with "antiquated" email applications.
Just checking in β any plans on allowing phone numbers as the primary identifier when an email is missing?
Currently, we have a FluentCRM Board for 'Client Acquisition'. Within this, we have:
- the Stages 'Started', 'Contacted', 'In Progress', 'Waiting For Payment' and 'Closed'
- each potential client has a task created from a template task with subtask groups 'Scoped', 'Interested - Draft', 'Interested - Pending Signature and Deposit' and 'Onboard'.
- within the potential client's task, subtasks are used to track where, within the sales pipeline, they are.
This requires manual updating of the subtasks completion status, and then the next subtasks assignment and due date manually added. The current 'Stage Changed' action does not work for this work for this workflow, as it would end up with duplicate tasks for a single contact.
In future, 'When a subtask is completed' (Trigger) within of these groups is completed, it would be good to be able to have 'Create a new subtask' (Action) and configure the new subtasks:
- subtask group
- assign the CRM contact responsible
- set how many days later the due date should be.




