Sleuth Documentation
HomeBlogSupportSign up
  • Getting started
  • Navigating Sleuth
  • DORA metrics
    • Deploy frequency
    • Change lead time
    • Change failure rate
    • MTTR
    • Interpreting Metrics in Sleuth
  • Deployment tracking
    • Organization
      • Labels
      • Trends
      • Compare
      • Search
      • Status
    • Projects
      • Issue trackers
    • Environments
    • Code deployments
      • Creating a deployment
      • How to register a deploy
      • Rollbacks
      • Automatic tagging
      • Deployment locking
      • Environment drift
      • Move code deployments
      • Search everything
    • Feature flags
    • Manual changes
    • Deploys
    • Teams
  • Work in Progress
  • Goals
  • Sleuth Automations
    • Automations Marketplace
      • Installing Automations
        • Installing PR "Update" Automations
      • Editing and uninstalling Automations
      • Smart suggestions
      • Understanding efficacy
    • Custom Automations
      • Automations Cookbook
      • Webhook Actions
      • Trigger Build Actions
        • Bitbucket Pipelines
        • CircleCI
        • Github Actions
        • Jenkins
  • Slack & Email Notifications
  • Auto-verify deploys
    • Anomaly detection
    • Error impact
    • Metric impact
  • Ignoring pull requests
  • Slack mission control
    • Approvals
    • Project notifications
    • Personal notifications
    • Search Sleuth in Slack
    • Project/Deployment history
    • Developer standup
  • Sleuth API
    • Deploy Registration
    • Deploy import
    • Manual Change
    • Custom Incident Impact Registration
    • Custom Metric Impact Registration
    • Deprecation information
    • GraphQL Queries
    • GraphQL Mutations
    • Query batching
  • Integrations
    • About Integrations...
    • Code integrations (read-only)
      • Azure DevOps
      • Bitbucket
      • GitHub
      • GitLab
      • Custom Git
      • Terraform Cloud
    • Code integrations (write)
    • Feature flag integrations
      • LaunchDarkly
    • Impact integrations
      • Error trackers
        • Bugsnag
        • Honeybadger
        • Rollbar
        • Sentry
      • Metric trackers
        • AppDynamics
        • AWS CloudWatch
        • Custom
        • Datadog
        • Jira metrics (Cloud / Data Center)
        • NewRelic
        • SignalFx
      • Incident tracker integrations
        • Blameless
        • PagerDuty
        • Datadog Monitors
        • Statuspage
        • Opsgenie
        • Jira (Cloud/Data Center)
        • FireHydrant
        • Rootly
        • ServiceNow
        • Custom
          • Grafana OnCall
      • CI/CD builds
        • Azure Pipelines
        • Bitbucket Pipelines
        • Buildkite
        • CircleCI
        • GitHub Actions
        • GitLab CI/CD Pipelines
        • Jenkins
    • Sleuth DORA App for Slack
    • Microsoft Teams integration
    • CI/CD integrations
      • Azure Pipelines
      • Bitbucket Pipelines
      • Buildkite
      • CircleCI
      • Github Actions
      • GitLab CI/CD Pipelines
      • Jenkins
    • Issue tracker integrations
      • Jira Cloud
      • Jira Data Center
      • Linear
      • Shortcut
    • Fixing broken integrations
  • Pulse
    • Welcome to Pulse docs
    • Quick Start setup guide
    • Beginner tutorials
      • 1. How to create a Teamspace
      • 2. How to create a Review
      • 3. How to create a Survey
  • Features
    • Reviews
      • Review workflow
      • Review templates
      • Widgets and Sections
        • Widget type
      • Review settings
    • Surveys
      • Survey Workflow
    • Teamspaces
    • Inbox
    • AI assistant
    • General settings
      • Users and Teams
      • Investment mix
  • Settings
    • Organization settings
      • Details
      • Authentication
        • SAML 2.0 Setup
          • Okta Configuration
          • Azure AD Configuration
          • PingIdentity Configuration
      • Access Tokens
      • Members
      • Team Settings
      • Billing
    • Project settings
      • Details
      • Slack settings
      • Environment settings
      • Code deployment settings
      • Feature flag settings
      • Impact settings
    • Account settings
      • Account settings
      • Notifications settings
      • Identities settings
    • Role Based Access Control
  • Resources
    • FAQ
    • Sleuth TV
    • Purchasing
    • About Sleuth...
Powered by GitBook
On this page

Was this helpful?

  1. Sleuth Automations
  2. Automations Marketplace

Installing Automations

PreviousAutomations MarketplaceNextInstalling PR "Update" Automations

Last updated 1 year ago

Was this helpful?

We've made it incredibly easy to install automations from right from the Marketplace.

We see Sleuth Automations as part of continuous improvement experimentation platform, so we understand how important is to enable teams to quickly try out an automation, see if it's working for them, and then quickly move on to trying out additional automations.

The install process varies slightly depending on the , but all automations share the the following easy-install features:

  • All automations can be installed (and also ed) from completely from within Sleuth's UI.

  • The install process will never require issuing a PR or otherwise modifying your code repositories

  • The install process allows you determine a specific Team or Project to which an automation will apply

Most automations can be applied to either a Project or a Team, but some are limited to one or the other.

When installing an automation to a Project, the automation will apply by default to all Code Deployments within that Project, but some automations provide a configuration option for limiting their scope to specific Code Deployments within the selected Project

In order to use automations that update PRs in your Git provider, you'll need to make sure you've enabled "write" permissions for that Git provider within Sleuth.

To install an automation in your sleuth environment, follow these steps:

  • to find an automation you'd like to install

  • Click on the automation card to view additional details about the automation

  • Click Install in Sleuth

  • The next page allows you pick a Project or Team for the automation and might prompt for further configuration parameters depending on the specific automation. In this PR check example, Sleuth is asking for the maximum number of files allowed on a single PR. Other common parameters might include a Slack channel for sending notifications, an Environment selector for determining which environments an automation applies to, etc.

  • Once all required fields have been specified, click Install and continue

  • Sleuth will display a toast indicating that the installation was successful, and the installed automation now appears under the Automations item in the left-hand-navigation pane for the selected Project/Team.

edited or uninstall
Browse the Marketplace
Installing and configuring a PR check automation
Viewing installed automations for a specific Project
automation type