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.
The Latest
In live financial environments, capital markets software cannot pause for rebuilds. New capabilities are introduced as stacked technology layers to meet evolving demands while systems remain active, data keeps moving, and controls stay intact. AI is no exception, and its opportunities are significant: accelerated decision cycles, compressed manual workflows, and more effective operations across complex environments. The constraint isn't the models themselves, but the architectural environments they enter ...
Like most digital transformation shifts, organizations often prioritize productivity and leave security and observability to keep pace. This usually translates to both the mass implementation of new technology and fragmented monitoring and observability (M&O) tooling. In the era of AI and varied cloud architecture, a disparate observability function can be dangerous. IT teams will lack a complete picture of their IT environment, making it harder to diagnose issues while slowing down mean time to resolve (MTTR). In fact, according to recent data from the SolarWinds State of Monitoring & Observability Report, 77% of IT personnel said the lack of visibility across their on-prem and cloud architecture was an issue ...
In MEAN TIME TO INSIGHT Episode 23, Shamus McGillicuddy, VP of Research, Network Infrastructure and Operations, at EMA discusses the NetOps labor shortage ...
Technology management is evolving, and in turn, so is the scope of FinOps. The FinOps Foundation recently updated their mission statement from "advancing the people who manage the value of cloud" to "advancing the people who manage the value of technology." This seemingly small change solidifies a larger evolution: FinOps practitioners have organically expanded to be focused on more than just cloud cost optimization. Today, FinOps teams are largely — and quickly — expanding their job descriptions, evolving into a critical function for managing the full value of technology ...
Enterprises are under pressure to scale AI quickly. Yet despite considerable investment, adoption continues to stall. One of the most overlooked reasons is vendor sprawl ... In reality, no organization deliberately sets out to create sprawling vendor ecosystems. More often, complexity accumulates over time through well-intentioned initiatives, such as enterprise-wide digital transformation efforts, point solutions, or decentralized sourcing strategies ...
Nearly every conversation about AI eventually circles back to compute. GPUs dominate the headlines while cloud platforms compete for workloads and model benchmarks drive investment decisions. But underneath that noise, a quieter infrastructure challenge is taking shape. The real bottleneck in enterprise AI is not processing power, it is the ability to store, manage and retrieve the relentless volumes of data that AI systems generate, consume and multiply ...
The 2026 Observability Survey from Grafana Labs paints a vivid picture of an industry maturing fast, where AI is welcomed with careful conditions, SaaS economics are reshaping spending decisions, complexity remains a defining challenge, and open standards continue to underpin it all ...
The observability industry has an evolving relationship with AI. We're not skeptics, but it's clear that trust in AI must be earned ... In Grafana Labs' annual Observability Survey, 92% said they see real value in AI surfacing anomalies before they cause downtime. Another 91% endorsed AI for forecasting and root cause analysis. So while the demand is there, customers need it to be trustworthy, as the survey also found that the practitioners most enthusiastic about AI are also the most insistent on explainability ...
In the modern enterprise, the conversation around AI has moved past skepticism toward a stage of active adoption. According to our 2026 State of IT Trends Report: The Human Side of Autonomous AI, nearly 90% of IT professionals view AI as a net positive, and this optimism is well-founded. We are seeing agentic AI move beyond simple automation to actively streamlining complex data insights and eliminating the manual toil that has long hindered innovation. However, as we integrate these autonomous agents into our ecosystems, the fundamental DNA of the IT role is evolving ...
AI workloads require an enormous amount of computing power ... What's also becoming abundantly clear is just how quickly AI's computing needs are leading to enterprise systems failure. According to Cockroach Labs' State of AI Infrastructure 2026 report, enterprise systems are much closer to failure than their organizations realize. The report ... suggests AI scale could cause widespread failures in as little as one year — making it a clear risk for business performance and reliability.