Paddle Webhooks
ListedPaddle Webhooks allows you to trigger actions in your systems based on Paddle events (like payments), streamlining workflows and automating business processes.
Install on your platform
Showing Claude Code. One command installs this skill into any of the agents below.
- 1
Run this in your project
terminal$ npx skills add hookdeck/webhook-skills --skill paddle-webhooks -a claude-code Uses the open-source
skillsCLI and needs Node.js. Add-gto install it for your user instead of this project.
What we know about this skill
Publisher
hookdeck
Taken from the source listing. We haven't verified who controls this account.
Install target
Live repository
Not pinned. Installing fetches whatever the repository holds at the time you run the command.
Automated safety checks
This skill failed 1 of 6 checks. A failure is not proof of bad intent; it means something in the code needs a human to look at it before you run it.
No undeclared network calls: failed
Contacts 1 host that is neither well-known infrastructure nor declared in the skill's frontmatter: api.paddle.com.
Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.
Hosts contacted
api.paddle.comundeclaredWhat it found
- skills/paddle-webhooks/references/setup.md:28contacts api.paddle.com
curl -X POST https://api.paddle.com/notification-settings \ - skills/paddle-webhooks/references/setup.md:57contacts api.paddle.com
curl https://api.paddle.com/notification-settings/{notification_setting_id} \
Declares what it does: passed
SKILL.md parses and declares a name and a description.
SKILL.md exists, its frontmatter parses, and it declares a name and a description.
No obfuscated payloads: passed
No encoded or obfuscated payloads.
No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.
No credential access: passed
Reads no keys, tokens, keychains or credential files.
Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.
No pipe-to-shell installers: passed
No pipe-to-shell or download-and-run installers.
No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.
Pinned to a commit: passed
Scanned hookdeck/webhook-skills at e9d1b145a4.
The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.
- Commit
- e9d1b145a4
- Manifest
- skills/paddle-webhooks/SKILL.md
- Scanned
- 18 files, 1,679 lines
About this skill
What it does
This skill enables AI agents to receive real-time event notifications directly from Paddle, allowing them to react instantly to subscription changes, payments, and customer lifecycle events without polling. It bridges the gap between Paddle's ecosystem and automated agent workflows by delivering structured webhook payloads.
When to use it
- Triggering automated onboarding sequences immediately after a new customer subscribes to a SaaS product.
- Sending instant support tickets or notifications when a payment fails or a subscription is downgraded.
- Updating internal CRM records automatically whenever a Paddle order status changes from pending to completed.
- Executing inventory adjustments or license key generation upon successful purchase confirmation.
Key capabilities
- Listens for specific Paddle events such as
OrderPaid,SubscriptionCreated, andCustomerCancelled. - Delivers event data in a standardized JSON format accessible to AI agent logic.
- Supports secure transmission of sensitive transaction details including customer IDs and order references.
Example prompts
- "Set up a workflow that sends a welcome email and generates a license key whenever I receive a
SubscriptionCreatedwebhook from Paddle." - "Alert the support team via Slack if the incoming Paddle webhook indicates an
OrderFailedevent for any customer." - "Update the user's status in our database to 'Active' only after verifying the payload contains a successful
PaymentReceivedsignal."
Tips & gotchas
Ensure your AI agent has proper authentication credentials configured to verify the signature of incoming Paddle webhooks, preventing unauthorized data injection. Be mindful that webhook delivery is asynchronous; your agent logic must handle potential retries or timeouts if the endpoint is temporarily unreachable.