Wait For Condition activity
Summarize
Summary of Wait For Condition activity
The Wait For Condition activity in ServiceNow Playbooks allows you to pause the playbook execution until a specified record meets defined field value conditions. This helps ensure that subsequent playbook actions only proceed when certain criteria are satisfied, enabling more controlled and conditional automation.
Show less
Key Features
- Role and availability: This common activity is available to users with admin, playbook.admin, or pdauthor roles.
- Configurable inputs: You can set a label and description for clarity, define run conditions using prior activity data, and select start rules for both stages and activities to control when the wait begins.
- Start with delay: Optionally delay the start of the activity or stage by a specified duration.
- Record targeting: Specify the record to monitor by providing a reference and the relevant table.
- Condition criteria: Define the exact field values or conditions the record must meet for the playbook to continue.
- Timeout handling: Optionally configure a timeout to skip the activity if the conditions are not met within a set duration, including schedule and duration inputs for precise timing control.
Practical Use for ServiceNow Customers
This activity is useful when your playbook needs to wait for external changes or updates to a record before proceeding. For example, waiting for approval status changes or updates from another process. It provides precise control over playbook flow by pausing execution until the business conditions you define are met, preventing premature or incorrect processing.
You configure it through the activity properties panel, leveraging condition builders and reference fields to connect to the right records and conditions. Timeout options prevent indefinite waiting, allowing your playbook to handle cases where conditions are unmet gracefully.
What to Expect
- The playbook pauses at this activity until the specified record fields match your criteria.
- If enabled, the activity can time out and skip itself after a defined wait period.
- This activity does not produce outputs but controls the flow by gating subsequent playbook steps.
Pause the playbook until a record has field values that match a set of conditions.
Roles and availability
- This activity is available as a common activity. Users with the admin, playbook.admin, or pd_author can add this activity to a playbook.
Inputs
| Input | Type | Description |
|---|---|---|
| Label | String | Title to display as activity and playbook card. |
| Description | String | Information to display about activity usage or outcome. |
| Run condition | Condition Builder | Conditions that must be met to run an activity or stage. You can use data from prior activities to build conditions. Note: Show additional options to see this field. |
| Start Rule | Choice | Under , select a start rule for when your stage should start running:
|
| Start with delay | True/False | Option to wait for a duration of time before running an activity or stage. When enabled, this input displays the Start with delay input properties. Note: Show additional options to see this field. |
| Record | Reference | Reference to the record that pauses the playbook until conditions match. |
| Table | Table Name | Table containing the record to update. |
| Conditions | Template Value | Criteria that a record must meet for the playbook to continue. |
Advanced inputs
| Input | Type | Description |
|---|---|---|
| Enable timeout | Choice | Option to time out the Wait for Condition activity if the conditions aren't met after a specified Duration. |
| Duration | Date/Time | Amount of time to wait before the activity times out and its state is set to Skipped. This input requires setting the Enable timeout input. |
| Schedule | Choice | Schedule used to compute duration values. This input requires setting the Enable timeout input. |
Outputs
The Wait for Condition activity has no outputs.