Webhook Integration
CheckedHelps with webhooks, integration as part of agent workflows workflows.
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 dodopayments/skills --skill webhook-integration -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
dodopayments
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 passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.
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 undeclared network calls: passed
Makes no network calls.
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.
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 dodopayments/skills at db432aa923.
The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.
- Commit
- db432aa923
- Scanned
- 4 files, 744 lines
About this skill
What it does
This skill enables AI agents to integrate with Dodo Payments webhooks, allowing for real-time notifications about payment events. It facilitates automating workflows, updating databases, and synchronizing systems based on these events. The agent can receive and process webhook data related to payments, subscriptions, refunds, disputes, license keys, credits, and more.
When to use it
- Automate order fulfillment upon successful payment (e.g.,
payment.succeeded). - Send notifications when a payment fails so that users are informed immediately (e.g.,
payment.failed). - Update internal records when a subscription status changes (e.g.,
subscription.active,subscription.cancelled). - Trigger actions based on credit balance events, such as sending alerts for low balances (
credit.balance_low). - Respond to new disputes automatically (e.g.,
dispute.opened).
Key capabilities
- Receives webhook notifications from Dodo Payments.
- Supports a wide range of event types including: payment events, subscription events, refund events, dispute events, license key events, and credit events.
- Requires configuration of an endpoint URL and a webhook secret in the Dodo Payments dashboard.
- Uses environment variable
DODO_PAYMENTS_WEBHOOK_SECRETto authenticate incoming webhooks. - Understands request headers including
webhook-id,webhook-signature, andwebhook-timestamp.
Example prompts
- "Listen for payment succeeded events from Dodo Payments and log the customer's email address."
- "When a subscription is cancelled, send an internal notification to the support team."
- "Monitor credit balance low events and trigger a reminder email to the customer."
Tips & gotchas
- You must configure a webhook in your Dodo Payments dashboard and provide its secret as the
DODO_PAYMENTS_WEBHOOK_SECRETenvironment variable. - Ensure your endpoint URL is publicly accessible for Dodo Payments to send webhooks.
- The skill receives data in JSON format, requiring appropriate parsing within your agent's workflow.