Introducing workflows

Workflows allow you to automate certain actions and behaviours based on specific triggers. For example, incident.io can automatically invite users or user groups to a particular Slack channel when a specific custom field is set on an incident.

A diagram of an example workflow: the trigger to start the workflow is "Incident created or changed"; the trigger condition is the custom field "Incident Type" is "Data Breach"; and the steps to run are "Invite @legal-team to the incident Slack channel" followed by "Start the 'Data Breach' decision flow".

Parts of a Workflow

Triggers: what should cause the workflow to run

Think of a trigger as something that happens to set off a chain of events. You can choose from the following pre-defined triggers:

• an incident is created or changed
• someone joins an incident channel
• someone posts a message in an incident channel

Conditions: which incidents or users this workflow should run for

Conditions are a set of criteria which control when the workflow should actually run. If you don't set any conditions, the workflow will apply to all incidents/users.

For example, if you choose the "someone posts a message in an incident channel" trigger, and don't add any conditions, the workflow will run for every new message posted in the incident channel.

Depending on the workflow trigger, you can choose from a number of fields such as:

• incident severity
• incident role
• incident status