The Problem
Dumping every Apple event into a single Slack channel creates noise. Developers don't want subscription alerts. Product managers don't want build processing updates. QA doesn't want refund notifications.
The Solution
Yeethook lets you route events by type to different Slack channels:
| Channel | Events |
|---------|--------|
| #releases | App review status, build processing |
| #testflight | TestFlight build approvals, external beta states |
| #bugs | Crash reports, screenshot feedback |
| #revenue | Subscriptions, renewals, refunds |
| #churn | Auto-renew disabled, billing failures, expirations |
| #billing-alerts | Consumption requests, failed renewals |
Each app can have multiple Slack targets, and each target can filter by event type. This means the same app can send crashes to #bugs and reviews to #releases.
How It Works
- Create targets — Each target is a Slack webhook URL linked to a channel.
- Link apps to targets — Connect your apps to one or more targets.
- Set event filters — Choose which event types each target receives. Leave empty to receive all events.
Best Practices
- Start simple: Begin with one channel for all events, then split as volume grows.
- Dedicated crash channel: Crashes deserve their own channel for immediate triage.
- Revenue visibility: Give your product and finance team a
#revenuechannel. - Alert fatigue: Don't route high-volume events (like DID_RENEW) to channels that need immediate attention.