--- title: "Patreon Integration" description: "Connect AI agents to your Patreon creator account. Agents pull campaigns, patron pledge and charge details, and published posts to power supporter rosters, thank-you workflows, and revenue dashboards." url: https://flowrunner.ai/integrations/patreon date_modified: 2026-08-04T10:04:16-07:00 --- # Patreon [Social Media](https://flowrunner.ai/integrations/category/marketing-social) Connect AI agents to your Patreon creator account. Agents pull campaigns, patron pledge and charge details, and published posts to power supporter rosters, thank-you workflows, and revenue dashboards. [Verified](https://flowrunner.ai/integrations/verified "What does verified mean?") · 6 actions · API key · available [Patreon website](https://patreon.com/) · [Platform Documentation](https://docs.patreon.com/) · Capability data verified 2026-07-28 1. A daily schedule fires for the membership health check 2. List Campaigns confirms the campaign and pulls current patron count and currency 3. List Members filtered to Active Patron pages through the roster with pledge amounts and entitled tiers 4. The agent diffs against yesterday's roster: new patrons, upgrades, and members whose status flipped to Declined Patron 5. Get Member pulls lifetime support and last charge date for everyone flagged 6. The creator reviews the declined list and the drafted outreach, deciding who gets a payment nudge and who gets left alone 7. New patrons and milestone counts post to the team channel, and the roster syncs to the reporting sheet ## What This Integration Enables A Patreon campaign is a membership business, and membership businesses live or die on knowing who supports you, who just left, and whose payment silently failed. Patreon's dashboard shows all of this to whoever logs in; this connector makes it available to flows that act on it. FlowRunner agents pull campaigns, patron rosters with pledge and charge detail, and published posts through Patreon's API v2, with the JSON:API field sets and includes handled for you so member records arrive usable, not nearly empty. - Sync patron rosters with pledge amounts, tiers, and last charge dates into sheets and CRM - Catch status changes daily: new patrons, upgrades, declines, departures - Power revenue dashboards with patron counts and lifetime support in cents - Draft tier-aware thank-yous and win-back outreach for creator approval - Feed published post metadata into announcement and archival flows For a working creator, the argument for orchestration is arithmetic: the hours spent exporting rosters, chasing declines, and writing thank-yous are hours not spent making the thing patrons pay for. But the naive fix, full automation, destroys the intimacy that makes membership work, because patrons can tell when the creator stopped being in the loop. FlowRunner's structure preserves both sides. Agents carry the operational weight on a schedule, and the [human-in-the-loop](https://flowrunner.ai/concepts/human-in-the-loop) gate keeps the creator's actual judgment on everything a patron will read. The business scales; the voice does not dilute. That trade is the entire case for orchestration in a membership business: more patrons handled with more care per patron, not less, and the creator's hours flowing back into the work that earns the pledges. ### Without FlowRunner **The patron list lives in Patreon's dashboard**: Supporter data reaches the CRM and the accountant as occasional CSV exports **Declined payments slip by**: Failed charges surface weeks later as quietly missing revenue **Thank-yous scale badly**: New patrons get the generic auto-message or a personal note, whichever the week allows ### With FlowRunner **The roster syncs itself**: Active patrons, pledges, and tiers land in sheets and CRM on a daily schedule **Declines surface within a day**: Status flips get caught in the diff, with lifetime support attached for context **Every patron gets a real acknowledgment**: Agents draft tier-aware thank-yous and the creator approves them in one pass ## Use Case Scenarios ### The supporter roster that is always current Each morning, List Members pages through active patrons and writes full name, email, entitled tier, pledge amount, and last charge date to [Google Sheets](https://flowrunner.ai/integrations/google-sheets). The diff against yesterday flags new arrivals and departures. New patrons trigger a drafted thank-you in [Gmail](https://flowrunner.ai/integrations/gmail-service) that references their actual tier; the creator approves the batch with coffee. The spreadsheet the accountant asks for at tax time has been building itself all year. ### Declined charges caught while they are recoverable A patron's card expires and their status flips to Declined Patron. The daily diff catches it, and Get Member adds the context that changes the tone: this is a supporter with three years and $800 of lifetime support, not a drive-by pledge. The agent drafts a warm, no-pressure note about the payment hiccup and queues it for the creator's review. Declines stop being silent churn and become conversations, handled while the patron still remembers subscribing. ### One report across every membership platform Creators rarely run one platform. The reconciliation flow pulls List Members here, [Memberful](https://flowrunner.ai/integrations/memberful) members, and [Gumroad](https://flowrunner.ai/integrations/gumroad) subscribers, and merges them on email into a single supporter picture: who pays where, who pays twice, and what total support actually looks like. Monthly revenue posts to [Slack](https://flowrunner.ai/integrations/slack) with per-platform breakdowns. The question "how is membership actually doing?" gets an answer that spans the whole business, not one dashboard at a time. ## Human-in-Loop Highlight List Members hands an agent the most sensitive asset a creator has: every patron's name, email, pledge amount, and payment status, the exact data that makes personalized outreach possible and makes a mistake with it expensive. The costly operation in these flows is the message built on that data, and nowhere more than the declined-payment note. Sent well, it recovers a supporter; sent clumsily, automated-sounding, mis-tiered, or aimed at someone grieving a canceled card, it reads as a paywall chasing a fan, in the creator's own voice. So the agent assembles and the creator sends: each drafted note arrives for review with the member's Get Member context, tier, lifetime support in cents, last charge date, so the human can judge tone against relationship. The roster syncs, the diffs run, and the dashboards update without anyone watching. The words that land in a supporter's inbox under the creator's name wait for the creator. Agent processes routinely Detects exception requiring judgment Clear match Continues automatically Ambiguous Routes to human via email Human decides Agent resumes with decision ## Agent Capabilities 6 actions ### Account 1 - **Get Identity** Returns the profile of the user who owns the creator access token, with full name, email, and optionally memberships and campaigns. The first call in any flow, confirming which account the automation acts for. ### Campaigns 2 - **List Campaigns** Lists the authenticated creator's campaigns, with tiers when requested. Most creators have one; its id feeds every member and post operation. Attributes arrive under the JSON:API envelope's data and included sections. - **Get Campaign** Retrieves a single campaign with creation name, patron count, currency, pledge URL, and tiers when requested. The source for dashboard metrics and milestone alerts. ### Members 2 - **List Members** Lists a campaign's patrons and followers with full name, email, patron status, pledge amount in cents, and currently entitled tiers, cursor-paginated and filterable by patron status. The roster read behind sync, diffing, and outreach flows. - **Get Member** Retrieves one member with linked user, campaign, entitled tiers, lifetime support in cents, and last charge date. The context pull that turns a status flip into a judgment-ready brief. ### Posts 1 - **List Posts** Lists a campaign's published posts with title, content, publish date, URL, and paid-or-public status, cursor-paginated. The feed behind announcement mirrors and content archives. ## Frequently Asked Questions ### What can FlowRunner do with Patreon? FlowRunner agents can run Get Identity, List Campaigns, and Get Campaign in Patreon, plus 3 more actions. ### Does connecting Patreon to FlowRunner require OAuth? No. Patreon connects to FlowRunner with an API key, no OAuth flow required. ### Can Patreon trigger a FlowRunner workflow automatically? Patreon doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger. **Work at Patreon?** This integration exposes Patreon to AI agents on every FlowRunner plan, including through MCP, at no cost to you. [See what FlowRunner offers integration partners](https://flowrunner.ai/integrations/partners), including how to keep this page current. --- Markdown version of https://flowrunner.ai/integrations/patreon. Site index: https://flowrunner.ai/llms.txt