Transposit announced expanded functionality of Transposit Actions and Runbooks, enabling more rapid incident response times and consistent data across all integrations.

The new runbook builder template and additional capabilities for actions allow teams to automate repeatable tasks at the onset of a runbook as well as group actions together as a single executable operation. To ensure consistency of data across processes, Transposit is also enabling teams to take output from an action and pass it through as input for another action.

“Our updated no-code runbook builder amplifies the power of human-in-the-loop automation, empowering customers to automate burdensome, repetitive tasks while allowing them to step in when necessary to more rapidly take action,” said Divanny Lamas, CEO of Transposit. “Transposit is simplifying automation with stateful runbooks and other features that keep humans as our number one priority.”

With the newly extended set of capabilities, users can now conjoin a set of standalone actions into a group of actions with a singular button to execute them, drastically accelerating incident response times. While incident response actions inherently cannot be entirely automated, processes should not be entirely manual either. After the initial triage of an incident, teams move into incident coordination and remediation. In these phases, there are many actions that can be performed simultaneously, including further escalations, communications to larger groups, SLA awareness and response urgency.

Development and operations teams can now build actions in Transposit to take the output of one action as the input of another action, creating limitless opportunities for automation. Teams can create incident management processes that take the unique Jira issue key to tie together communication channels in Slack and Zoom and to escalate issues to engineers and the operations team, all with the context available in the originating ticket. In doing so, all communication channels created through the runbook use the same incident name.

The updated no-code runbook builder boosts the power of Transposit’s human-in-the-loop automation, redirecting the burden of repetitive actions to automation technology while enabling humans to intervene and take action faster. The new UI makes it simple to automate predictable tasks that kick off any activity, take action on multiple connected services with a single click and automate actions to run when a runbook is done or has an error.

The new template fully automates actions on the onset of a runbook. For example, when an incident begins, teams may create a Jira ticket and Zoom bridge and conduct an AWS service status check. Now, these actions will automatically execute once a runbook is in-use.

Teams can choose to automate actions upon completion of a runbook. Such actions can include creating an incident report, closing a Slack channel or adding an update to Statuspage. When an automated action has an error, the runbook state will update to “error,” guaranteeing teams are aware that an element has not run properly and can take corrective action. Teams can create automated actions like notifying the incident commander or restarting a server.

Transposit is creating new actions every day to create more automated scenarios for the platform’s hundreds of connectors. New actions have been added with GoToMeeting, GitHub, Google Drive, Octopus and Airtable that enable teams to do everything from creating GitHub releases and repos, to creating a Google Drive folder to deploying an Octopus release.