Stripe revenue alerts in 2 minutes
Get a cha-ching in Slack the next time someone pays you — connect Stripe to EventSend with no code.
The goal: the next time someone pays you, your team channel says so. No code, no deploy — about two minutes of clicking.
You'll need a Stripe account and permission to install an app into your Slack workspace.
1. Connect Slack
In EventSend, open Connections and connect Slack. You'll be sent to Slack to approve the install and pick the channel EventSend may post to.
Then open Destinations, create a destination of type Slack, and point it at that connection. Give it a name you'll recognize later, like "Revenue channel".
2. Create the Stripe source
Open Sources, create a source, and choose Stripe. Leave the default event selection alone — it already covers payments, failures, subscriptions, and disputes.
Copy the endpoint URL the form shows you.
3. Point Stripe at it
In your Stripe Dashboard, go to Developers → Webhooks → Add destination, paste the endpoint URL,
and select the events you enabled. After the endpoint is created, reveal its signing secret
(whsec_...) and paste it back into the signing secret field in EventSend.
Full detail, including the event mapping table, is on the Stripe source page.
4. Route payments to Slack
Open Topics and create one:
- Connect it to the route your Stripe source feeds.
- Connect it to the Slack destination from step 1.
- Set the event pattern to
payment-*.
That pattern catches payment-received and payment-failed — the money coming in, and the money
that didn't. Leave the minimum level at its default so both get through.
If you'd rather split them, make two topics: one with pattern payment-received to your revenue
channel, and one with minimum level error to wherever you handle billing problems.
5. Test it
With the Stripe CLI:
stripe trigger checkout.session.completed
Within a second or two you should see 💰 New payment: 20.00 USD in Slack, and the event in EventSend's Events list with a delivery attempt against your Slack destination.
If nothing arrives, the event page tells you why. The two usual causes are a signing secret that
wasn't saved (the source's failure counter will be climbing) and a topic that isn't connected to both
the route and the destination — an event with nowhere to go is recorded as dropped.
Where to take it next
- Add a Telegram destination to the same topic to get payments on your phone.
- Send your own
trial-startedandupgradeevents from your app with the Events API so the whole funnel lands in one channel. - Route disputes (level
critical) somewhere noisier than payments.