Runway Documentation
  • About Runway
  • 🚀Getting started
    • Adding apps
    • Setting up your integrations
      • Branching strategies
      • Builds and branches
      • Pattern strings / tokens
    • Preparing your first release
    • Setting up your team
  • 🎛️Using Runway
    • Navigating Runway
    • Build Distro
      • Quickstart
      • Uploading builds for distribution
      • Build Distro buckets
      • Sharing builds
      • Installing builds
      • Signing and provisioning cheat sheet
    • App overview
    • Releases
      • Release overview
      • Feature flags
      • Kickoff
      • Feature readiness
      • Translations
      • Release candidate
      • Regression testing
      • Beta testing
      • Screenshots
      • Metadata
      • Approvals
      • App submission
      • App store review
      • Release
    • Release schedule
    • Rollout
    • Hotfixes
    • Rollbacks
    • Checklists
    • Build matching
    • App settings
      • General settings
      • Team settings
      • Release pilot rotation
      • Integrations settings
      • Profiles and devices
      • Signing keys
      • Health metrics settings
      • Automations settings
      • Notifications settings
      • Schedule settings
      • Beta testing settings
      • Metadata settings
      • Release defaults
      • Checklists settings
      • Custom strings settings
    • Organization overview
    • Organization settings
      • Team
      • SSO/SAML
    • User settings
    • Over-the-air (OTA) releases
  • ⚙️Integrations
    • Integrations overview
    • Version control
      • Azure Repos
      • Bitbucket
      • GitHub
      • GitLab
    • Project management
      • Asana
      • Azure Boards
      • GitHub Issues
      • Jira
      • Linear
      • Pivotal Tracker
      • Monday.com
      • Shortcut
    • CI/CD
      • App Center Build
      • Azure Pipelines
      • Bitbucket Pipelines
      • Bitrise
      • Buildkite
      • CircleCI
      • Codemagic
      • GitHub Actions
      • GitLab CI
      • Jenkins
      • TravisCI
      • Xcode Cloud
    • Regression testing
      • TestRail
      • Xray
    • Beta testing
      • Google Play testing tracks
      • TestFlight
      • App Center
      • Firebase App Distribution
    • App stores
      • App Store Connect
      • Google Play Console
      • Amazon Appstore
      • Huawei AppGallery
      • Samsung Galaxy Store
    • Notifications
      • Microsoft Teams
      • Slack
    • Stability monitoring
      • BugSnag
      • Datadog
      • Embrace
      • Firebase Crashlytics
      • New Relic
      • Sentry
      • Dynatrace
    • Observability & analytics
      • Amplitude
      • Datadog
      • Google Analytics
      • Mixpanel
      • New Relic
      • Custom observability & analytics
    • Feature flagging
      • Optimizely
      • LaunchDarkly
    • Scheduling
      • Opsgenie
      • PagerDuty
    • Translations
      • Crowdin
      • Lokalise
    • Calendar
      • Google Calendar
  • ⚡Automations
    • Automations overview
    • Types of automations
  • 🔔Notifications
    • Notifications overview
    • Types of notifications
  • 🪝Webhooks
    • Outgoing webhooks
  • 📡REST API
    • Overview
    • Reference Docs
    • Markdown Badge API
    • App configuration files
  • 🛠️Quickstart CI/CD
    • Quickstart CI/CD overview
    • Getting started
  • Support
    • Contact us
Powered by GitBook
On this page
  • Notifications settings
  • Primary channel
  • Configuring individual notifications

Was this helpful?

  1. Notifications

Notifications overview

PreviousTypes of automationsNextTypes of notifications

Last updated 3 months ago

Was this helpful?

Notifications are a key way for teams to stay in sync and collaborate more efficiently during a release process. Where before you might have been checking in various tools for status updates (? ?), or pinging teammates when a task needed to be done (?), Runway has you covered.

Notifications settings

Primary channel

All notifications will go to your primary channel, unless an override is defined in an individual notification's settings.

Configure primary channel

Visit your integration settings to configure your primary channel:

Configuring individual notifications

Navigate to notifications settings

  1. Select an app in the top left corner from the Switcher

  2. Navigate to App Settings by clicking the gear icon (⚙️) at the top of the Timeline sidebar

  3. Click on Notifications in the sidebar

Settings for individual notifications

  • Enabled: Toggle this type of notification on or off

  • Mentions: Mention individual users or groups in the notification

  • Channel(s) — Select or enter one or more channel names for this type of notification.

Runway can send notifications to a private Slack channel once it has access to the channel, via one of these methods:

  • In Slack, send a message to the private channel using the @Runway Slack handle

  • In Slack, click on the user count icon at the top right of the private channel, then Integrations > Add an app. Search for Runway and click Add

Once the Runway app has been added, return to Runway, and the private channel name will now be available as an option in Runway integration settings for Slack.

Leave this field blank to send notifications to your configured (default).

Release-specific channel names containing the pattern {version} are supported. If the automation is enabled, Runway will automatically create a new Slack or Teams channel(s) for the release according to the entered pattern, if it doesn't exist yet.

You can also opt into receiving email notifications for each app-level notification type. For more details visit the .

🔔
primary channel
Notifications
MS Teams
Slack
Is that build finished
Who's in charge of the next release
did we get signoff from Compliance
Create release-specific channel(s)
email notification settings documentation