Paddle events, straight into Slack
Every transaction, renewal, or failed payment — posted to Slack the moment it happens. No $20+/month automation plan just to move one webhook.
Why not just use Slack's built-in options? Even where Paddle offers some form of Slack integration, it's often tied to one account, limited in which events it covers, or more than you need. ZestyGlue is a dedicated, always-on feed of exactly the events you choose, for $9/month instead of a full automation-platform subscription.
What it looks like
ZestyGlue
Paddle — Transaction · Completed
29.00 USD
A real Paddle event, shown as ZestyGlue formats it for Slack.
Setup — about two minutes
- Create the connector. In ZestyGlue, start a new Paddle → Slack connector. You'll get a unique webhook URL right away.
- Point Paddle at it. Go to Developer Tools → Notifications → add destination, paste in your ZestyGlue webhook URL, and select the events you want.
- Copy the secret key. Paddle shows a secret key for your notification destination — paste that into ZestyGlue's connector setup so every event can be verified as genuinely from Paddle.
- Point Slack at ZestyGlue. Create a Slack app (or reuse one) → Incoming Webhooks → Add New Webhook to Workspace, pick the channel, and copy the URL into ZestyGlue.
Under the hood: Paddle signs its payload with a timestamped HMAC in the paddle-signature header — ZestyGlue verifies both the signature and, implicitly, that the request wasn't replayed from days ago.
Events you can forward
transaction.completed
transaction.payment_failed
subscription.created
subscription.canceled
subscription.updated
Questions
Is my Paddle Webhook Secret Key safe with ZestyGlue?
It's encrypted at rest with Fernet symmetric encryption before it ever touches disk, it's never logged, and it's never displayed again in the dashboard after you enter it — only a masked placeholder is shown.
Does this work with Paddle Classic or only Paddle Billing?
This connector is built for Paddle's current Billing API (v2) webhook format. Paddle Classic uses a different payload shape and isn't supported.
Can I track failed renewals separately?
Yes — subscribe to transaction.payment_failed as its own event alongside transaction.completed.
Does this need Slack admin approval?
No app installation is required on Slack's side — an Incoming Webhook is just a URL generated once. No OAuth review, no admin approval flow.
What happens if my ZestyGlue subscription lapses?
Events are silently dropped rather than causing errors on Paddle's side — Paddle 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.