Sale
Welcome sequences, onboarding, upsell offers
Post-purchase email automation
Missio connects to BuyGoods, ClickBank, and Digistore24 webhooks so you can build visual email flows that trigger on every sale, refund, and rebill.
Built for marketplace operators



0
Marketplaces supported
BuyGoods, ClickBank, Digistore24
0%
Post-purchase event-driven
Sale, refund, rebill, chargeback, upsell
0
Cron jobs for enrollments
Stateful execution per buyer
Missio sits at the center of your marketplace stack — ingesting webhooks, normalizing events, and routing each buyer into the right automated flow.
LiveBuyGoods, ClickBank, and Digistore24 are live today. Additional marketplaces shown for roadmap context.
Plug in your marketplace webhook URL and every event arrives as a standardized payload — ready to trigger flows.
Endpoint URL
https://api.missio.app/hooks/buygoods/abc123
Normalized event
Map triggers, emails, waits, and conditions on a visual canvas — no code required.
ExploreEvery email leaves from your authenticated sending domain. Your reputation, your deliverability.
Welcome — your order is confirmed
buyer@example.com
Getting started with your purchase
buyer@example.com
Renewal reminder
buyer@example.com
We received your refund request
buyer@example.com
Three steps to automate your buyer emails. No pre-checkout capture — contacts arrive when buyers complete a purchase.
Create a webhook endpoint in Missio and paste the URL into your marketplace. Buyer data flows in after every sale.
Drag nodes onto the canvas — trigger, send email, wait, condition, tag, goal. Save drafts and publish when validated.
Each buyer enrollment runs in its own durable execution. Waits, branches, and sends happen without cron jobs.
Generic ESPs weren't built for marketplace webhooks. Missio normalizes every event from your marketplace into triggers your flows can act on.
ExploreWelcome sequences, onboarding, upsell offers
Cross-sell follow-ups after additional purchases
Subscription renewal confirmations and reminders
Payment retry nudges before cancellation
Exit sequences and win-back campaigns
Immediate suppression and account updates
Example journey
Generic email platforms excel at newsletters and e-commerce carts. Missio is purpose-built for the post-purchase lifecycle of infoproduct marketplaces.
| Capability | Generic ESP | Missio |
|---|---|---|
| Native marketplace webhooks | ||
| Post-purchase event triggers | ||
| Send from your authenticated domain | Limited | |
| Stateful per-buyer enrollment | ||
| Visual flow editor | ||
| Pre-checkout email capture |
Native marketplace webhooks
Generic ESP
Missio
Post-purchase event triggers
Generic ESP
Missio
Send from your authenticated domain
Generic ESP
LimitedMissio
Stateful per-buyer enrollment
Generic ESP
Missio
Visual flow editor
Generic ESP
Missio
Pre-checkout email capture
Generic ESP
Missio
Pricing
No credit card required on Free. Scale through Starter and Pro, or talk to us for Enterprise.
Starter
Billed monthly
Pro
Billed monthly
Enterprise
Tailored volume, SLA, and onboarding
FAQ
Everything you need to know before connecting your first marketplace webhook.
No. Missio is built for post-purchase automation. Buyer contacts arrive via marketplace webhooks after a sale completes — there is no pre-checkout capture flow.
BuyGoods, ClickBank, and Digistore24. Each marketplace webhook is verified with HMAC signatures and normalized into a standard event format.
Yes. On the Pro plan you authenticate your own sending domain via AWS SES. Emails always send from your domain, not a shared platform address — protecting your sender reputation.
Refund and chargeback events trigger their own flows. You can run exit sequences, suppress future emails, or branch based on the event type — all handled by the same event-driven engine.
Each buyer enrollment runs in its own stateful execution. Wait nodes schedule alarms internally — no central cron job scans a queue. Timers survive restarts and scale independently.
Yes. The Free plan includes 1 marketplace webhook, 1 active flow, and 500 emails per month. No credit card required to get started.
Yes. Flows can be saved as drafts while you build. When you publish, server-side validation runs to catch errors before any emails go out.
Every database query carries your tenant ID. Row-level security is enforced in Postgres, and each webhook endpoint is scoped to your account.
Sign in to connect your marketplace and publish your first flow.