Skip to main content

FluentCRM

Move contact inside the funnel

Is there a way to apply this kind of action for moving the contact to a different position at a certain point of the funnel?

I couldn't find anything like that... In my opinion it's quite an important missing action if it's not available!

Move contact inside the funnel
  • 2 likes
  • 5 comments

Jorge de los Reyes

You may want to try "Goals"

With this, you can check the option so as contacts enter directly to that point if conditions are meet (eg.: Tag added). Or mix it with conditionals, so as not to allow continuation of grant it depending on previously determined conditions.

There's currently, no option like "Go to other action" (like on Active Campaign, Keap or alike). But with Goals, and the proper condition, you may find a workaround.

Hope it helps, even, it's not the proper "action" we would love to see on core.

Also, I am not taking here into account, that you can develop this kind of workaround too, with more granular control, on your own with plugins, or custom snippets using hooks and the rest of the docs. But, I will try this approach first before losing yourself reading those :)

Marco Mandaliti

Thanks, Jorge de los Reyes 

I'll try this workaround in the meantime, but In case I would think about the second option (custom plugin or snippet), for sure I will let Claude doing it! 😁

I'll take this opportunity to ask you something else: how would you manage the fact that also nested "Yes/No Conditions" are not available?

In the automation I'm trying to replicate there's a ton of nested Y/N (example of a segment in the screenshot)...

Jorge de los Reyes

Marco Mandaliti God bless AI 🫠

Quick fix: use the Conditional element. It’s flexible enough for most cases.

Real talk: the issue isn’t the logic. It’s the variables. Not everything is exposed natively in the ecosystem. Sadly…

So you’ve got 3 plays:

  1. Go external (n8n, etc.): unlimited nested logic, filter by anything in your CRM/stack.

  2. Extend variables: some devs already add missing ones.

  3. I build it: if you’re missing a variable, ship a small snippet/plugin so it’s native.

Yes, you can build anything (dashboards, custom plugins, deeper automations).

But here’s the rule, and my take: keep it stupid simple.

Complexity is where automations go to die 😅

JF

This action is essential! I'm planning to migrate from Brevo to FluentCRM 3.0 (when it's available) and in Brevo I am using this action a lot. I hope Shahjahan Jewel  and the team can add this option soon.

Ioannis Glossopoulos

+1