AutomatorWP FluentCRM Addon

Removing a tag is a signal too, and your site is not hearing it

Someone cancels, your team removes their customer tag in FluentCRM and the contact is correctly classified. But in WordPress everything stays the same: same access, same list, same group. The CRM changed its mind about that person and the rest of the site never found out.

Almost everything automated around a CRM starts with adding: add a tag, add to a list. But what the CRM decides to take away is information too. The free FluentCRM integration in AutomatorWP already reacts when a tag is added, when someone joins a list or when a status changes. This add-on covers the other side: reacting when something is removed, and working directly on contacts.

What the add-on adds to the free integration

Triggers, for both users and anonymous contacts:

• A tag is removed.
• Someone leaves a list.

Actions on users and on contacts:

• Create a contact.
• Remove a tag from a user, or add and remove one on a contact.
• Create a tag and assign it to a contact.
• Remove a user from a list, or add and remove a contact.
• Change a contact's status.

Filters:

• The user has or does not have a tag.
• The user is or is not in a list.

The free part also brings two actions, add a tag to a user and add them to a list, and the data tags with the contact's fields.

Combinations it opens, to test before trusting them

These recipes are combinations of separate pieces, and they depend on the other plugins on your site. Try them with a test contact.

• Tag removed, access removed. The tag removed trigger starts an action from another AutomatorWP integration on your site, for example in your membership plugin.
• Visitor without an account, contact created. An anonymous automation can create a user or use an existing one, and end in the create contact action.
• Leave a list and clean up. When someone leaves a list, another action changes their status or gives them a follow-up tag.
• A rule with a condition. Tag or list filters make the same automation act only on those who meet the condition.

Where the add-on ends and FluentCRM begins

• It does not replace FluentCRM. Campaigns, sequences and sending stay there. Among its actions there is no sending a campaign or starting a sequence.
• Among its triggers there are no email opens or clicks. It reacts to tags, lists and statuses, so those events would first have to become a tag inside FluentCRM.
• Its filters look at the user. All four check a user's tag or list; none of them is by status.

What needs to be installed and the first flow

You need AutomatorWP and FluentCRM active. To build the first automation:

1. Go to AutomatorWP, Automations, and click Add new automation.
2. Choose the type: logged-in users or anonymous.
3. Add a FluentCRM trigger, for example tag removed, and select the tag.
4. Add the actions that should happen next.
5. Test it with a test contact before leaving it active.

If you need more pieces or prefer another engine

FluentCRM Pro adds store, course and membership triggers inside the CRM itself: if what you want is for the CRM to know what happens on your site, it may be enough without AutomatorWP.

Webhooks connects AutomatorWP with external services compatible with webhooks or a REST API. And Uncanny Automator Pro is another automation engine inside WordPress, based on recipes, with conditions that include CRM tags.

Notes on triggers and contacts

Do I need this add-on to react to a new tag?

No. That trigger is in the free integration. The add-on is needed for a removed tag.

Does it work with people who have no WordPress account?

Yes. It has anonymous triggers for contacts, and an anonymous automation can create a user or use an existing one.

Can I use the contact's fields in other actions?

Yes, through the data tags for fields and custom fields.

How many steps does an automation allow?

As many triggers and actions as you want.