Jeli workflows are automated processes that rely on a defined scope, frequency, and action. The scope determines when the workflow triggers, based on specific conditions and events, while the frequency controls how often the workflow runs. The action is the core task that the workflow automates, ensuring efficient and consistent handling of incidents.

📘

Availability

• Jeli workflows are only available on the Jeli Standalone (Legacy) pricing plan. This feature does not come standard with the Enterprise for Incident Management pricing plan.
• At this time, Jeli is not available for accounts in the EU service region (i.e., https://subdomain.eu.pagerduty.com/).

🚧

Required User Permissions

Admin permissions are required to manage Jeli workflows.

Create a Jeli Workflow

1. In the Jeli web app, select Workflows in the left pane and click Create Workflow.
2. Enter the following information:

3. Click Create.

Filter Workflows

You can limit the number of workflows in your view by applying a filter. Enter a search term or click Add Filter. You can filter by the following attributes:

• workflow name
• workflow trigger type
• workflow active state

Change Slack Workspaces

Jeli workflows are scoped to a Slack workspace, which enables you to take action in Slack channels outside of the primary incident channel. Use the Slack workspace dropdown to adjust which workspace your workflows can access. When you change the selection, the UI updates to only show workflows for that workspace.

Duplicate a Workflow

1. In the Jeli web app, navigate to Workflows in the left pane and select the workflow you would like to duplicate.
2. On the details page of the workflow, click Duplicate.

3. Make your desired changes and click Update.

Update a Jeli Workflow

1. In the Jeli web app, select Workflows in the left pane.
2. Select your desired workflow to view its details page and click Edit.

3. Make your required changes to the workflow and click Update.

Deactivate a Jeli Workflow

1. In the Jeli web app, select Workflows.
2. On your preferred workflow, click the toggle to deactivate it.

Delete a Jeli Workflow

1. In the Jeli web app, select Workflows in the left pane and click Create Workflow.
2. Select your desired workflow to view its details page and click Delete.

3. In the confirmation modal, click OK.

❗️

Permanent Action

This action is permanent and cannot be undone.

Core Concepts

A workflow consists of three components:

• Scope: The scope of the workflow includes the trigger for what initiates the workflow and additional conditions that the trigger must meet.
• Frequency: The frequency of the workflow defaults to once per incident but can also be set to occur every time the conditions and/or trigger for the workflow are met.
• Actions: Actions are the most substantial part of the workflow; the tasks that the workflow automates.

Scope

Scope controls when a workflow executes and is made up of triggers and conditions.

Trigger

Triggers are events in the system. For example, Incident Opened fires when someone opens a new Jeli incident, whether from the Jeli Slackbot or from the API.

Conditions

Conditions consist of an incident dimension and a conditional operator. Incident dimensions refer to the various fields on a Jeli incident. These fields can be compared using a conditional operator to determine whether a workflow runs.

📘

Tip

Each dimension can only be used once per workflow. Conditions are not required to create a workflow, but multiple dimensions per workflow are supported.

Operators

Available operators may vary based on the selected dimension.

• is / is not
  • Check if the given dimension is equal or not equal to one of the selected values. Example: Severity is 0. The workflow runs when the severity is set to 0.
• is set / is not set
  • Check if the dimension exists on the incident or not. Example: Communications Lead is not set. The workflow runs if the Communications Lead role has not been set.
• includes / does not include
  • Check if the dimension includes the provided substring. Matching ignores case. Example: Incident name includes down. The workflow runs if the incident name includes the word down.

Frequency

Frequency lets you configure how often you want the workflow to run. There are two options:

• Once per incident
• Every match, which means every time the scope is met

Once Per Incident

Use this frequency with the triggers Incident Opened and Incident Closed.

Examples:

• Name: Sev 0 Creation email notification
• Trigger: Incident Opened
• Conditions: Severity is 0
• Frequency: run once per Incident
• Action: Send email to [email protected]

Every Match

Runs every time the scope is met (trigger and conditions). Use this frequency with the triggers Severity Change and Stage Changed.

Examples:

• Name: Update Support on Incident Stage
• Trigger: Stage Changed
• Conditions: Type is Customer Facing, Severity is 0
• Frequency: every time scope is met
• Action: Send message to a channel #support-oncall

Actions

Actions run when the scope of a workflow is met. There is no limit on duplicate actions; you can send a different message to different users from the same workflow. You need to supply additional information to each action, such as an email address and a message for the Send email action.

📘

Important

A workflow must have at least one action before you can enable it.

Types of Actions

FAQ

How do Jeli workflows work?

Workflows are evaluated concurrently based on the trigger. Conditions are evaluated one at a time for a given workflow, halting if any evaluate false. Conditions are chained together with an AND operator. Actions for a given workflow are executed serially and do not halt if one fails. Some actions may send a message to the incident channel to notify responders that an automated action has been taken.

Are there any limitations with Jeli workflows?

Workflows currently have the following limitations:

• There are certain situations when an action may not run. For example, sending a message to a role that is not currently assigned. You can use conditions to add an appropriate scope to the workflow and ensure the role is assigned.
• Workflows currently run after most other automatic steps.