Runbook & action triggers

Transposit runbooks have two types of triggers: Runbook and action triggers. Runbook triggers are a set of conditions that when fulfilled trigger a run of a runbook, including any action triggers that are set to run. Let's break down your trigger options!

Action triggers#

There are two types of action triggers. Use action triggers to specify conditions for automatically running an action.

On runbook start#

An action with the "on runbook start" condition will run when the runbook is manually or automatically triggered.

On action completed#

An action with the "on action completed" condition will run when the selected action in the same runbook completes.

Runbook triggers#

There are three types of runbook triggers. Use runbook triggers to specify conditions for automatically running a runbook.

Activity creation#

Like the name implies, these runbook triggers run any time an activity is created in Transposit. There are a few additional conditions you can set:

Activity type:
If set, the runbook will trigger if the activity type (Incident or Task) matches.

Severity:
If set, the runbook will trigger if one or more severity levels match (SEV0, SEV1, SEV2, SEV3, SEV4, SEV5)

Originating webhook:
If set, the runbook will trigger if it originated from the specified incoming webhook.

Custom output params:
If set, the runbook will trigger if the comparison made against a field in customOutputParams from the data parser is true. You must set a field (path within the JSON object), select a comparator (=, !=, >, >=, <, <=, or contains), and set a value to compare against. See Data parsers getting started for more info.

Activity update#

Like the name implies, these runbook triggers run any time an activity is updated in Transposit. There are a few additional conditions you can set:

Old or new activity type:
If set, the runbook will trigger if the old or new activity type matches.

Old or new severity:
If set, the runbook will trigger if any of the one or more old or new severity levels match (SEV0, SEV1, SEV2, SEV3, SEV4, SEV5)

Note: Each of these condition types will only match if the relevant activity trait changed in the update we’re looking at.

For example, if you have these conditions set:

  • Old activity type = Task
  • New activity type = Incident
  • Old severity = SEV0

The trigger won’t fire if a SEV0 Task changes to be an Incident - the severity didn’t change, so the condition on old severity won’t be met.

Webhook#

Like the name implies, these runbook triggers run any time the selected webhook fires:

Custom output params:
If set, the runbook will trigger if the comparison made against a field in customOutputParams from the data parser is true. You must set a field (path within the JSON object), select a comparator (=, !=, >, >=, <, <=, or contains), and set a value to compare against. See Data parsers getting started for more info.

If you need help with accessing the right information in the customOutputParams field, we'd be happy to help you at support@transposit.com. Most external services document their respective webhooks, but we understand it can be tricky to wade through this data.