Skip to main content

Workflows

Learn how to use Workflows to automate actions across Issues, Tasks, Risks, Steps, and Parts by configuring triggers, conditions, and actions directly from Settings.

Updated yesterday

Workflows allow you to automate repetitive actions across your organization by defining rules that trigger automatically when specific events occur.

For example, you can automatically create an issue when a procedure step fails, generate a purchase request when part inventory drops below a threshold, or spin up a task whenever a new risk is logged.

Each workflow is made up of three components:

  • A Trigger that defines what event starts the workflow

  • Optional Conditions that narrow when it should run

  • An Action that executes automatically

All configuration is done directly in the UI with no code required. This reduces manual overhead, ensures nothing falls through the cracks, and keeps your team focused on execution instead of administrative follow-up.


Accessing Workflows

To configure workflows, navigate to:

Settings > Workflows

The Workflows page displays all existing rules in a table view, including:

  • Workflow Name

  • Status

  • Action (play/pause control)

  • Executions (how many times it has run)

  • Last Triggered

  • Additional options via the three-dot menu

You can sort the table by Workflow Name, Executions, or Last Triggered using the column headers.

The top toolbar also includes:

  • Search to quickly locate a workflow by name

  • Filters to filter by status (Active, Inactive, Archived)

  • Add to create a new workflow

  • Bulk actions (Run, Pause, Archive) when selecting one or more workflows

  • A three-dot menu to Export Table as CSV


Creating a Workflow

Click Add in the upper right corner to open the workflow builder.

At the top of the modal, enter a Workflow Name and optional Description to clearly define its purpose.

The builder is structured into three sections:

  1. Trigger

  2. Condition (optional)

  3. Action


Step 1: Configure the Trigger

The Trigger defines what entity and which event will start the workflow.

Select Entity (What)

Choose one of the following entities:

  • Issue

  • Task

  • Risk

  • Step

  • Part

Once selected, the available events will dynamically update based on the entity.

Select Event (When)

The event options vary by entity:

Issue

  • Created

  • Status Changed

Task

  • Created

  • Status Changed

Risk

  • Created

  • Status Changed

Step

  • Step Passed

  • Step Failed

Part

  • Created

  • Low Inventory

For example:

  • Selecting Step enables Step Passed and Step Failed.

  • Selecting Part enables Created and Low Inventory.

This dynamic behavior ensures you only see relevant automation triggers for the selected object type.


Step 2: Add Conditions (Optional)

Conditions allow you to narrow when the workflow runs. If no conditions are set, the rule will always run when the trigger event occurs.

Condition options depend on the selected entity.

Issue, Task, Risk

You can filter by:

  • Project

This allows workflows to apply only within specific projects.

Step

You can filter by:

  • Project

  • Procedure Name

    • Contains (Value)

    • Does Not Contain (Value)

This is particularly useful for targeting only certain procedures without duplicating rules.

Part

You can filter by:

  • Procurement Type

    • Make

    • Buy

    • Make or Buy

For example, you may only want to generate purchase requests for parts marked as Buy when inventory drops below a threshold.


Step 3: Define the Action

The Action determines what the workflow will automatically create or execute when triggered.

Available actions depend on the entity and event selected.

Issue

  • Issue Created

    • Create Risk

    • Create Task

  • Issue Status Changed

    • Create Risk

    • Create Task

Task

  • Task Created

    • Create Issue

    • Create Risk

  • Task Status Changed

    • Create Issue

Risk

  • Risk Created

    • Create Issue

    • Create Task

  • Risk Status Changed

    • Create Task

Step

  • Step Failed

    • Create Issue

    • Create Risk

  • Step Passed

    • Create Issue

    • Create Risk

Part

  • Part Created

    • Create Task

  • Part Low Inventory

    • Create Purchase Request

    • Create Work Order

Select the appropriate Action Type from the dropdown to complete configuration.

Once configured, click Save Workflow.

NOTE: You are not currently able to set more than one action type, or more than one condition on a workflow. You will need to create separate workflows for each.


Managing Workflows

After saving, the workflow appears in the Workflows table.

Workflow Status

Each workflow has a Status indicator:

  • Running

  • Paused

You can toggle execution directly from the Action column by clicking the play or pause icon.

A confirmation message appears when a rule is activated or deactivated.

When paused, the workflow will not trigger even when the event and conditions are met.


Executions and Monitoring

The table displays:

  • Executions: Total number of times the workflow has run

  • Last Triggered: The most recent execution time

This provides quick visibility into how active and effective your automation rules are.


Editing or Archiving

Click the three-dot menu at the end of a workflow row to:

  • Edit

  • Archive

Archived workflows can be filtered using the Filters control.


Bulk Actions

Select one or more workflows using the checkboxes on the left to enable bulk controls:

  • Run

  • Pause

  • Archive

This is useful for pausing multiple rules during maintenance or activating several at once.


Filtering and Searching

Use the Search bar to locate workflows by name.

Click Filters to filter by status:

  • Active

  • Inactive

  • Archived

This is especially helpful as your automation library grows.


Exporting Workflows

From the three-dot menu in the upper-right corner of the table, select:

Export Table as CSV

This allows you to export the entire workflow table for reporting, audits, or documentation purposes.


Best Practices

  • Start with a clear name that describes both the trigger and action (for example, “Step Failed – Create Issue”).

  • Use conditions to avoid over-triggering workflows across unrelated projects.

  • Periodically review Executions and Last Triggered to confirm rules are behaving as expected.

  • Archive unused workflows instead of deleting them to preserve history.

Workflows provide a flexible, no-code automation framework that scales with your organization. By thoughtfully combining triggers, conditions, and actions, you can eliminate repetitive coordination tasks and ensure critical follow-ups happen automatically and consistently.

Did this answer your question?