Integrations · Paddle

Paddle transaction and subscription notifications on your phone

A push when a transaction completes, a subscription changes or a payout is made, per notification destination.

Paddle's own page was read on 12 September 2026 for every step below. If a menu has moved since, write to hello@youlmk.com and it is corrected the same day.

What Paddle sends

The events you choose, as JSON with event_id, event_type, occurred_at, notification_id and the object under data, signed with Paddle-Signature.

What arrives in the inbox

Title
The event's type in words ("Transaction completed")
Priority
normal; set the source's Reach for how loud a failed payment should be
Group
the event type

Set it up

In YouLMK, create a source of type webhook named after the service, and copy its webhook URL: youlmk.com/w/k_7hq2nk3f9qd8w4 with your own key. Then:

  1. In Paddle, open Developer tools, then Notifications, then New destination.
  2. Give it a description, choose the notification type webhook, paste your source's webhook URL from YouLMK, and select the events.
  3. Save. The secret key and the Paddle-Signature header are Paddle's; YouLMK reads the event, not the signature, for Paddle.

Make it quiet where it should be

Everything above lands with the source's own rules: its Reach (Silent, Badge, Banner, Break through), whether quiet hours hold it, and grouping of repeats into one card. Set them once on the source, in the app or at app.youlmk.com; the service never has to change. Unknown fields arrive as rows on the card, up to six; the whole request is capped at 8 KB (Webhooks).

Try it

The trial is 10 notifications and 3 watches, no card. Get your key, or read the webhooks reference first.

Source

developer.paddle.com/webhooks/overview, read 12 September 2026.