Patreon New-Member Welcome

What it does

Each new Patreon member gets a personal welcome for their tier with a checklist of its perks, by Gmail and/or a Discord channel welcome.

• Starts when someone joins your Patreon campaign (paid or free) and reads their tier from Patreon.
• AI writes a personal welcome for that tier with a checklist of its perks and how to claim each one, from the perks you listed.
• Code checks the member's email and leftover placeholders; review is off by default, and you can switch it on to approve each welcome.
• Emails the welcome from your Gmail and/or posts a short first-name-only welcome in your Discord channel (Gmail, Discord or both), and reports only what really went out.

What it needs

• A paid plan (agents run live on paid plans).
• An AI provider key (Settings → AI Providers).
• Patreon, plus Gmail, Discord or both, connected in Settings → Integrations.
• Each tier's perks and how members claim them.

What it doesn't do

• It can't assign Discord roles or post on Patreon (the APIs don't allow it).
• It never mentions pledge amounts and never invents perks.
• Members Patreon gives no email for are held (an email is checked before anything is sent).

Availability and plans

Included free on the Enterprise plan; on other paid plans it's a one-time purchase per workspace (the price is on the Agents page). The Agents page in the app always shows its current status.

Before you start

• A paid plan: agents run live, and the Free plan only runs Dry Runs.
• An AI provider key (OpenAI, Anthropic, Google and more) in Settings → AI Providers. AI usage is billed by your provider.
• These apps, connected in Settings → Integrations: Patreon, Gmail and Discord.
• The app it watches, connected in Settings → Integrations (the agent starts from an app event).
• About 10 minutes.

• Bring your own AI key
• Patreon (live)
• Gmail (live)
• Discord (live)

Set it up step by step

Get the agent first (buy it, or it's already yours when your plan includes it), then in Agents → My agents press “Set up this agent”. That creates the agent's workflow in your workspace (it counts towards your plan's workflow limit) and opens the canvas with a setup checklist above it. Each item links to the exact place to go and ticks itself off when it's done.

1. Connect your AI provider

The AI steps run on your own key (OpenAI, Anthropic, Google and more). Add one in Settings → AI Providers.

• Connect your AI provider

2. Connect Patreon

Connect your Patreon creator account (Settings → Integrations → Patreon) and allow access to members and their emails.

• Connecting Patreon

3. Connect Gmail, Discord or both

Connect Gmail to email the welcome, and/or your Discord bot to welcome members in a channel (Settings → Integrations). One is enough; the step for an app you don't connect is skipped.

• Connecting Gmail
• Connecting Discord

4. Pick your campaign

Open the trigger and “Look up their tier” and pick your Patreon account and campaign.

5. List your perks

Open “Write the welcome and perks checklist” and replace the placeholder with your tiers, perks and review switch.

6. Gmail and/or Discord

Open “Email the welcome from Gmail” and “Welcome them in Discord” and pick what you use (one is enough).

7. Test it with Dry Run

Press Dry Run: the agent runs on sample data with no messages sent and nothing written to your apps.

• Dry Run vs Run

8. Switch the trigger on

Open the trigger and press “Activate app trigger”. New members are picked up on Patreon's next check (about every 15 minutes).

How it works

The agent is a normal workflow with 18 steps (1 AI step, with a person approving in Reviews). You can open, edit and monitor it like any other workflow.

• New Patreon member — Starts on “New member” in Patreon (an app event). Starts a run when someone joins your campaign, paid or free (Patreon is checked every 15 minutes or so).
• Look up their tier — Patreon: Get a member. Reads the member from Patreon: name, email, tier and pledge.
• Write the welcome and perks checklist — AI step (runs on your AI provider key). AI writes a personal welcome for their tier with a checklist of the perks you listed for it and how to claim each one, plus a short Discord welcome.
• Check the welcome — Step. In code: one valid email from Patreon, a subject and a body and Discord message with no leftover placeholders.
• Review first? — Decision: picks the branch to follow. Incomplete: held. With review off (the default) the welcome goes out at once; switch review on to approve each one.
• Held: not sent — Kept in the run history. Branch: Incomplete. No email from Patreon, or the welcome was blank or had a placeholder.
• Approve the welcome — A person approves or rejects it in Reviews (the run waits). Branch: Review first. The welcome waits in Reviews: edit it and approve to send it. Reject to send nothing.
• Ready to send — Step. Branch: No review / Approved. In code, after any edits: the welcome still has no placeholders.
• Still ready? — Decision: picks the branch to follow. An edit that left a placeholder holds the welcome.
• Held after review — Kept in the run history. Branch: Held. An edit left a placeholder.
• Email the welcome from Gmail — Gmail: Send an email. Branch: Send. Sends the welcome to the member's email from your Gmail. Skipped when Gmail isn't connected.
• Welcome them in Discord — Discord: Send a message. Posts the short welcome (first name only) in your Discord channel. Skipped when Discord isn't connected.
• Emailed? — Step. In code: did Gmail return a sent message? (No when Gmail isn't connected.)
• What went out? — Decision: picks the branch to follow. In code: names only what really went out (a step whose app isn't connected was skipped).
• Emailed and welcomed in Discord — Kept in the run history. The run history keeps the welcome.
• Emailed — Kept in the run history. The run history keeps the welcome.
• Welcomed in Discord — Kept in the run history. The run history keeps the welcome.
• Nothing sent — Kept in the run history. The run history keeps the welcome.

Test it with Dry Run

Press Dry Run in the canvas. The agent runs on the sample data stored on its trigger (the “Sample data for Dry Run” box), so you can check every step's output before anything is live. The sample has the same shape as a real event from the app.

Sample data fields

member_id, full_name, email, patron_status, pledge_relationship_start, currently_entitled_amount_cents, will_pay_amount_cents, campaign_lifetime_support_cents, last_charge_status, last_charge_date, next_charge_date, user_id, tier_ids (a list), tier_title, tier_titles (a list), member.

• Nothing is sent or written: app actions, emails and Slack posts are simulated, and AI steps don't call your AI provider.
• Approval steps use the Dry Run decision you pick in the step's settings (approved, rejected or timeout), so you can try each branch.

Go live

• Open the trigger and press “Activate app trigger”. New members are picked up on Patreon's next check (about every 15 minutes).
• Activating the app trigger needs the trigger's connected account. The first check only remembers what's already there, so older items don't start runs; the same item never starts two runs.
• The setup checklist adds a “paid plan” item before activation: live runs need a paid plan (the Free plan only runs Dry Runs).
• When every checklist item is done and the trigger is on, the checklist says “Live — this agent is running”. Follow its runs in the workflow's History tab and in Analytics → Agents.

• App event triggers
• Switching a trigger on (Activation)

Questions

Can it give members their Discord role?

No. Our Discord connection posts messages; it can't assign roles. Patreon's own Discord integration does that, and the checklist tells members how to link it.

Does every welcome wait for me?

Not by default: new members expect a quick hello. Write “REVIEW BEFORE SENDING: yes” in your creator details to approve each one; members of a tier you didn't describe always wait.

What does the Discord welcome show?

Their first name and tier only, never their email or pledge.

Troubleshooting

• “No AI provider connected” or a rejected key: connect or fix the key in Settings → AI Providers, then press Test there.
• A checklist item stays unticked: the setting is still empty or still contains its placeholder text. Open the step from the checklist and fill it in.
• An app step fails with “Needs reconnect”: the account's access was revoked or expired. Reconnect it in Settings → Integrations.
• No runs start: activate the app trigger with a connected account. Only items created after activation start runs.
• A run shows as paused: it's waiting for someone in Reviews to approve or reject it.
• A step failed: open the run in History and check that step in the Trace tab for the error and what it received.

• Debugging failed runs
• Error messages
• Get help