The gap this fills: Gumroad doesn't ship an official ntfy app. If you want sale or refund to show up in ntfy the moment it happens, the usual options are a paid third-party bot, custom code, or routing everything through a $20–50/month automation platform just to move one webhook from one URL to another. ZestyGlue does exactly that one thing for $9/month.
What it looks like
A real Gumroad event, shown as ZestyGlue formats it for ntfy.
Setup — about two minutes
- Create the connector. In ZestyGlue, start a new Gumroad → ntfy connector. You'll get a unique webhook URL right away.
- Point Gumroad at it. Go to Settings → Advanced → Ping, and paste in your ZestyGlue webhook URL. That's the only setting — Gumroad's Ping feature has no event picker.
- Point ntfy at ZestyGlue. Pick any topic name — e.g.
https://ntfy.sh/your-secret-topic — enter it into ZestyGlue, and subscribe to that same topic in the ntfy app or web client.
Tip: Gumroad's Ping feature sends one webhook format for every sale and marks refunds with a refunded field — ZestyGlue reads that automatically, so refunds show up clearly labeled instead of looking like new sales.
Events you can forward
sale (ping)
refund
Questions
Does Gumroad support picking specific event types like other platforms?
No — Gumroad's Ping feature sends every sale to one URL with no event picker. ZestyGlue reads the refunded field to label refunds separately.
Will this work for subscription or affiliate products?
Yes, the Ping payload includes the same core fields regardless of product type, so subscriptions and affiliate sales flow through normally.
Do I need to self-host ntfy?
No, the free public ntfy.sh server works fine for most people — just pick an unguessable topic name.
What happens if my ZestyGlue subscription lapses?
Events are silently dropped rather than causing errors on Gumroad's side — Gumroad never sees a failure response, so it won't retry aggressively or flag your webhook as broken. Your dashboard will simply stop showing new events until you resubscribe.