Transposit announced new Activities that harmoniously bring together ITSM processes and automation, providing a single source of truth across issues, incidents, tasks, requests and all associated operational data.
Often, engineering and operations teams are using automation and carrying out processes separately from the documentation of those actions. With Transposit Activities, automation is now baked into ITSM processes. As the container for all automation and processes, Activities enhance visibility and collaboration, enabling teams to use structured data from across the stack and take swift action with human-in-the-loop automated runbooks—all with automatic documentation of every action taken by both humans and machines. Transposit also announced that it is now SOC 2 Type 2 certified, cementing its commitment to providing customers with the confidence to keep their critical data safe within the platform and ensuring the company upholds the highest industry standards for data security.
“Transposit is taking a modern approach to ticketing that makes Transposit Activities the container to all processes and actions,” said Divanny Lamas, CEO at Transposit. “Teams shouldn’t have to leave the context of a ticket to take action. Now, when a new activity is created, the entire process can be carried out within that context through human-in-the-loop automated runbooks. Context stays relevant and up-to-date with automatic input and updates to the metadata within Activities.”
The data around automation and human processes provide context with activity metadata that captures progress, identifies owners and services, and ensures visibility across teams. Activity types and fields are fully customizable—no coding or specialized skills in the tooling are required. Teams can create activity types for various operational events, such as incidents, changes, requests, deployments and more. Fields within activity types can be customized for any use case.
While data can be added to Activities manually, it can also be updated automatically through runbook actions. Transposit enables teams to take output from one action and pipe it into another action or activity field. For example, a user could use an EC2 action to create a new VM, which would output its IP address. Now, users can send that action output – the IP address – into an activity field to be used in later actions. This auto-updating of tickets ensures context is always up to date, with less manual toil.
Minimizing ticket drudgery, Activities are the new auto-ticket, automatically capturing human and machine actions throughout any activity within the Transposit Timeline. With hundreds of pre-built integrations and the ability to connect to any API, the Transposit Platform enables teams to create processes that span their entire toolchain. Any automated or human action taken within an activity will be automatically captured, creating a full audit trail that teams need to ensure compliance and prepare for audits.
Teams can execute a human-in-the-loop automated process for an activity by running one or more runbooks, whether in response to an incident, service request, change or any other operational task. Runbooks can be automatically run based on an activity type or manually executed from within an activity.
Every action within a runbook will run within the context of the activity, ensuring teams have the data they need to make intelligent decisions and accelerate response to any event. Runbooks combine automation and human actions, automating away repetitive tasks while providing humans with the data and context they need to use judgment and take immediate action.
Benefits from Activities span beyond the event itself. Automatic documentation and a full history of runbook “runs” (the execution of a runbook) provide teams with the feedback loop needed to improve automation and processes over time. Teams have full visibility into which runbooks were used, how they were used and by whom, making it easy to understand where there are areas for improvement.
This full history of actions also enables people to use past learnings during a current event. If a similar event occurs, teams can easily look to see how it was handled previously and what were the mitigating actions taken.
Activities functionality includes:
- Manual or automatic activity creation: Activities can be created manually or automatically created from a runbook.
- Customizable activity types and fields: Activity types (i.e., incidents, service requests, change requests, deployments, etc.) and fields (i.e., severity, commander, environment, impacted services, status, requester name, etc.) within Activities are fully customizable.
- Runbook execution: One or more runbooks can be manually run from within an activity or automatically triggered based on activity type.
- Human-in-the-loop automation: Automated human-in-the-loop workflows can be run within an activity.
Auto-update Activities from action outputs: The output from a runbook action can be automatically used as an input for another action or to update an activity field.
- Timelines: Timelines automatically capture every action by humans and machines.
- Executive summary: A summary of the event progress can be added so stakeholders remain up to date. Updates to the executive summary will be documented in the Timeline and also pinned to the corresponding Slack channel.
- Slack integration: A Slack channel is automatically created for every new activity (this is customizable based on activity type – e.g., one may want a new Slack channel for every incident, but not every service request). Activities can be edited and runbooks can be executed from within Slack.
- Searchability and discoverability: Users can filter Activities by activity type for ease of discovery and investigation.
“Legacy service management wasn’t built for the best-of-breed cloud stack—integrating APIs and automation have been patched on after the fact, making it hard to customize legacy platforms, scale processes, and solve for modern use cases,” Lamas continued. “With today’s ops teams using dozens of tools and services to get work done, modern service management must enable teams to take the best functionality of all these services and bring them together to automate processes, enhance visibility, and deliver great customer experiences. Transposit brings automation to service management, combining no-code automation with a powerful developer platform so that teams have both the ease of use and flexibility to solve for any use case and achieve operational excellence.”
“Teams need automation, process and documentation brought together, connecting a best-of-breed cloud to enhance context and visibility, accelerate event response and continuously improve processes, which Transposit provides,” concluded Lamas.
The Latest
I've spent a lot of time in the channel, and one thing I keep coming back to is this: a partner program is only as good as what it looks like in the field. Many programs look great on paper, but when a partner is in front of a customer navigating a complex hybrid environment or trying to make the case for AI-powered observability, the gap between what a vendor promises and what it actually delivers becomes very clear, very fast ...
Enterprises today operate in a real-time environment where uninterrupted access to trusted data has become a baseline expectation for users, applications and automated systems. Traditional DataOps models, built on manual effort and human triage, cannot keep pace with this always active demand. AI agents are emerging as the operational backbone, ensuring consistent data availability, reinforcing trustworthiness and enabling a level of scale that manual processes cannot achieve ...
For decades, trust in the digital workplace rested on familiar signals. We trusted faces on video calls, voices on the phone, and emails that appeared to come from people we knew. These cues felt human and intuitive. They anchored how decisions were made, approvals were granted, and access was authorized. AI-powered deepfakes have quietly broken that model ...
Cloud migration was supposed to be a one-way door. For most enterprises, it turns out it isn't. Cloud data repatriation is a real and growing trend. A new survey ... finds that 89% of organizations plan to expand their on-premises infrastructure footprint over the next two years — and 75% have already moved at least some workloads back from public cloud in the past 24 months. The findings point to a broad rethinking of where data belongs ...
Over the past few years, large language models (LLMs) have revolutionized the software industry. Given their ability to excel at multi-step reasoning, LLMs have helped enterprises streamline workflows and adapt to the unknown. However, employing such models comes with sky-high costs, latency issues, and limited flexibility. In the realm of IT operations, it is generally wiser to employ smaller, domain-specific models instead ...
For years, DevOps teams operated under a simple assumption: collect enough telemetry, and you can find and fix any problem. That assumption is breaking down. Modern enterprises now operate across microservices, hybrid cloud environments, APIs, Kubernetes, and highly automated delivery pipelines. Releases happen continuously, dependencies shift constantly, and failures spread faster than teams can diagnose them ...
New Relic surveyed IT and engineering leaders from the media and entertainment (M&E) sector to understand what's working — and where challenges persist with their observability practices. The findings reveal how M&E organizations are navigating rising platform complexity, audience expectations, and AI-driven change. Below are five takeaways that stand out ...
Let me start with something I've seen play out more times than I can count. A team hits a wall with the cloud. Costs creep up, then spike. Performance starts to feel inconsistent. Someone in finance asks a simple question like "why did this double?" and nobody has a clean answer ... Maybe this isn't the right place for everything. That realization feels like a breakthrough, like you've identified the problem. In reality, you've just identified the starting line ...
In MEAN TIME TO INSIGHT Episode 24, Shamus McGillicuddy, VP of Research, Network Infrastructure and Operations, at EMA discusses network observability tool sprawl ...
In cloud-native systems, scaling is often as simple as moving a slider. For on-premise databases, the stakes are different. Over-provisioning hardware is expensive. Under-provisioning leads to performance bottlenecks that are difficult to fix once the equipment is in the rack ...