Agent setup guide
Gumroad Sale Welcome & Delivery Check
Every new Gumroad sale gets a personal welcome with tips for that product; buyer emails that look mistyped are flagged to you in Slack instead.
What it does
Every new Gumroad sale gets a personal welcome with tips for that product; buyer emails that look mistyped are flagged to you in Slack instead.
- Starts for each new Gumroad sale (all products, or the one you pick).
- AI writes a short personal welcome: where the files are, the 2–3 tips you gave for that product and your help link.
- Checks the buyer's email: the format in code, and likely typos (gmial.com, .con, placeholders) by AI. A suspect address is flagged in your Slack channel with the likely fix, and no welcome goes to it.
- With review on (the default) each welcome waits for your approval; then it's emailed with replies to your inbox.
What it needs
- A paid plan (agents run live on paid plans).
- An AI provider key (Settings → AI Providers).
- Gumroad and Slack, connected in Settings → Integrations.
- Your getting-started tips for each product.
What it doesn't do
- It can't see whether the buyer downloaded the files (Gumroad's API doesn't say); Gumroad itself delivers the files.
- It doesn't change or resend the Gumroad receipt, and it never emails the address it flagged.
- It never offers discounts, bonuses or refunds you didn't describe.
Availability and plans
Available
Its workflow is built and tested, and every app it needs is live. You can get it and set it up now.
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: Gumroad and Slack.
- The app it watches, connected in Settings → Integrations (the agent starts from an app event).
- About 10 minutes.
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.
2. Connect Gumroad
Connect Gumroad with an access token (Settings → Integrations → Gumroad).
3. Connect Slack
Connect the Slack workspace you use (Settings → Integrations → Slack).
4. Pick your Gumroad account
Open the trigger and pick your Gumroad account (and a product, if you want only one).
| Setting | What to enter | In step |
|---|---|---|
| Gumroad account | The Gumroad account whose sales start the agent. Pick your connected Gumroad account. | “New Gumroad sale” |
5. Describe your products
Open “Write the welcome and check the email” and replace the placeholder with your store, product tips and sign-off.
| Setting | What to enter | In step |
|---|---|---|
| Your store and product tips | Replace the placeholder with your store, 2–3 getting-started tips per product, your help link, tone, sign-off and whether every welcome needs approval (yes by default). It starts as “[DESCRIBE YOUR STORE AND, FOR EACH PRODUCT, 2–3 TIPS FOR GETTING STARTED (WHAT TO OPEN FIRST, A HELP OR COMMUNITY LINK), YOUR TONE, YOUR SUPPORT EMAIL, YOUR SIGN-OFF AND WHETHER EVERY WELCOME NEEDS YOUR APPROVAL. REVIEW EVERY WELCOME: yes]” until you replace it. | “Write the welcome and check the email” |
6. Pick Slack and your inbox
Open “Flag the sale in Slack” and pick the account and channel, then enter your Reply-to on “Email the welcome”.
| Setting | What to enter | In step |
|---|---|---|
| Slack account | The Slack workspace you use. Pick your connected Slack account. | “Flag the sale in Slack” |
| Slack channel for flagged sales | Where sales with a suspect email are posted, e.g. #sales. | “Flag the sale in Slack” |
| Your inbox (replies) | Buyers' replies to the welcome come back to this address. | “Email the welcome” |
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.
8. Switch the trigger on
Open the trigger and press “Activate app trigger”. New sales are picked up every few minutes.
How it works
The agent is a normal workflow with 11 steps (1 AI step, with a person approving in Reviews). You can open, edit and monitor it like any other workflow.
- New Gumroad sale — Starts on “New sale” in Gumroad (an app event). Starts a run for each new successful Gumroad sale (of every product, or pick one on the trigger). Gumroad is checked every few minutes, so runs start a few minutes after the sale.
- Write the welcome and check the email — AI step (runs on your AI provider key). AI checks whether the buyer's email address looks mistyped (gmial.com, .con…) and writes a short personal welcome with the tips you gave for that product.
- Check the buyer's email — Step. In code: exactly one valid email address; combined with the AI's typo check. A suspect address is flagged to you instead of welcomed.
- Check the welcome — Step. In code: a subject and body are there with no leftover placeholders.
- What happens next? — Decision: picks the branch to follow. Suspect email: flagged in Slack, no welcome. Incomplete welcome: held. Otherwise it's sent, after your approval when review is on (the default).
- Flag the sale in Slack — Slack: Post a message. Branch: Email looks wrong. Tells you the buyer's email looks wrong (and the likely fix), so you can reach them another way. No welcome is sent to that address.
- Flagged — Kept in the run history. The run history keeps the sale and the reason.
- Held: welcome incomplete — Kept in the run history. Branch: Incomplete. The welcome was blank or still had a placeholder; nothing was sent. Check your store details.
- 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.
- Email the welcome — Sends an email from your workspace's sender. Branch: No review / Approved. Sends the welcome to the buyer from your workspace's sender, with replies to your inbox.
- Welcome 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
id, email, product_id, product_name, price, currency, formatted_total_price, order_id, license_key, subscription_id, refunded, created_at, sale.
- 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 sales are picked up every few 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.
Questions
Can it tell whether the buyer downloaded the files?
No. Gumroad's API doesn't say whether files were downloaded. The “delivery check” is the email check: a mistyped address means Gumroad's receipt and files went nowhere, so the sale is flagged to you.
Does every welcome need my approval?
By default, yes. Write “REVIEW EVERY WELCOME: no” in your store details to send routine welcomes straight away; refunded sales and products without tips still wait for you.
Can I limit it to one product?
Yes: pick the product on the trigger. Leave it blank for every product.
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.
- Slack says the app isn't in the channel: in Slack, type /invite @Fluxo Flow in that channel (always needed for private channels).
- 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.
Generated from the agent's own workflow, so it always matches what the agent does. Last updated .