Will it be possible to add API to create edit and launch, campaigns, emails, etc? thanks!

Hi everyone!

Just wanted to share a quick update that might be useful for those running multilingual WordPress sites and use FluentCRM.

Linguise – WordPress-friendly translation tool – now automatically translates FluentCRM emails based on each contact’s language. Super handy if you want to send the right message in the right language, without extra work. Just flip the toggle in your Linguise dashboard, and new emails will match your contacts’ language settings automatically. This applies to new contacts added after the feature is enabled.

You can find more details and setup guide here.

Give it a try and let me know what you think!

After spending way too much time searching the FF and FCRM Facebook groups with no luck (big surprise), I remembered there is a community for this! I searched here, but still didn't find a solution.

I need to create both a contact AND a company in FluentCRM Pro from a Fluent Forms Pro submission (all plugins updated to most recent version).

I've tried (with no luck):

1. Looking for company creation in FluentCRM feed settings
2. Using "Apply Company" in automations (only allows selecting existing companies)
3. Fluent Forms/Snippets code hooks

What am I missing?! Webhooks? Action/Filter hooks? My mind?

Has anyone implemented automatic company creation from Fluent Forms that creates a company and contact from one FF submission?

My coffee budget is depleted and it's way past my bedtime trying to figure this out. Any help is much appreciated! 🙏☕😴

Each contact could be assigned points when opening email, clicking a smart link, filling a form, booking an event, etc. These points would accumulate over time resulting in an engagement score.

We're thrilled to announce the latest update to FluentCRM! Version 2.9.60 brings powerful new features, enhanced customization options, and important bug fixes.

🚀 WHAT'S NEW

Built-in Templates - Save time with our new collection of ready-to-use email templates.

List-wise Double Opt-in Settings - Configure double opt-in emails separately for each list, giving you more control over subscriber verification.

Voxel New Order Placed Trigger - Automatically engage with customers when they place new orders through Voxel.

Transactional Email Flexibility - Send custom emails as transactional emails, improving deliverability for important messages.

Enhanced Company Profiles - Added custom menu tab functionality on company profile pages for better organization.

Dynamic WooCommerce Segments - Create segments based on active WooCommerce subscriptions for targeted marketing.

Developer Improvements - New Contact Unsubscribe hook and bulk add/update contacts REST API endpoint for better integrations.

FIXED ISSUES

• Resolved sorting issues in the Purchase History tab of Contact Profiles

• Fixed multi-line text issues in Custom Fields

• Corrected CSV export problems with contact filters

• Fixed link tracking in Campaign details Link Stats

Plus several other improvements and bug fixes to enhance your overall experience!

Read the full release post here - https://fluentcrm.com/fluentcrm-2-9-6/

really love the update! Especially the list-unsubscribe option.

Also, it would be great if the 'Send Custom Emails as Transactional Email' would also work in automations 😀

We currently have a lead form on our site. When someone submits it, we want to redirect them to the next step in the funnel (instead of just showing a success message).

At the same time, we send a double opt-in email that includes a dynamic #confirmation_url#. When the user clicks this link, it currently takes them to the funnel redirect URL.

Instead, we want the #confirmation_url# to confirm their opt-in and log them into the Fluent community dashboard.

Is there a way to have the form submission redirect users to the next funnel page, while the #confirmation_url# in the email confirms the opt-in and sends them to the Fluent community?

Hi,

I need help organizing my automations in FluentCRM and the access rules set up in FluentCommunity. I believe my current configuration is incorrectly applying access tags, and I want to ensure that only the right users get access to the members area.

Here’s a summary of my situation:

I have a membership site with different types of users:

• Old members from 2024 (manually migrated and tagged via FluentCRM inside FluentCommunity settings)
• Monthly subscribers (with an automation based on WooCommerce order, set up yesterday)
• Annual subscribers (also using WooCommerce order-based automation)
• Free access users (who shouldn't have full access — WooCommerce order with value 0€, automation created yesterday)

I’ve created different tags in FluentCRM to identify each group, and I use automations to assign access via FluentCommunity based on these tags.

However, something is wrongly assigning the “Old Members 2024” tag to every new member — including free users. This breaks the whole access control system and is giving unauthorized access.

At this point, I’ve disabled FluentCRM tag management in FluentCommunity settings to avoid more errors, but I really need help to properly reorganize everything.

Here’s what I’d appreciate your help with:

1. How can I correctly reassign tags and access to the proper users?
2. Can I move existing users into the automations where they should have been originally?
3. Is there a best practice to avoid assigning incorrect tags in the future, especially for free users?

I can share screenshots of my automations and tag settings in FluentCommunity if that’s helpful.

Thanks in advance for your support!

Best regards,
Sofia

I was wondering if there were any plans to connect Booking with the CRM at all. It would be really good to be able to click a 'booking link' from within the specific contact screen, with customer details being available or transfered automatically when manually booking?

I would like to be able to see all automations that reference a specified tag, especially for triggering on a tag, but I would like to be able to see all automations that have an action involving a tag. Right now it is difficult to know what automations reference a tag, either as a trigger, an action, or a goal.

#idea #request