HN Showcase
Back to browse
Yeethook, Enriched App Store Connect Webhooks to Slack

Yeethook, Enriched App Store Connect Webhooks to Slack

by ronistrom·Feb 27, 2026·1 point·0 comments
Visit ProjectView on HN

AI Analysis

●●●BangerSolve My ProblemSlick

Automatic webhook enrichment with p8 key context—Apple events arrive readable in Slack.

Strengths
  • •Solves genuine iOS developer pain: Apple's cryptic webhook payloads combined with scattered context across tools (Sentry, RevenueCat, Firebase)
  • •Automatic p8 key setup eliminates manual webhook configuration entirely; webhook health monitoring auto-repairs broken integrations
  • •Multi-channel routing (Slack, Discord, Teams, PagerDuty) + event filtering means one service replaces multiple integrations
Weaknesses
  • •Requires uploading p8 API key to third-party service—security/trust model needs transparent audit or SOC2
  • •Market is iOS teams only; doesn't address Android or cross-platform developers
Target Audience

iOS developers, app teams using App Store Connect

Similar To

Sentry · RevenueCat · Firebase

Post Description

Hey HN, I built Yeethook (https://www.yeethook.com/) to solve a problem that bugged me every day as an iOS developer: having no real-time visibility into what's happening in App Store Connect.

The problem: Tools like Sentry, RevenueCat, and Firebase each cover a slice, but nothing catches all Apple events in one place. And Apple's own webhook payloads are cryptic: event IDs and status codes, not the information you actually need. I wanted one service that catches everything, enriches it, and routes it to the right Slack channels.

What Yeethook does: You upload your App Store Connect API key (p8), and Yeethook:

- Receives webhooks from both App Store Connect and App Store Server Notifications V2 - Uses your p8 key to pull the full context: crash logs with stack traces, tester names, device models, OS versions, screenshots, subscription details - Delivers formatted Slack messages to the right channels. Crashes to #bugs, review updates to #releases, subscription events to #revenue.

A TestFlight tester hits a crash, and seconds later your team's Slack channel has the crash log, the device info, and the screenshot. Before anyone opens Xcode, everyone already knows what happened.

The p8 key is optional (you can skip enrichment and configure webhooks manually), and encrypted at rest when connected. The Slack connection is one-way via incoming webhooks. Yeethook sends messages, it can't read your channels.

Setup takes a few minutes. Upload your p8 key, pick your Slack channels, and Yeethook creates the webhooks on Apple's side automatically. It also monitors webhook health on both the Apple side and the Slack side.

Beyond delivery: There's a dashboard with delivery metrics and trends, and an event log where you can inspect any event down to the raw payload, enriched data, and per-channel delivery status with retry history. One team account with shared visibility, no per-developer setup.

Pricing: Free for 1 app and 100 events/month. Paid plans start at $15/mo. Enrichment (p8) is included on every plan, including free.

Right now it's Slack only. Discord, Teams, PagerDuty, and email are next.

I'd love to hear what you think, especially from teams already dealing with App Store Connect webhooks.

Similar Projects