Use case
Recurring webhook triggers for billing and entitlements.
Lemon Squeezy handles checkout and merchant-of-record duties. Your daily entitlement refresh, your custom dunning, your weekly partner-payout job all live in your backend. Crontap is the external clock that fires those endpoints on a real cron.
Free plan · no credit card required
The problem
Why this is painful without the right tool
- Lemon Squeezy's webhook surface is event-driven; daily reconciliation runs need a clock you bring yourself.
- Custom dunning across LS and your CRM needs a single cadence that does not exist in either tool natively.
- Partner-payout cadences are calendar-bound (1st, 15th, end of month) and need precise local-time firing.
The fix
How Crontap solves it
Crontap calls your /billing/lemonsqueezy/recon or /billing/lemonsqueezy/payout endpoint on the cadence you choose. Your backend uses the LS API; LS stays the processor. Failures alert to email / webhook (Slack / Discord / Telegram).
0 1 1,15 * *FAQ
Common questions
- Does this replace LS's automatic recurring billing?
- No. Lemon Squeezy still bills the customer on the schedule attached to the subscription. Crontap fires your own custom logic (entitlement refresh, partner payouts, custom dunning) that LS does not natively handle.
- What's the shortest interval Crontap supports?
- Every 1 minute on paid plans. Free tier available for slower cadences.
Adjacent use cases
Ready to fix it?
Point Crontap at any URL. Pick any cron. Done.
WordPress, Shopify, Railway, Cloud Run, Vercel, HubSpot, Ghost, your own box. If it answers HTTP, Crontap can drive it on a clock you can read, in the timezone that actually matters, and page you when something breaks.
Free forever tier ・ No credit card required
/wp-cron.php?doing_wp_cron=1
Schedule
"every 5 minutes"
Next
in 23s