The Problem
Webhooks break silently. Someone accidentally deletes the webhook in App Store Connect. Apple disables it after too many failures. The URL gets out of sync. You don't notice until events stop arriving — and by then you've missed critical notifications.
The Solution
Yeethook continuously monitors your webhook health on both sides:
Apple-side monitoring:
- Detects if a webhook was deleted from App Store Connect and recreates it.
- Detects if a webhook was disabled and re-enables it.
- Detects if the webhook URL drifted and corrects it.
- Monitors App Store Server Notification V2 configuration.
Delivery-side monitoring (Slack and Discord):
- Validates that channel webhooks are still reachable.
- Auto-deactivates a channel if Slack or Discord reports its webhook deleted or revoked.
- Circuit breaker pattern: after 3 consecutive delivery failures, automatically pauses to prevent cascading errors.
How It Works
When you open the Yeethook dashboard, it checks the health of every configured app. If something is wrong, you see the issue and can trigger a one-click repair. With a p8 key, many repairs happen automatically.
Requires a p8 Key
Webhook health monitoring and auto-repair require a p8 key because Yeethook needs to call the App Store Connect API to check and modify webhook configuration. This is one of the key reasons to use Quick Start with a p8 key.
Best Practices
- Check the dashboard periodically: Even with auto-repair, it's good to verify everything is healthy.
- Don't edit webhooks manually: Let Yeethook manage the webhook configuration to avoid conflicts.
- Keep channel webhooks current: If you archive a Slack channel or delete a Discord webhook, update the channel in Yeethook.