Upload your App Store Connect API key and Yeethook catches every webhook (crashes, reviews, subscriptions, builds), enriches them with full context (crash logs, tester names, screenshots), and routes formatted messages to the right Slack channels.
No reviews yetBe the first to leave a review for Yeethook
Wispr Flow: Dictation That Works EverywhereStop typing. Start speaking. 4x faster.
Promoted
Maker
📌
Hey Product Hunt! I'm Roni, and I built Yeethook because I got tired of having no real-time visibility into what was happening in App Store Connect.
The problem: Apple's webhooks exist, but the payloads are cryptic. You get event IDs and status codes, not the information you actually need. And nothing catches all Apple events in one place. Tools like Sentry, RevenueCat, and Firebase each cover a slice.
So I built a service that catches everything, enriches it using your App Store Connect API key, and routes the complete picture to Slack. A TestFlight tester hits a crash, and seconds later your team has the crash log, device info, and screenshot. Before anyone opens Xcode.
What makes this different from just forwarding webhooks:
- Enrichment: Uses your p8 key to pull crash logs with stack traces, tester names, device models, OS versions, screenshots, subscription details
- Both webhook types: App Store Connect webhooks AND App Store Server Notifications V2
- Smart routing: Crashes to #bugs, reviews to #releases, subscriptions to #revenue
- Auto-setup: Upload your p8 key and Yeethook creates the webhooks on Apple's side automatically
- Reliability: Monitors webhook health on both Apple and Slack sides, auto-repairs issues
Free for 1 app and 100 events/month with full enrichment included. No credit card needed.
I'd love to hear what you think, especially from teams already dealing with App Store Connect webhooks. What events would be most useful for your workflow?