FluentCRM Integration #

The FluentCRM integration for Flexi Subscription lets you connect subscription lifecycle events directly with FluentCRM Automations.

Unlike a basic webhook or generic event bridge, Flexi Subscription adds native subscription triggers inside FluentCRM, so you can build CRM workflows around subscription activity without manually entering hook names.

The integration is available with Flexi Subscription Pro and requires FluentCRM to be installed and active.

Requirements #

Before configuring the integration, make sure you have:

• Flexi Subscription installed and activated
• Flexi Subscription Pro installed and activated
• FluentCRM installed and activated
• FluentCRM Automations available on your site

Flexi Subscription detects FluentCRM through its automation system and loads the integration only when the required FluentCRM automation classes are available.

Enable the FluentCRM Integration #

From your WordPress dashboard:

1. Go to Flexi Subscription → Integrations.
2. Locate FluentCRM under the Marketing & CRM section.
3. Make sure FluentCRM is installed and active.
4. Enable the FluentCRM integration.

Once enabled, Flexi Subscription registers its native subscription triggers inside FluentCRM.

If FluentCRM is unavailable or the integration is disabled, Flexi Subscription simply skips FluentCRM processing and continues normal subscription operations.

Native FluentCRM Triggers #

Flexi Subscription currently provides the following native FluentCRM automation triggers.

Subscription Activated #

Triggered when a subscription becomes active.

Typical uses include:

• Customer onboarding
• Welcome campaigns
• Membership activation communication
• Product-specific email sequences
• Customer tagging
• CRM pipeline updates

Subscription Pending #

Triggered when a subscription enters the Pending state.

Typical uses include:

• Pending-payment reminders
• Follow-up sequences
• Payment instructions
• Internal CRM notifications

Subscription Cancelled #

Triggered when a subscription is cancelled.

Typical uses include:

• Cancellation confirmation
• Feedback requests
• Retention campaigns
• Win-back campaigns
• Removing active-member tags
• Updating customer lifecycle stages

Subscription Expired #

Triggered when a subscription reaches the Expired state.

Typical uses include:

• Expiration notices
• Re-subscription campaigns
• Customer reactivation sequences
• CRM segmentation updates

Grace Period Started #

Triggered when an eligible subscription enters its configured grace period.

Typical uses include:

• Payment recovery automations
• Failed-payment reminders
• Update-payment-method campaigns
• Internal follow-up tasks
• Adding payment-risk tags

Grace Period Ended #

Triggered when a subscription’s configured grace period has ended and the lifecycle reaches the applicable expired state.

Typical uses include:

• Final payment recovery communication
• Removing temporary grace-period tags
• Access-ended notifications
• Re-subscription campaigns
• Customer lifecycle updates

Creating a FluentCRM Automation #

Once the integration is enabled:

1. Go to FluentCRM → Automations.
2. Create a new automation.
3. Choose one of the Flexi Subscription triggers.
4. Configure the trigger settings.
5. Add the FluentCRM actions you want to perform.
6. Publish the automation.

Only published FluentCRM automations are processed.

Draft or unpublished automations are ignored.

Trigger Settings #

Each Flexi Subscription FluentCRM trigger includes subscription-specific controls.

Contact Status #

You can choose the FluentCRM contact status that should be applied when the customer enters the automation.

For example:

• Subscribed
• Pending
• Other FluentCRM-supported statuses

This lets the automation work with your existing FluentCRM contact-management strategy.

Target Products #

You can restrict an automation to selected subscription products.

For example:

Automation:
Subscription Activated

Target Products:
Gold Membership
Premium Membership

The automation will run only when the subscription belongs to one of those selected products.

If no products are selected, the automation applies to all supported subscription products.

Product Matching #

Flexi Subscription supports matching against:

• simple subscription products
• variable subscription products
• specific subscription variations
• parent products associated with variations

This makes it possible to build different automation journeys for different subscription products or plan levels.

Restart Automation Multiple Times #

Each trigger includes an option to control whether the same contact can enter the automation multiple times.

Disabled #

If the customer has already entered that automation for the event, Flexi Subscription skips it.

Conceptually:

Customer already in automation
        ↓
Run Multiple = No
        ↓
Skip

Enabled #

Flexi Subscription removes the previous funnel enrollment and starts the automation again.

Conceptually:

Customer already in automation
        ↓
Run Multiple = Yes
        ↓
Remove previous enrollment
        ↓
Restart automation

This is especially useful for lifecycle events that can happen more than once.

For example:

• a subscription becomes active again
• the customer enters another grace period
• the subscription moves back to pending after a failed renewal

Subscription Data Used by FluentCRM #

When Flexi Subscription starts a FluentCRM automation, the integration provides the core identifiers required to load the customer and subscription context.

The trigger payload includes:

• user_id
• email
• subscription_id
• status

The native FluentCRM trigger then loads the subscription through Flexi Subscription’s existing data layer.

This avoids duplicating subscription data inside FluentCRM-specific storage.

Example Automation Workflows #

New Subscription Onboarding #

Trigger: Subscription Activated

Possible workflow:

Subscription Activated
        ↓
Add Active Subscriber Tag
        ↓
Add to Customer List
        ↓
Send Welcome Email
        ↓
Wait 3 Days
        ↓
Send Getting Started Email

Product-Specific Onboarding #

Trigger: Subscription Activated

Target Products: Gold Membership

Possible workflow:

Gold Membership Activated
        ↓
Add Gold Member Tag
        ↓
Send Gold Member Welcome Email
        ↓
Start Premium Onboarding Sequence

Customers subscribing to other products will not enter this automation.

Pending Payment Follow-up #

Trigger: Subscription Pending

Possible workflow:

Subscription Pending
        ↓
Add Payment Pending Tag
        ↓
Send Payment Reminder
        ↓
Wait
        ↓
Send Follow-up Email

Cancellation Follow-up #

Trigger: Subscription Cancelled

Possible workflow:

Subscription Cancelled
        ↓
Remove Active Subscriber Tag
        ↓
Add Cancelled Subscriber Tag
        ↓
Send Cancellation Confirmation
        ↓
Send Feedback Request
        ↓
Start Win-back Campaign

Expiration Campaign #

Trigger: Subscription Expired

Possible workflow:

Subscription Expired
        ↓
Update Contact Lifecycle
        ↓
Send Expiration Notice
        ↓
Wait
        ↓
Send Re-subscription Offer

Grace Period Recovery #

Trigger: Grace Period Started

Possible workflow:

Grace Period Started
        ↓
Add Payment Problem Tag
        ↓
Send Payment Recovery Email
        ↓
Wait
        ↓
Send Final Reminder

Grace Period Ended #

Trigger: Grace Period Ended

Possible workflow:

Grace Period Ended
        ↓
Remove Grace Period Tag
        ↓
Add Expired Customer Tag
        ↓
Send Access Ended Email
        ↓
Start Re-subscription Campaign

Using FluentCRM Actions #

Once a Flexi Subscription trigger starts an automation, you can use normal FluentCRM automation actions.

Depending on your FluentCRM installation, these can include:

• Send email
• Add tag
• Remove tag
• Add to list
• Remove from list
• Update contact properties
• Add delays
• Add conditions
• Create branches
• Send webhooks
• Start internal CRM workflows

Flexi Subscription provides the subscription event.

FluentCRM controls what happens afterward.

Product Filtering Example #

Suppose your store has:

• Basic Membership
• Gold Membership
• Business Membership

You could create three separate automations.

Basic Automation #

Trigger:
Subscription Activated

Target Product:
Basic Membership

Gold Automation #

Trigger:
Subscription Activated

Target Product:
Gold Membership

Business Automation #

Trigger:
Subscription Activated

Target Product:
Business Membership

Each customer enters only the automation that matches their subscription product.

Variable Subscription Products #

The FluentCRM integration supports variable subscription products.

When a customer purchases a subscription variation, Flexi Subscription can evaluate:

• the variation ID
• the parent product ID
• the canonical subscription product relationship

This allows FluentCRM product targeting to work with variable subscription products instead of matching only simple products.

Multiple Automations for the Same Trigger #

You can create more than one published FluentCRM automation using the same Flexi Subscription trigger.

For example:

Subscription Activated
    ├── Customer Onboarding Automation
    ├── Internal Sales Notification Automation
    └── Product Education Automation

When the event occurs, Flexi Subscription can start all matching published automations.

Draft automations are ignored.

Integration Safety #

The FluentCRM integration is isolated from the core subscription lifecycle.

If FluentCRM throws an error while:

• loading an automation
• checking product conditions
• preparing a contact
• checking an existing funnel
• restarting an automation
• processing a funnel

Flexi Subscription catches the integration failure instead of allowing it to interrupt the subscription operation.

For example:

Subscription becomes Active
        ↓
FluentCRM automation fails
        ↓
FluentCRM failure logged
        ↓
Subscription remains Active

This protects critical workflows such as:

• checkout
• activation
• renewal
• cancellation
• expiration
• grace-period processing

Logging #

FluentCRM integration failures can be logged through WooCommerce logging.

The integration uses the log source:

flexi-wc-subscriptions-pro-fluentcrm

This can help diagnose:

• automation failures
• invalid contacts
• FluentCRM compatibility issues
• trigger-registration problems

Disabling the Integration #

You can disable FluentCRM without uninstalling the plugin.

Go to:

Flexi Subscription → Integrations → FluentCRM

and disable the integration.

After disabling it:

• Flexi Subscription stops starting new FluentCRM subscription automations.
• Existing subscriptions remain unchanged.
• Existing FluentCRM contacts remain unchanged.
• FluentCRM continues working for its other automations and integrations.

Troubleshooting #

FluentCRM Shows as Unavailable #

Check that:

• FluentCRM is installed.
• FluentCRM is activated.
• Flexi Subscription Pro is active.
• FluentCRM’s Automation system is available.

Flexi Subscription checks for FluentCRM’s automation capability rather than relying only on a plugin folder name.

FluentCRM Is Active but the Integration Is Disabled #

Go to:

Flexi Subscription → Integrations

and enable FluentCRM.

Flexi Subscription Triggers Do Not Appear #

Check that:

• FluentCRM is active.
• Flexi Subscription Pro is active.
• FluentCRM integration is enabled.
• FluentCRM Automations are available.

The native triggers are registered only when FluentCRM’s automation system is ready.

Automation Does Not Run #

Check that:

• the automation is published
• the correct Flexi Subscription trigger is selected
• the subscription actually entered the required lifecycle state
• the customer has a valid WordPress user account and email
• the Target Products setting matches the subscription product
• the Run Multiple setting is appropriate for your workflow

Automation Works for One Product but Not Another #

Check the Target Products field.

If products are selected, only matching subscriptions will enter the automation.

For variable subscription products, check both the variation and parent-product configuration.

Customer Does Not Enter the Automation Again #

Check:

Restart Automation Multiple Times

If disabled, FluentCRM will not restart the same automation for a contact who has already entered it.

Enable this option when repeated lifecycle events should restart the workflow.

Subscription Works but FluentCRM Does Not #

This can happen because FluentCRM failures are intentionally isolated from subscription processing.

The subscription can still:

• activate
• renew
• cancel
• expire

even if FluentCRM cannot process the associated automation.

Check WooCommerce logs using the source:

flexi-wc-subscriptions-pro-fluentcrm

Frequently Asked Questions #

Is FluentCRM available in Flexi Subscription Core? #

The FluentCRM automation integration requires Flexi Subscription Pro.

Core provides the subscription lifecycle and integration-management foundation used by Pro.

Do I need to manually enter WordPress hook names? #

No. Flexi Subscription registers native triggers that appear directly inside FluentCRM Automations.

Can I create different automations for different products? #

Yes. Use the Target Products setting in the trigger.

Does it support variable subscription products? #

Yes. The integration supports variation and parent-product matching.

Can the same customer run the automation more than once? #

Yes. Enable: Restart Automation Multiple Times for the trigger.

What happens if FluentCRM fails? #

FluentCRM errors are isolated from the main Flexi Subscription lifecycle so the external CRM integration does not prevent the underlying subscription operation from completing.

Which triggers are currently available? #

The integration currently provides:

• Subscription Activated
• Subscription Pending
• Subscription Cancelled
• Subscription Expired
• Grace Period Started
• Grace Period Ended

Is Pending Cancellation available? #

Not currently. Flexi Subscription does not currently maintain a separate Pending Cancellation lifecycle state, so the integration does not expose a synthetic trigger for it.

Can I use multiple FluentCRM automations for the same subscription event? #

Yes. Multiple published automations can use the same Flexi Subscription trigger, and each matching published automation can run when the event occurs.