The plan-type filter in the last step matters more than it looks: a recipe built against “has an expiry date” instead of “is on the annual plan” will eventually catch a monthly member mid-cycle and confuse them. Spell out the filter before building.
Automation
Remind members before their subscription expires
A scenario prompt that converts a described membership-expiry-reminder workflow into a recipe covering multi-touch timing, renewal-in-progress, and failed-payment overlap.
Works with Claude / GPT380 uses★ 3.9
The prompt
automation-membership-expiry-reminder
A membership site describes their process like this: "I want members emailed 7 days before their annual membership expires, reminding them to renew, with a link to their account page, and I don't want to email them again if they've already renewed." AVAILABLE TOOLS: [MemberPress (trigger), Uncanny Automator, email/SMTP, MemberPress subscription status] Turn this into an implementation-ready automation recipe, thinking through what the plain description leaves ambiguous: 1. Trigger: since MemberPress doesn't fire an event "7 days before expiry" natively, decide what scheduled check runs daily against expiry dates, and confirm it queries against a rolling window rather than an exact date match, so a member isn't skipped if the daily check runs a few hours late. 2. Conditions: state the exact logic to skip a member who already renewed between the scheduled check and the send, and also skip members on a subscription marked for cancellation who shouldn't be nudged to renew at all. 3. Actions in order: decide whether one reminder at 7 days is enough or whether a second reminder at 1 day before expiry is needed for members who haven't acted, and specify the exact condition that suppresses the second email if they renewed after the first. 4. Failure handling: if the renewal payment fails silently in the background (card declined) right after the reminder goes out, should a separate "payment failed" email fire, or does that count as a duplicate touch the member will find annoying. 5. One edge case specific to this exact workflow: a lifetime or monthly member accidentally caught by the same recipe meant only for annual members. Confirm the condition filters by membership plan, not just presence of an expiry date. Replace the workflow description and available tools with your own.