What RevenueCat's Slack integration does
RevenueCat's Slack integration posts purchase events from your RevenueCat project to a Slack channel through an Incoming Webhook. It sends nine event types: Initial Purchase, Trial Started, Trial Converted, Trial Cancelled, Renewal, Cancellation, Non Subscription Purchase, Billing Issue, and Product Change. Each message carries the RevenueCat customer ID with a link to the customer's profile, the product identifier, the revenue amount where applicable, a timestamp, and an emoji and colour per event type.
It is a good fit if RevenueCat already sits in your app and you want its view of purchases in Slack. The limits are the ones RevenueCat documents: it requires a RevenueCat project and its SDK in the app, it does not send negative revenue, customer attributes, or transfer events, sandbox events have to be switched on separately, and there is no documented way to route different events to different channels.
It also stops at purchases. Nothing about App Review, build processing, TestFlight crashes, or tester feedback reaches Slack, because RevenueCat never sees those events.
Based on RevenueCat's public Slack integration documentation as reviewed on September 8, 2026. Features may have changed since then.
What Yeethook does instead
Yeethook takes subscription events straight from Apple. App Store Server Notifications V2 are sent by the App Store for every subscription and purchase event, signed by Apple, to a server URL you set in App Store Connect. Yeethook is that server. It verifies the signature, decodes the transaction, and posts a formatted message to Slack:
- Every notification type, not nine. SUBSCRIBED, DID_RENEW, DID_CHANGE_RENEWAL_STATUS, DID_FAIL_TO_RENEW, EXPIRED, GRACE_PERIOD_EXPIRED, REFUND, REFUND_DECLINED, REFUND_REVERSED, OFFER_REDEEMED, PRICE_INCREASE, REVOKE, CONSUMPTION_REQUEST, and the rest, each with its subtype.
- Transaction details from Apple's signed payload: product, price and currency, expiry date, auto-renew status, renewal product, transaction ID, and environment.
- No SDK. Nothing changes in your app. If you already have a p8 key connected, Yeethook registers the notification URL with Apple for you.
- The Apple events RevenueCat never sees. Review status, build processing, TestFlight crash reports and screenshot feedback, from the same account, in the same Slack workspace.
- Routing. Subscriptions to
#revenue, churn signals to#churn, refunds to#refunds, per app and per event type.
What Yeethook does not replace
Be clear about the boundary before you switch anything off. Yeethook is a notification service. It does not provide:
- An SDK, entitlements, or receipt validation in your app.
- Paywalls, experiments, or offer management.
- Google Play, Stripe, or Amazon subscriptions. Yeethook is Apple-only.
- Revenue analytics, MRR charts, cohorts, or customer profiles.
If you rely on RevenueCat for any of those, keep it. Yeethook only competes with the Slack notification part.
Side by side
| Capability | RevenueCat Slack integration | Yeethook |
|---|---|---|
| Data source | RevenueCat's event pipeline | App Store Server Notifications V2, direct from Apple |
| SDK or project required | RevenueCat project and SDK | None. Optional p8 key for automatic setup |
| Subscription events | 9 event types | All App Store Server Notification V2 types and subtypes |
| Message fields | Customer ID, product, revenue, timestamp | Product, price and currency, expiry, auto-renew, transaction ID, environment, app |
| Refunds | No negative revenue events | REFUND, REFUND_DECLINED, REFUND_REVERSED with product and price |
| App Store Connect events (review, builds, TestFlight) | No | Yes, all 12 webhook types |
| Google Play, Stripe, Amazon | Yes | No |
| Multiple Slack channels | Not documented | Per app and per event type |
| Sandbox events | Separate toggle | Delivered with an Environment field |
| Customer profiles and attributes | In the RevenueCat dashboard | No |
| Setup | Slack Incoming Webhook in RevenueCat | Slack app manifest plus p8 key or manual URL |
When to switch, when to keep both
You only use RevenueCat's Slack integration for Apple alerts. Point Apple's notifications at Yeethook and you get every event type with transaction details, plus review and TestFlight events, without the SDK dependency for notifications.
You want App Store Connect events too. Keep RevenueCat for the SDK and entitlements. Add Yeethook for Slack. The App Store Connect webhooks are independent of anything RevenueCat does.
You ship on Google Play as well. Stay with RevenueCat for cross-platform purchase alerts. Use Yeethook for the Apple-only events it does not cover: review status, builds, and TestFlight.
How to Set It Up
- Sign up at yeethook.com. Free for one app, no credit card required.
- Upload your p8 key so Yeethook can register the App Store Server Notifications URL and the App Store Connect webhooks with Apple, or choose Manual Setup and paste the URL into App Store Connect yourself.
- Add your app and select the subscription notification types you want, plus any review, build, or TestFlight events.
- Connect Slack with the pre-built app manifest and route subscription events to
#revenue.
Apple accepts one production server URL and one sandbox server URL per app. If the production URL is already in use by another service, start with the sandbox URL to see the messages, then decide.
Pricing
RevenueCat's Slack integration is bundled with RevenueCat's plans. Yeethook is free for one app, one Slack or Discord channel, and 100 events per month, with enrichment included. Team is $15/month for three apps, three channels, three members, and 500 events. Scale and Fleet add more apps, members, and volume. Paid plans start with a 7-day trial. See pricing for details.