Statused logoStatused
ChangelogSystem StatusGet HelpGo to Dashboard

Webhooks

Automate your app release workflow with webhooks. Save CI minutes, avoid app rejections, and trigger custom actions when your app status changes.

Webhooks let you receive real-time notifications about your app status changes directly in your own systems. Perfect for triggering CI/CD workflows, notifying your team, or automating release processes.

Why Use Webhooks?

Save CI Minutes

Stop waiting in CI for iOS build processing. Get notified when your app is ready and resume your workflow automatically.

Instant Automation

Trigger custom actions the moment your app status changes — notify QA, submit for review, or update your deployment dashboard.

Avoid App Rejections

Toggle feature flags when your app enters review, and automatically switch back once it's approved.

CI/CD Integration

Seamlessly integrate with GitHub Actions, Jenkins, GitLab CI, or any system that can receive HTTP requests.

Smart CI/CD Workflows

The most powerful use case: stop burning expensive CI minutes while waiting for Apple to process your builds.

Traditional Workflow (Wasteful)

Submit App → Wait in CI (15min - 3hrs) → Process Complete → Continue Pipeline
                ↑ Expensive idle time

Some teams have varying approaches, all of which with their own drawbacks:

  • Manual work: CI generates build, engineer is notified when processing is done, then manually submits the app for review
  • CI timeouts: CI systems usually have built-in timeouts to prevent indefinite waiting and may fail the job after a certain period, before the build is processed
  • Day-after submission: App is submitted for processing and only the next day the app is submitted for review, delaying releases

Smart Webhook Workflow (Efficient)

Submit App → Stop CI Job → Webhook Notification → Resume Pipeline
                ↑ Zero idle cost

This approach can save 15 minutes to several hours of CI time per release, depending on app store processing times. For teams releasing frequently, this adds up to significant cost savings.

Avoid App Rejections with Feature Flags

Here's the reality: App Store reviewers sometimes flag features that have been working perfectly for months, or get confused by A/B tests that show different experiences, or stumble upon edge cases that aren't even related to your current update.

The industry-standard workaround (that Apple would prefer you didn't know about, but every experienced team uses): present a vanilla experience during review.

The goal isn't to hide bugs — it's to create a consistent, predictable experience that won't trigger a reviewer's "something's fishy" radar.

  • When app enters review → Disable experimental features
  • When app is approved → Re-enable all features

This ensures reviewers get the most straightforward version of your app, whether they're testing with a reviewer account, as an anonymous user, or in some edge case scenario you never anticipated. Because the last thing you need is a rejection for a feature that's been stable for months but happened to confuse the reviewer.

This pattern works especially well for:

  • A/B testing features that might confuse reviewers who expect consistent behavior
  • Beta features that aren't ready for prime time (or prime time reviewers)
  • Features that require specific user data or permissions to function properly

Need feature flags?

This assumes you already have a feature flagging system in place. Statused handles the "when to toggle" part by tracking your app's review status — you bring the flags, we'll trigger the automation. Works with any system: 3rd party services, your homegrown solution, or even a simple config file.

Team Coordination

  • QA notifications: Alert your QA team when TestFlight builds are ready
  • Release announcements: Inform stakeholders when apps go live
  • Issue escalation: Page on-call engineers for rejected submissions

Need something simpler?

For pure messaging without automation, Slack notifications often work just as well and require less setup. Learn more about our Slack integration.

Release Orchestration

  • Feature phased rollout: Start feature flag rollouts when your app is approved or released
  • Multi-platform releases: Coordinate iOS and Android releases
  • Backend synchronization: Deploy backend changes when mobile apps are approved
  • Rollback automation: Trigger rollback procedures for failed releases

Get Started

Ready to automate your release workflow? Here's what you need to set up:

Configure Webhooks

Set up your webhook endpoints and configure which events to receive.

Security & Authentication

Learn how to secure your webhooks with secrets and signature validation.

Webhook Reference

Complete reference for event types, payload formats, and CloudEvents specification.

Code Examples

Ready-to-use examples for GitHub Actions, CI/CD pipelines, and popular frameworks.

Ready to save CI costs and automate your releases? Start with configuring your first webhook.

Slack

Learn how to set up Slack notifications for your app store status changes with Statused.

Configure Webhooks

Set up webhook endpoints to receive real-time app store status notifications and automate your release workflow