Connecting, Resolving, and Extending

There are three primary stages to getting the most out of Transposit.

  • Connect. We begin with a process focused on helping administrators and configurators set up automated workflows in Transposit.
  • Resolve. Here we focus on helping you, as a user of Transposit, go through your first sample incident.
  • Extend. Finally, we provide a set of activities to encourage administrators and configurators to explore the more advanced features of Transposit.


By the time you, as an administrator or configurator, have completed the initial stage of the setup experience, you will have told Transposit about the tools your team uses, you will have authenticated to some of those tools, and you will have set up your team's first script.

Right from the start, you will see a list of commonly used Cloud services, organized by category. Useful pre-built scripts from Transposit's library are prioritized for the tools that you select to use.

You should be able to set up your first automation, from selecting tools, to authentication, within 10 minutes of logging into Transposit. This stage of the setup experience is exposed to any user that has permission to create new scripts.


Once a first script has been set up, the first step for you, as a user working as an incident responder in a team, is to work through the process of managing your first incident.

This part of working with Transposit differs depending on whether your workflow has been set up to integrate with Slack or whether Transposit's web user interface is used. For both scenarios, you now step through the main parts of interacting with a Transposit incident.

That includes activities such as:

  • Creating an incident.
  • Updating an incident’s severity and status.
  • Running a script.
  • Creating and assigning an action item.
  • Learn from the related documentation about the help guide with additional Slack command options.
  • Closing an incident.

This set of steps happens without any additional setup required because the default incident template handles basic incident flows end-to-end without additional customization being needed.

You'll be able to complete this stage in no more than 10 minutes. Every user is able experience this stage of the setup experience.


Once the initial incident resolution scenario has been completed, and the administrator or configurator has received feedback and discussed next steps with users in their team, they can move on to exploring Transposit's extensibility and customization options.

This can include one or more of the following activities:

  • Setting up a runbook.
  • Setting up an action item.
  • Configuring webhooks and alerts.
  • Configuring a custom field.
  • Setting up a custom incident type.

This set of tasks is not required for basic usage of the product, though you'll quickly find them to be relevant in making full use of the features Transposit provides to help support incident management processes.