Conditional step requirements

Published

August 28, 2026

Configure conditional requirements on certain workflow step types.

Prerequisites

Configure conditional requirements

Conditional requirements are required or optional for the following step types:3

Inventory Record Stage Change optional

  1. Under When These Conditions Are Met, set your AND and OR conditions.

  2. Add a single independent rule or a linked condition group. These rules and groups can be nested if desired:

    • Click Add Rule to add an independent rule.
    • Click Add Group to add a linked group of rules that all must be true to qualify.

Inventory Record Type Change optional

  1. Under When These Conditions Are Met, set your AND and OR conditions.

  2. Add a single independent rule or a linked condition group. These rules and groups can be nested if desired:

    • Click Add Rule to add an independent rule.
    • Click Add Group to add a linked group of rules that all must be true to qualify.

Artifact Status Change

  1. Under When These Conditions Are Met, set your AND and OR conditions.

  2. Add a single independent rule or a linked condition group. These rules and groups can be nested if desired:

    • Click Add Rule to add an independent rule.
    • Click Add Group to add a linked group of rules that all must be true to qualify.

User Action optional

  1. Under Display Action Button When, set your AND and OR conditions.

  2. Add a single independent rule or a linked condition group. These rules and groups can be nested if desired:

    • Click Add Rule to add an independent rule.
    • Click Add Group to add a linked group of rules that all must be true to qualify.

  • Select any Requested Fields4 to be entered by users during the action.

    Toggle Optional to ON if the field should be optional and not required.

  • (Optional) Create conditional requirement groups so fields appear and become required only when certain conditions are met:

    1. Click ⋮ on the step menu and select Add Conditional Group.

    2. In the dashed Conditional Display Group container that appears, click Edit Conditions and configure when this group should apply:

      • Use the same AND / OR rule builder available elsewhere in workflows
      • Conditions are evaluated against record or artifact field values

    3. Drag requested fields into the group container to make them conditionally required. A field placed in a group has its required/optional switch locked — inside a group, requiredness is decided by the group’s condition. When the rule matches, these fields will appear in the form with a caption explaining why, and they become required. When the rule does not match, the fields remain hidden and a note appears: “[N] fields don’t apply to your answers. Anything you entered is kept.”

    4. At runtime, as users answer questions on the form, fields in conditional groups appear and disappear based on their answers. Required fields are enforced only while their group’s condition is active — the form tells users what is still needed before they can submit.

    Note: Each workflow’s audit trail records when a user’s answers cause a conditional group to become active, providing visibility into what drove a particular set of field requirements.

  • (Optional) Present these requested fields to users in steps:

    1. Click Add Step to add a step.
    2. On the Add Step modal that appears, enter the step Title and provide an optional Description.
    3. Click Save to insert the step.
    4. Drag request fields into a step to add them to that step.

  1. Toggle Enable deadline on to configure a User Action Deadline for when users should complete this action by.

  2. Then, under End Action, select the type of deadline:

    • After Time Interval — Set the Amount and Unit of the deadline.
    • At Specified Date — Set the date and time the action should Wait Until.
    • At Specified Date on Custom Field — Select a date, date time, or calculated Record Field that defines the deadline.
    • Time Delta from Specified Date on Custom Field — Select a date, date time, or calculated Record Field to calculate a deadline from, then set a Time Delta Direction and Wait Duration.

Approval required

  1. Under Approval Group, click Add Individual Approver to set an individual approver selected from User Roles,5 Inventory Record Stakeholder Types,6 or Inventory Record Fields — User:7

    • Click Add Rule to add an individual rule.
    • Click Add Group to add a group of rules.

    One approver per rule or rule group must provide approval. If you’ve set multiple rules or rule groups, select whether they are AND or OR conditions.

  2. (Optional) Add more individual rule or rule group approvers as required.

    If you’ve set multiple individual approvers, select whether they are AND or OR conditions.

  3. Select the Fields to Review shown to your Approval Groups as read-only fields.

Broadcast required

Select from either Inventory Record Stakeholder Types8 or User Roles.9

Condition Branch required

  1. Under each branch’s Conditions, set your AND and OR conditions.

  2. Add a single independent rule or a linked condition group. These rules and groups can be nested if desired:

    • Click Add Rule to add an independent rule.
    • Click Add Group to add a linked group of rules that all must be true to qualify.

Wait required

Select when you would like to Resume Workflow:

Set the Wait Duration in minutes, hours, or days.

Set a time to Wait Until as defined by a specific timestamp.

Set the Record Field10 with a valid Date or Date Time type record field that defines the specific timestamp on a per record basis.

  1. Set the Record Field11 to a valid Date or Date Time type record field that defines the specific timestamp on a per record basis.

  2. Select a Time Delta Direction relative to your selected field.

  3. Enter a Wait Duration in minutes, hours, days, or months for the delta.

HTTP Request optional

  • Enter a request timeout in seconds under Timeout (seconds).

  • Max 300 seconds, or enter 0 to disable timeout.

Toggle the following request options on or off:

  • Fail on Non-2xx — Whether or not the request will be considered failed if the response status code is not in the 2xx range.

  • Allow Invalid Certificates — Whether or not the request will be allowed to use invalid certificates.

  • Follow Redirects — Whether or not the request will follow redirects.

  • Require HTTPS — Whether or not the request will require HTTPS.

  • Save Response to Context — Store the response so downstream nodes can reference it.

Enter optional headers to include with your request:

  1. Click Add Header under Headers to enter a header.

  2. Provide a Header Name and Header Value.

To avoid storing credentials in plaintext, use {secret:name} syntax to reference a webhook secret.12