---
sourceDocument: Australia Build workflows
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/build-workflows

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia Build workflows

ft:clusterId :

    - crworkflow

bundleId :

    - crworkflow

workflow :

    - Creator


---

# Invoke PaCE activity

# Invoke PaCE activity {#ariaid-title1}

* Release version: Australia
* 
* Updated March 12, 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read

Enable the Policy as Code Engine (PaCE) activity in Playbooks to develop playbook processes.

## Roles and availability {#invoke-pace-policies__section-subscription-roles}

These activities are available as part of the application that is automatically bundled with PaCE. Users with the admin, pd_admin, pd_author, or pd_content_author can add these activities to a playbook.

## Inputs {#invoke-pace-policies__section-inputs}

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).{#invoke-pace-policies__inputs-description}
{#invoke-pace-policies__table_qmc_knm_sbc__entry__3}

| Name | 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. You can use data from prior activities to build conditions. |
| When to start | Choice | Select a start rule for when your activity should start running: * Immediately: Your activity starts running as soon as its stage starts running. Your stage starts running when your playbook is triggered. * Before previous: Your activity starts before specified activities have finished running. * After previous: Your activity starts running after specified activities have finished running. {#invoke-pace-policies__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://servicenow-prod.fluidtopics.net/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."). |
| Service | String | The calling service that is invoking the PaCE API. |
| Category | String | The category type. |
| Policy tag | String | Tag name of the policy. |
| Document Ids | Array.Object | Name of document IDs. |
| Data | JSON | The policy-specific data that includes all possible caller inputs. |
| Options | Object | Options of the policy. |
[ ]

{#invoke-pace-policies__table_qmc_knm_sbc}

## Outputs {#invoke-pace-policies__section-outputs}

The outputs are configurable in Flow Designer and are set by the Automation plan.{#invoke-pace-policies__table_hsz_vvm_sbc__entry__2}

| Label | Type |
|-|-|
| Root execution id | Sys ID (GUID) |
| Don't Treat as Error | True/False |
| Response | JSON |
| Action Status | String |
[ ]

{#invoke-pace-policies__table_hsz_vvm_sbc}