Dunning
When
A payment fails
Then
- Recovery email asking the customer to update their card
- Slack follow-up in #revenue if still unpaid after 3 days
No workflow to design from scratch. Start from a playbook that already covers the common case.
Paste a restricted, read-only Stripe key and add the Likiro webhook. Then connect the channels you want: Resend, Slack, Discord, Telegram or Vercel.
Install a ready-made playbook in one click, then adjust the email copy, delays and channels to fit your product.
When the Stripe event arrives, Likiro runs the actions and logs the run with the result of each action.
Each playbook is a trigger plus actions. Install it, customize it, and it runs on every matching event.
When
A payment fails
Then
When
A trial is about to end
Then
When
A subscription is canceled
Then
When
A customer upgrades their plan
Then
When
A customer pays their first invoice
Then
When
A Vercel deploy fails
Then
Coming soon: Google Analytics anomaly triggers, user-inactivity triggers from your database and a visual builder.
Each action goes to the right place: your customer's inbox, your team's chat or your own systems.
Sent through your own Resend account, from your domain. Templates with variables like customer name and plan.
Post to the channel that fits: #revenue, #sales, #incidents.
The same alerts for teams that live on Discord.
Optional: alerts and a daily digest in a Telegram chat.
Send the event to your CRM or any HTTP endpoint.
Write templates with variables, or let AI draft the email for each event. You review and approve before it goes out — or turn on auto-send once you trust it.
For email actions, AI can write a draft using the event and customer context. Nothing is sent to your customer until you approve it, unless you choose auto-send.
Hi {{customer.name}},
We noticed you canceled your {{subscription.plan}} plan subscription.
We'd like to offer you a 30% discount on your next month if you decide to come back.
Ask the customer to update their card, with a direct link.
Remind trial users before the trial ends.
Reach out after a cancellation with your offer.
Thank customers who move to a bigger plan.
Welcome new paying customers after their first invoice.
Ask the customer to update their card, with a direct link.
Remind trial users before the trial ends.
Reach out after a cancellation with your offer.
Thank customers who move to a bigger plan.
Welcome new paying customers after their first invoice.
Ask the customer to update their card, with a direct link.
Remind trial users before the trial ends.
Reach out after a cancellation with your offer.
Thank customers who move to a bigger plan.
Welcome new paying customers after their first invoice.
Ask the customer to update their card, with a direct link.
Remind trial users before the trial ends.
Reach out after a cancellation with your offer.
Thank customers who move to a bigger plan.
Welcome new paying customers after their first invoice.
Likiro already reads your Stripe data, so you also get revenue metrics — and a check on whether a Vercel deploy moved them.
📊 Deploy Analysis — Tuesday 14:23
Branch: main · fix/checkout-flow · 3-day window
Consider rollback or hotfix
MRR, ARR, churn and subscriber movements computed from Stripe, in the dashboard.
A short daily summary of your revenue numbers.
Compares MRR, new subscriptions and churn in the days before and after each Vercel deploy.
Connect Stripe with a read-only key, install a playbook and let Likiro handle the follow-up.