Transposit Glossary

Frequently used terms in Transposit are as follows.

  • Activity. A response to a requirement for work to be done, defined in Transposit as a container for everything happening as part of that response. Events are added to a timeline, generating an audit trail for the activity and producing a single source of truth. Incidents, tasks, requests, and jobs are examples of different activity types.
  • Runbook. A combination of documentation and automation enabling teams to codify processes. Automation can be incrementally added via hundreds of pre-built Actions using the no-code builder, or built using code-level customization. Runbooks can be triggered manually or automatically.
  • Action. An operation that pushes, pulls, and puts data leveraging Transposit's library of integration APIs. For example, actions can start an automated process, reboot a server, ask a question, or change a runbook's state.
  • Event. Anything that exists on an activity's timeline is logged as an event. A customer reports the failure of a system, an external alerting system is notified, sending an alert, causing an incident to be created in Transposit so that one or more runbooks are started, a Slack channel is created, team members join the conversation, a graph is generated, ending with a postmortem document... each of these are events along the timeline.
  • Webhook. A call into Transposit enabling activities to be created or closed, runbooks to be started, data to be changed, triggering events to happen in Transposit.
  • Connector. An extension to the Transposit platform's functionality. For example, a runbook can contain a button that is pressed to reboot a server, with the connector being the conduit that enables Transposit to connect to the services enabling the server to be rebooted.

To understand how these terms fit in a Transposit environment, see Configuring Transposit.

Further Reading#