The DIY approach
You can process Apple webhooks yourself. Here's what that looks like:
- Webhook endpoint. A server that receives HTTP POST requests from Apple, validates signatures, and parses the payload. You deploy it, keep it running, and handle TLS termination.
- Event parsing. App Store Connect webhooks and App Store Server Notifications V2 have different payload formats. You write parsers for each event type and subtype.
- Slack formatting. Raw JSON is unreadable. You build message templates for every event type, handle edge cases, and maintain them when Apple changes payloads.
- Enrichment. The webhook payload often just contains an ID. To get crash logs, tester names, device info, or subscription details, you call the App Store Connect API yourself. That means managing p8 key auth, token rotation, and rate limits.
- Health monitoring. Webhooks break silently. Apple deletes them, disables them, or changes the URL. You build polling to detect this and alerting to notify yourself.
- Retry logic. Slack delivery fails sometimes. You implement retry queues, exponential backoff, and dead-letter handling.
This is a real project. Most teams either skip it entirely or build a minimal version that forwards raw JSON and call it done.
Alternatives
A few tools exist in this space, but they solve different problems or cover a fraction of the surface area:
App Store Connect CLI. The most popular open-source project in this space is an impressively comprehensive Go CLI that covers almost the entire App Store Connect API: builds, TestFlight, reviews, subscriptions, signing, Xcode Cloud, Game Center, notarization, and more. It ships as a single Homebrew-installable binary with JSON-first, non-interactive output designed for CI/CD pipelines. For webhooks specifically, it supports CRUD operations (create, update, delete, ping, redeliver) and delivery inspection, plus a manual notify slack command for one-off messages. This is an automation tool for doing things in App Store Connect, not a notification tool for knowing when things happen. It can create and manage webhooks, but it doesn't receive, enrich, or deliver the events those webhooks produce. Complementary to Yeethook, not competitive.
appstore-webhook-proxy. A Node.js proxy that forwards App Store Connect webhooks to Slack and Microsoft Teams via incoming webhook URLs. It has well-crafted Slack Block Kit message templates with deep links to App Store Connect and Xcode Organizer for TestFlight feedback, and one-click deployment to Render makes it easy to get running. It verifies signatures with HMAC SHA-256 and has templates for 6 of the 12 App Store Connect event types (the original five plus the ping event). The newer alternative distribution and background asset event types are not covered. Unknown events arrive as raw JSON. Delivery targets are limited to one Slack channel and one Teams channel. You deploy it yourself (Docker, Render, Unraid, or bare Node.js) and own the infrastructure: hosting, uptime, updates, and security patches. No p8 enrichment, no App Store Server Notification V2 support, no health monitoring, no auto-repair, no event routing.
Automation platforms. Make and Zapier have no native App Store Connect integration. You can use their generic webhook modules to receive Apple's HTTP POST and route it to Slack, but you configure each event type manually, messages are raw or minimally formatted, and there is no enrichment. Pricing is per operation, which adds up at volume. Relay.app has a native "App Store" integration, but it only covers reviews: one trigger ("App reviewed") and one action ("Reply to review"). It does not handle App Store Connect webhooks or App Store Server Notifications V2.
App Store Connect mobile app. Apple's free iOS app sends push notifications for some App Store Connect events: build processing status, app review updates, TestFlight invitation acceptance. It is the most obvious baseline, already on many developers' phones. But it notifies one developer at a time with a one-line push notification. There is no enrichment (no crash logs, no tester details, no screenshots), no team-wide visibility, no App Store Server Notifications V2 coverage (subscriptions, renewals, refunds, churn signals), no event routing, and no searchable history. Every developer on the team needs to install the app and sign in individually. For a solo dev who just wants a heads-up that a build finished, it works. For a team that needs the full picture in a shared channel, it does not replace a webhook-based solution.
This comparison is based on a review of the listed projects conducted on February 15, 2026. Features may have changed since then.
What Yeethook does differently
Yeethook is a managed service. You don't deploy or maintain anything.
Enrichment, not just forwarding. Yeethook uses your p8 key to call the App Store Connect API and attach the details Apple doesn't include in the webhook: crash logs with stack traces, tester names and emails, device models, OS versions, screenshots, and subscription context. You get the full story, not a payload ID.
Every Apple event type. All 12 App Store Connect webhook types and all 17+ App Store Server Notification V2 types. One service, both webhook sources.
Formatted Slack messages. Every event arrives as a readable, scannable message. No raw JSON, no parsing, no squinting at payload fields.
Webhook health monitoring. Yeethook watches every webhook on both the Apple side and the Slack side. Deleted webhook? Recreated. Disabled? Re-enabled. URL drifted? Fixed. Slack channel gone? Auto-deactivated before delivery failures pile up.
Event routing. Route different event types to different Slack channels. Crashes to #bugs, reviews to #releases, subscriptions to #revenue. Per-app, per-event-type routing rules.
Security. Your p8 key is encrypted with AES-256-GCM at rest. Slack credentials are encrypted the same way.
Side by side
| Capability | DIY server | Open-source proxy | ASC mobile app | Yeethook |
|---|---|---|---|---|
| Receives Apple webhooks | You build it | 6 of 12 ASC types | Push notifications for some ASC events | All ASC + ASN V2 types |
| Signature verification | You build it | Yes (HMAC SHA-256) | N/A | Built in |
| Delivery destinations | You build it | 1 Slack + 1 Teams channel | Individual push notifications | Slack (multiple channels) |
| Formatted messages | You build it | Templates for known types | One-line notification | Full formatting, all types |
| p8 enrichment (crash logs, tester info) | You build it | No | No | Built in |
| Health monitoring and auto-repair | You build it | No | N/A | Built in |
| Event routing to multiple channels | You build it | No | No | Built in |
| Server Notifications V2 support | You build it | No | No | Built in |
| Team-wide visibility | You build it | One channel | Per-person setup | Shared Slack channels |
| Searchable history | You build it | In Slack | No (push notifications disappear) | In Slack |
| Infrastructure to maintain | Yes | Yes | No | No |
Getting started
- Sign up at yeethook.com.
- Upload your p8 key for automatic webhook setup and enrichment, or choose Manual Setup.
- Add your apps from App Store Connect.
- Connect Slack and route events to your channels.
Free for one app. No credit card required.