---
sourceDocument: Australia Build workflows
sourceDocumentLink: https://www.servicenow.com/docs/r/australia/build-workflows

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia Build workflows

ft:clusterId :

    - crworkflow

bundleId :

    - crworkflow

workflow :

    - Creator


---

# Ask for Ad Hoc Approval activity

# Ask for Ad Hoc Approval activity {#ariaid-title1}

Release version: Australia  
Updated November 2, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read
Summarize  
![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI  
This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.  

## Summary of Ask for Ad Hoc Approval activity

The Ask for Ad Hoc Approval activity allows agents and fulfillers to specify which users must complete approval requests dynamically during a playbook run in ServiceNow.
This capability enhances control over the approval process within playbooks by enabling targeted, flexible approvals.
Show full answer Show less  
Only users with the **playbook.admin** or **pdauthor** roles can add this activity to a playbook.

## Configuration Inputs

When configuring the activity, you define several key inputs to control its behavior and appearance:

* **Label:** The title displayed on the activity card.
* **Description:** Information about the activity's purpose or outcome.
* **Run condition:** Logical conditions that determine when the activity or stage runs, which can reference data from prior activities.
* **Start Rule:** Defines when the stage or activity begins, such as immediately when triggered, after specific stages, or after specific activities.
* **Start with delay:** Optionally delays the start of the activity or stage by a specified duration.
* **Display order:** Controls the sequence in which the activity appears during runtime.

Advanced options are available to refine these inputs further by selecting "Show additional options."

## Automation Inputs

These inputs specify whom the approval requests are sent to and the context of the approval:

* **Approver:** Individual user(s) who receive the approval request.
* **Approver group:** User group that receives the approval request.
* **Table:** The table from which the associated record for approval is selected.
* **Record:** The specific record that the approval request concerns.

## Outputs

The activity generates output data that can be used by other playbook activities, including:

* **Created date:** The date the approval request was created.
* **Approval Record:** The record representing the approval request.
* **Approval State:** The current state of the approval request.

## Practical Benefits for ServiceNow Customers

This activity streamlines the approval process within playbooks by allowing dynamic selection of approvers and flexible scheduling. It supports complex workflows by enabling conditions and delays, ensuring approvals happen in the right sequence and context. The outputs facilitate tracking and integration with subsequent playbook activities, improving overall process automation and visibility.  
Enable agents and fulfillers to specify which users must complete approval requests during a playbook run.

## Roles and availability {#request-adhoc-approval-activity__section_p41_34j_35b}

Users with the playbook.admin or pd_author role can add these activities to a playbook.

## Inputs {#request-adhoc-approval-activity__section_r2m_k4j_35b}

Open the activity properties panel and configure your activity to add values for the following inputs. If the input value varies, use the pill-picker to show where to get the value. To learn more about the pill-picker, see [Dot-walking examples](https://www.servicenow.com/docs/access?context=dot-walking-examples&version=australia&pubname=australia-platform-user-interface&ft:locale=en-US).  
Note:  
After configuring the required inputs for your activity, you can also choose to configure additional inputs. In the side panel, select Show additional options to display these advanced inputs. For more information, see [Activity experience](https://www.servicenow.com/docs/aEvbv54ObgcCjjhXabvx8w#activity-definitions__activity-experience).
{#request-adhoc-approval-activity__table_asm_m4j_35b__entry__3}

| 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: Select Show additional options to see this field. |
| Start Rule | Choice | Under ScheduleStart Rule, select a start rule for when your stage should start running: * When process starts: Your stage starts running as soon as the playbook starts. * After specific stages: Your stage starts running after specified stage(s) have finished running. {#request-adhoc-approval-activity__ul_f4z_nq1_ppb}Under Schedule \> Start Rule, select a start rule for when your activity should start running: <!-- --> * When stage starts: Your activity starts running as soon as its stage starts running. Your stage starts running when your playbook is triggered. * After specific activities: Your activity starts running after specified activities have finished running. {#request-adhoc-approval-activity__ul_zzc_3ls_m1c} |
| 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](https://www.servicenow.com/docs/EdInaaLAHZCnrBcJbs96Lw "Specify a duration of time to wait before running an activity or a stage whose start rule and conditions have been met. Give users time to act during automated playbooks. Give users time to wait for a specific date and time to complete actions."). Note: Select Show additional options to see this field. |
| Display order | Number | Defines the order in which this activity will appear during runtime. Note: Select Show additional options to see this field. |
[ ]

{#request-adhoc-approval-activity__table_asm_m4j_35b}

## Automation inputs {#request-adhoc-approval-activity__section_bjc_mbr_clc}

Open the Automation tab to add values for the following inputs.
{#request-adhoc-approval-activity__table_okq_jcr_clc__entry__3}

|   |   |   |
|-|-|-|
| Approver | Choice | Individual users that will receive approval requests. |
| Approver group | Choice | User Group that will receive approval requests. |
| Table | Choice | Table that you want to choose the associated record from. |
| Record | Choice | Associated record for the approval requests. |
[ ]

{#request-adhoc-approval-activity__table_okq_jcr_clc}

## Outputs {#request-adhoc-approval-activity__section_lsz_31k_35b}

These outputs can provide data to other activities in your playbook. You can access this data as activity inputs when you configure your activity:{#request-adhoc-approval-activity__table_gjv_msj_clc__entry__3}

| Output | Type | Description |
|-|-|-|
| Flow Data Created date | String | Create date of your approval request. |
| Approval Record | String | Record of your approval request. |
| Approval State | String | State of your approval request. |
[ ]

{#request-adhoc-approval-activity__table_gjv_msj_clc}

*[\>]: and then