Skip to content

Patreon Churn Saver · Creators & Studios

Win back lapsed patrons and learn why they left

Declined payments and ended pledges get a kind, approved note with your one-question survey; each week the reasons are counted and posted to Slack.

Available now $69 one-time · never renewsIncluded in Enterprise
Get this agent See how it works

Free account to start. Buying and running live need a paid plan.

  • Starts from an event in a connected app
  • 1 AI step
  • A person approves before it acts
  • About 20 min to set up

Sound familiar?

The job, before and after this agent.

What it feels like today

  • “Patrons drop off when a card fails and never notice.”
  • “I have no idea why people cancel.”
  • “Writing to every lapsed member feels awkward, so I don't.”

What you get with the agent

  • Every declined payment or ended pledge is logged to your sheet.
  • AI writes a kind note for the situation: how to update a declined payment, or thanks and what's coming for a member who left.
  • You approve each note; it goes from your Gmail with your one-question survey link.
  • Once a week, lapses and survey answers are counted by reason in code and posted to Slack.

Before

Three patrons lapse in a week; the creator only notices the lower total at the end of the month.

After

Each lapse gets a gentle note within the hour after a quick approval, one card gets updated, and Monday's Slack shows that most leavers chose “Not using it enough”.

How it works

The whole workflow, step by step.

When a member's payment is declined or their pledge ends, the agent logs it to your sheet and AI writes a short, kind note for that situation: how to update a declined payment, or thanks and what's coming up for a member who left (with your comeback offer only if you give one). Each note waits for your approval, then goes from your Gmail with your one-question survey link below it. Once a week, with the next lapse, code counts that week's lapses and your survey's answers by reason and posts the summary to Slack. It can't retry or refund Patreon payments.

  1. TriggerPledge declined or ended
  2. App callLog the lapse
  3. AI stepWrite the win-back note
  4. LogicCheck the note
  5. LogicReady for review?
    • Incomplete:Held: not sent
    • Review:Approve the win-back note
  6. OutputHeld: not sent
  7. Human approvalApprove the win-back note
    • Approved:Check before sending
  8. LogicCheck before sending
  9. LogicSend it?
    • Send:Email the note from Gmail
    • Held:Held after review
  10. OutputHeld after review
  11. App callEmail the note from Gmail
  12. OutputNote sent
  13. LogicWhen was the last summary?
  14. LogicSummary due?
  15. LogicSend the summary?
    • Due:Read the survey answers
    • Not due:No summary this run
  16. OutputNo summary this run
  17. App callRead the survey answers
  18. LogicKeep the last 7 days
  19. LogicEach answer
  20. OutputCounted
  21. LogicCount the reasons
  22. App callRead the lapses log
  23. LogicKeep the last 7 days
  24. LogicEach lapse
  25. OutputCounted
  26. LogicCount the lapses
  27. App callPost the weekly summary
  28. LogicRemember the summary date
  29. OutputSummary posted

This is the workflow that opens in your workspace when you set the agent up. Every step can be edited.

  1. Step 1Pledge declined or endedStarts a run when a member's payment is declined or their pledge ends (Patreon is checked every 15 minutes or so).
  2. Step 2Log the lapseAdds a row to your lapses tab (Date | Member | Email | Status | Tier | Pledge (cents) | Last charge).
  3. Step 3Write the win-back noteAI writes a short, kind note for the situation: a declined payment (how to update it) or an ended pledge (thanks, and what's coming). The survey link is added in code.
  4. Step 4Check the noteIn code: one valid member email, a subject and body with no leftover placeholders.
  5. Step 5Ready for review?Incomplete notes are held; every other note waits for your approval.
  6. Step 6Held: not sentNo member email, or the note was blank or had a placeholder.
  7. Step 7Approve the win-back noteThe note waits in Reviews: edit and approve to send it from your Gmail with your survey link. Reject to send nothing.
  8. Step 8Check before sendingIn code, after any edits: still no placeholders in the note.
  9. Step 9Send it?Passes: emailed. Otherwise held.
  10. Step 10Held after reviewAn edit left a placeholder.
  11. Step 11Email the note from GmailSends the note from your Gmail with your one-question survey link below it.
  12. Step 12Note sentThe run history keeps the note.
  13. Step 13When was the last summary?Reads the date of the last weekly summary.
  14. Step 14Summary due?In code: the summary goes out once every 7 days, with the first lapse after that.
  15. Step 15Send the summary?Not due yet: this branch ends.
  16. Step 16No summary this runThe last summary went out less than 7 days ago.
  17. Step 17Read the survey answersReads your survey's answers tab (Timestamp | Reason), e.g. a Google Form's responses sheet.
  18. Step 18Keep the last 7 daysIn code: answers from the last 7 days (your time zone).
  19. Step 19Each answerGoes through this week's answers so they can be counted (up to 200).
  20. Step 20CountedNothing is changed in the sheet.
  21. Step 21Count the reasonsIn code, not AI: this week's answers grouped by reason.
  22. Step 22Read the lapses logReads your lapses tab (Date | Member | Email | Status | Tier | Pledge (cents) | Last charge).
  23. Step 23Keep the last 7 daysIn code: lapses logged in the last 7 days.
  24. Step 24Each lapseGoes through this week's lapses so they can be counted (up to 200).
  25. Step 25CountedNothing is changed in the sheet.
  26. Step 26Count the lapsesIn code, not AI: declined payments and ended pledges this week.
  27. Step 27Post the weekly summaryPosts this week's lapses and survey reasons (counted in code) to your Slack channel.
  28. Step 28Remember the summary dateStores today's date so the next summary waits 7 days.
  29. Step 29Summary postedThe run history keeps the summary.

Example run

What goes in, and what comes out.

Example with fictional data

Comes in

Ada Lovelace's Supporter payment is declined.

The agent produces

The lapse is logged. AI writes a note explaining how to update her payment in Patreon, the creator approves it, and it goes from Gmail with the survey link. The weekly Slack summary counts 2 declined, 1 ended and the survey reasons.

What you need

Everything it takes to run it.

About 20 minutes from purchase to live. A checklist above the canvas takes you through each step.

Plan

Included in Enterprise; on other paid plans it's $69 once. Agents run live on paid plans, from Basic ($39/mo).

Your AI key

Connect any of 15 AI providers on your own key. Your provider bills usage directly, at cost; we add no markup.

Apps

Checklist

  • A paid plan (agents run live on paid plans).
  • An AI provider key (Settings → AI Providers).
  • Patreon, Gmail, Google Sheets and Slack, connected in Settings → Integrations.
  • A one-question survey (e.g. a Google Form, choices: Too expensive, Not using it enough, Content isn't for me, Payment problem, Joined for one thing, Other) whose answers go to a sheet.

Setup, about 20 minutes

  1. Connect your AI provider. The AI steps run on your own key (OpenAI, Anthropic, Google and more). Add one in Settings → AI Providers.
  2. Connect Patreon. Connect your Patreon creator account (Settings → Integrations → Patreon) and allow access to members and their emails.
  3. Connect Gmail. Connect the Gmail account the notes should come from (Settings → Integrations → Gmail).
  4. Connect Google Sheets. Connect the Google account that can open your lapses and survey sheets (Settings → Integrations → Google Sheets).
  5. Connect Slack. Connect the Slack workspace for the weekly summary (Settings → Integrations → Slack).
  6. Pick your campaign. Open the trigger and pick your Patreon account and campaign.
  7. Pick the lapses tab. Open “Log the lapse” and pick the account, spreadsheet and tab (Date | Member | Email | Status | Tier | Pledge (cents) | Last charge).
  8. Your note and survey. Open “Write the win-back note” and replace the placeholder, then pick Gmail and paste your survey link in “Email the note from Gmail”.
  9. Your weekly summary. Open “Read the survey answers” and “Read the lapses log” and pick the tabs, then pick the Slack account and channel on “Post the weekly summary”.
  10. Test it with Dry Run. Press Dry Run: the agent runs on sample data with no messages sent and nothing written to your apps.
  11. Switch the trigger on. Open the trigger and press “Activate app trigger”. Lapses are picked up on Patreon's next check (about every 15 minutes).

Is it a fit?

Who it's for, and what it won't do.

Built for

  • Creators on Patreon who want to reduce churn
  • Communities with monthly memberships
  • Creators who want honest feedback from leavers

What it doesn't do

  • Nothing is sent without your approval, and it never offers discounts you didn't describe.
  • It doesn't read survey answers from Patreon: they come from your own survey's sheet.
  • A week without lapses sends no summary; members removed from Patreon entirely can't be detected.
  • It can't change, retry or refund a Patreon payment.

We list the limits up front so you can decide before you buy.

Price

$69 one-time

Per workspace. It never renews.

Available now
  • Included at no extra cost on Enterprise.
  • Buying and running it live need a paid plan, from Basic ($39/mo).
  • Dry Run costs nothing: simulated AI and app calls, nothing sent.
  • AI usage is billed by your own provider, at cost. No AI credits to buy from us.
Get this agent See how it works

One-time agent purchases aren't covered by the 30-day money-back guarantee. Refund policy

FAQ

Questions about Patreon Churn Saver.

Will it pester people?

No. Each lapse gets one note, and you approve every one before it's sent. It never offers discounts you didn't describe.

Where do the reasons come from?

From your own one-question survey, such as a Google Form with fixed choices. Code counts the answers; the agent asks nothing else.

Which apps do I need?

Patreon, Gmail, Google Sheets, Slack and your own AI provider key. The agent's page shows whether each app is ready to connect.

Is it worth it?

It's a one-time purchase that never renews, and rescuing a few failed cards a month adds up. Running it live needs a paid plan; Dry Run is free.

How are the reasons collected?

With your own one-question survey (a Google Form works well) whose answers land in a sheet. Code counts the answers by its choices: Too expensive, Not using it enough, Content isn't for me, Payment problem, Joined for one thing, Other. The agent never asks members anything else.

When does the weekly summary arrive?

With the first lapse at least 7 days after the last summary. A week without lapses sends no summary.

Does every note wait for me?

Yes. Win-back notes are personal and sometimes sensitive, so each one is approved before it's sent.

Is this a subscription?

No. Patreon Churn Saver is a one-time purchase of $69 per workspace and never renews. The Enterprise plan includes it at no extra cost. Running it live needs a paid plan (from Basic ($39/mo)), and your AI provider bills you directly for usage.

Can I test it before it touches real data?

Yes. Once it's set up in your workspace, Dry Run plays every step on sample data with simulated AI and app calls: nothing is sent and nothing in your apps changes. Switch the trigger on only when you're happy.

Put Patreon Churn Saver to work.

Free account, no credit card. Your Agents page opens with Patreon Churn Saver ready to buy and set up, then Dry Run it before it goes live.

Get this agent See how it works