Membership Started Trigger Block

What’s in This Article

• What this trigger does

• When to use this trigger

• When not to use this trigger

• Block settings explained

• Trigger event fields

• Common use cases

• What data this block uses

• Important things to know

• Example automations

• Best practices

 

---

 

What This Trigger Does

The Membership Started trigger fires when:

1. A membership record exists for a contact in Patch

2. The membership Start At date/time is reached (has passed)

3. Patch sends the membership start event into the automation

In simple terms:
“Run this automation when the membership start date is active.”

 

---

 

When to Use This Trigger

Use Membership Started when you want to:

• Send a welcome/onboarding sequence for new members

• Share how to use benefits (booking rules, guest passes, perks)

• Confirm membership details (plan name, start date, next billing date)

• Kick off a “first 7 days” drip campaign to reduce early churn

• Tag or segment contacts by membership product

 

---

 

When Not to Use This Trigger

Don’t use this trigger if your workflow should start from a different event:

• Order Finished → purchases and revenue/product details

• Check-In Finished → visits/check-ins

• Calendar Event → reminders tied to scheduled times

• Contact Created → brand new contacts entering Patch

• Contact Updated → field-change logic (tags, email engagement, etc.)

 

---

 

Block Settings Explained

Details (Info Panel)

This section explains how the trigger works. It’s informational only.

---

Add Conditions

Use Add Conditions to limit which memberships trigger the automation.

Common filters:

• Product / Product ID (only run for specific membership plans)

• Status (only run for “Active” or equivalent statuses)

• Start At (only run for memberships starting after a certain date)

• Tags [] (if membership tags are synced from your integration)

Tip

If you have multiple membership products, filter by Product so each plan can have its own onboarding.

---

Trigger Event Fields (What You Can Filter On)

You’ll typically see trigger fields like:

• Product 

You can also filter using membership fields on the contact record (often under Memberships []):

• Memberships [] → Start At

• Memberships [] → Next Billing At

• Memberships [] → End At

• Memberships [] → Status (Active, Expired)

• Memberships [] → Product ID (Opens products popup)

• Memberships [] → Tags []

 

---

 

Common Use Cases

• Membership onboarding + benefit education

• “How to book” member message

• Plan-based tagging (example: “Plan – Gold”)

• VIP plan internal alerts

• Retention cadence during the first month

 

---

 

What Data This Trigger Has Access To

This trigger includes:

• Contact fields (standard + custom)

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

 

---

 

Important Things to Know

• Memberships in Patch are currently created by integrations (not manually created in Patch).

• Some integrations sync on a schedule, so timing depends on when Patch receives membership data.

• Plan-specific conditions prevent the wrong members from getting the wrong onboarding.

 

---

 

Example Automations

Example 1: Membership Onboarding (Day 0–7)

1. Trigger: Membership Started

2. Condition: Product = “Monthly Unlimited”

3. Send: Welcome message + benefits

4. Delay: 2 days → send booking tips

5. Delay: 5 days → send “Need help?” check-in

6. Eject if Order Finished or Checkin Finished triggers

Example 2: VIP Plan Alert

1. Trigger: Membership Started

2. Condition: Product = “VIP”

3. Create internal notification/task for staff - Send Email or Send SMS to staff member

4. Add tag: “VIP Member”

 

---

 

Best Practices

• Use one onboarding automation per membership plan (filter by Product).

• Add a short delay before the second message to avoid overwhelming new members.

• Always include one clear next step (book, redeem perk, contact support).