Skip to content
English
  • There are no suggestions because the search field is empty.

Membership Ended Trigger Block

The Membership Ended trigger starts an automation when a contact’s membership ends in Patch. This is ideal for churn prevention, win-back campaigns, and “what happens next” messaging.

What’s in This Article

 


 

What This Trigger Does

The Membership Ended trigger fires when:

  1. A membership record is marked ended/expired/canceled (integration dependent) or reaches End At

  2. Patch records the membership ending

  3. The automation receives the event + contact information

In simple terms:
“Run this automation when the membership is expired/no longer active.”

 


 

When to Use This Trigger

Use Membership Ended when you want to:

  • Send a “membership ended” confirmation

  • Offer a renewal link or rejoin incentive

  • Start a win-back flow for churned members

  • Tag contacts as “Former Member”

  • Trigger internal follow-up for high-value plans

 


 

When Not to Use This Trigger

Use other triggers when the workflow depends on:

  • Visits (Check-In Finished)

  • Purchases/revenue (Order Finished)

  • Scheduled reminders (Calendar Event)

  • Field changes (Contact Updated)

 


 

Block Settings Explained

Details (Info Panel)

Informational summary of how the trigger works.

 


 

Add Conditions

Common filters:

  • Product / Product ID

  • Status (ended, expired, canceled)

  • End At

  • Tags []

Tip

If trials should not be treated as churn, filter them out by Product or Tag.


Trigger Event Fields (What You Can Filter On)

Trigger fields commonly include:

  • Product 

Membership fields on the contact record may include:

  • Memberships [] → End At

  • Memberships [] → Status

  • Memberships [] → Next Billing At

  • Memberships [] → Product ID

  • Memberships [] → Tags []

 


 

Common Use Cases

  • Renewal reminder + rejoin link

  • Exit survey / feedback request

  • Win-back series (3–14 day cadence)

  • Staff follow-up for VIP churn

  • Downgrade offer instead of cancel

 


 

What Data This Trigger Has Access To

This trigger includes:

  • Contact fields

  • Membership fields stored on the contact record (product, status, start/end, next billing, tags)

 


 

Important Things to Know

  • Membership end timing depends on integration sync frequency.

  • Some systems mark “canceled” before the membership actually ends. Decide if you want to trigger on cancel status, End At, or both.

 


 

Example Automations

Example 1: Renewal Win-Back

  1. Trigger: Membership Ended

  2. Send: “Want to rejoin?” + SmartLink

  3. Delay: 3 days → reminder

  4. Delay: 7 days → with offer

Example 2: VIP Save Attempt

  1. Trigger: Membership Ended

  2. Condition: Product = “VIP”

  3. Notify staff + tag “VIP Churn Risk”

  4. Send personal outreach message

 


 

Best Practices

  • Filter by Product so the message matches the plan.

  • Keep win-back simple: one clear offer + one clear link.

  • Add internal alerts for high-value memberships.