A TestFlight tester crashes your app at 2am. By the time you pick up your phone, the crash log, the tester's name, their device model, and the screenshot they attached are already sitting in your team's Slack channel. One message. Full context. No one opened App Store Connect.
That's what Yeethook does. And today, it's live.
What it is
Yeethook catches every webhook Apple sends from App Store Connect and App Store Server Notifications v2, enriches them with your p8 API key, and delivers formatted Slack messages with the complete picture.
Not raw JSON. Not "event ID: abc123, go look it up." The actual crash log. The actual tester name. The actual screenshot.
Here's what enrichment looks like across event types:
- Crash reports arrive with the stack trace, tester name, device model, OS version, and attached screenshots
- Build events show your app name, version, build number, and processing status
- App review updates tell you exactly which version moved to In Review, got approved, or was rejected
- Subscription events include the plan, renewal period, and transaction context
- TestFlight feedback delivers the tester's screenshot and comments directly into Slack
Every event type. Both Apple webhook sources. One service.
What else ships today
The enriched Slack messages are the core, but we built more than a webhook relay.
Dashboard. Four stat cards (events received, delivered, delivery rate, failed), an area chart showing volume over time, top event types by volume, and a recent events table. Period-over-period comparison so you can spot trends. Your team's App Store Connect activity, summarized in one view.
Event log. Every event Yeethook receives is logged. Filter by status, event type, app, channel, or date range. Drill into any event to see the raw Apple payload, enriched data, delivery status per channel, and retry history. When something looks off, you don't guess. You look it up.
Webhook health monitoring. Yeethook watches your webhooks on both the Apple side and the Slack side. Webhook deleted by Apple? Detected. Slack URL revoked? Caught. Yeethook flags the issue and offers a one-click fix. Your connections stay alive without you babysitting them.
Team accounts. One setup covers the whole team. Invite members, assign Owner or Member roles, share a single dashboard and event log. No per-developer setup, no individual push notifications that only one person sees. Everyone knows what's happening.
Usage tracking. Real-time resource consumption against your plan limits. Apps, channels, members, and monthly events, each with a progress bar and status indicator. You always know where you stand.
Setup takes two minutes
- Upload your p8 API key from App Store Connect. Yeethook encrypts it with AES-256-GCM at rest.
- Pick your apps. Yeethook can automatically create Apple webhooks for you, or you can configure them manually.
- Paste a Slack webhook URL. Route different event types to different channels if you want. Crashes to #bugs, reviews to #releases, subscriptions to #revenue.
- Done.
You can skip the p8 key entirely if you prefer. Yeethook still delivers formatted Slack messages for every event type. You just won't get the enriched context (crash logs, tester details, screenshots, subscription info). We call this Manual Setup.
Free for one app
The Free plan gives you one app, one Slack channel, 100 events per month, and full enrichment. No credit card. No trial expiration. Just connect and go.
If you're shipping multiple apps or working with a team, the paid plans start at $15/month and scale up from there. Enrichment is included on every plan. We don't gate the good stuff.
Why now
Apple added webhook support to App Store Connect. That's the foundation. But the raw webhooks only tell you that something happened. They don't tell you the full story. The gap between "something changed" and "here's exactly what happened, who it happened to, and what it looked like" is what Yeethook fills.
If you ship iOS or macOS apps and you're tired of the daily App Store Connect check-in, give it a try.
Stop checking. Start knowing.