← All templates

Fitness

Membership Lapse Win-Back

Members do not cancel when they decide to leave; they cancel three weeks after they stopped coming. This workflow reads attendance weekly, finds the members who have not been in for a fortnight, sends a note that offers help rather than guilt, and books a call for anyone at three weeks — because a member who has not attended in a month is a cancellation that has not been processed yet.

7 stepsRequires Zapier Starter or higher20 minMedium
Google SheetsGmailTwilioTodoistSchedule by ZapierFilter by Zapier

What you get

Absent members are identified at fourteen days, while they can still be recovered.
The outreach offers a route back rather than making them feel caught out.
Long absences become a booked conversation instead of a cancellation email.

Workflow blueprint

SC
When this happens
Schedule by ZapierEvery Week
1GS
Google SheetsLookup Spreadsheet Row
2FI
Filter by ZapierOnly continue if
3GM
GmailSend Email
4TW
TwilioSend SMS
5GS
Google SheetsUpdate Spreadsheet Row
6TO
TodoistCreate Task

The full blueprint — every field mapping, example value and the written copy for each message — is included with purchase.

Getting it into Zapier

Build this one from the recipe. The blueprint gives you the exact trigger, action events and field mapping for all 7 steps, so it is a copy-and-paste job rather than a design job.

You need your own Zapier account. Zapier’s Free plan runs single-step Zaps only; multi-step Zaps need a paid plan, and Paths and Webhooks need Professional. How this works →

Not on Zapier?

n8n — import and go

An n8n workflow JSON ships with this template. Import it and all 7 steps arrive on the canvas wired in order, and 6 of the 7 nodes arrive with their fields already filled in — the subject lines, the message copy, the delays, the column names. Every step maps to a native n8n node.

What an import cannot carry is your credentials, and the IDs that only exist inside your own account — which spreadsheet, which channel, which board. Those stay in a sticky note under the node, listing what is already done so you do not retype it, and what is left so you can see it.

Make — build guide

A Make-specific guide ships with this template: every module in order, every field value, and the concept translations that catch people out — filters live on the links between modules, and the schedule lives on the scenario rather than in a trigger module.

Self-hosted n8n has no per-task fee, which is worth knowing if this workflow runs at volume. Platform coverage →

Setup steps

1
Run every Monday

Configure this step using the field mapping in the blueprint.

2
Find members absent for fourteen days

Configure this step using the field mapping in the blueprint.

3
Continue only for active paying members

Configure this step using the field mapping in the blueprint.

4
Send the come-back note

Configure this step using the field mapping in the blueprint.

5
Text the three-week absentees

Configure this step using the field mapping in the blueprint.

6
Raise a call task

Configure this step using the field mapping in the blueprint.

Implementation notes

  • Fourteen days is the intervention point. At thirty days the member has already mentally left and you are negotiating with a decision, not a lapse.
  • Offer the freeze before they ask to cancel. A freeze keeps the relationship and most frozen members return; a cancellation ends it.
  • Never phrase this as being caught out. "We noticed you have not attended" reads as surveillance and produces the cancellation you were trying to prevent.
  • Mindbody, Glofox, TeamUp and most access-control systems can export attendance to a sheet nightly. Do not maintain this list by hand.