---
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


---

# Call a workflow flow logic

# Call a workflow flow logic {#ariaid-title1}

* Release version: Australia
* 
* Updated March 12, 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 Call a Workflow Flow Logic

This feature allows you to execute a published and active workflow from within your flow, using flow data as input.
You can specify the current record as a workflow input, enabling seamless integration between flows and workflows.
Show full answer Show less  

## Key Features

* **Select a Workflow:** Choose from published and active workflows, determining the associated records. Inputs from the workflow are displayed as additional flow inputs.
* **Wait?** Option: Set to true to pause the flow until the workflow completes, allowing for the return of output values. If set to false, the flow continues independently.
* **Current:** Allows you to select a data pill representing the current record processed by the workflow.
* **Outputs:** The flow execution details provide workflow output values generated during execution, contingent on the wait setting.
* **State Tracking:** Outputs include the workflow state (Complete, Canceled, Invalid), context reference, result string, and return value from the workflow context record.

## Key Outcomes

By utilizing this flow logic, ServiceNow customers can effectively manage workflow executions within flows, enabling better control and visibility of workflow progress and results. It allows for enhanced automation and decision-making based on the workflow's outputs, ultimately improving operational efficiency.  
Run a published and active workflow from your flow. You can use the flow data as a workflow input. For example, you can specify the current record as a workflow input.

## Inputs {#flow-logic-call-workflow__section_tbt_tqn_p2b}

{#flow-logic-call-workflow__table_pft_qpn_p2b__entry__2}

| Input | Description |
|-|-|
| Select a Workflow | Published and active workflow that you can select to run. The workflow that you select determines the records that are associated with it. If the workflow has inputs, Workflow Studio displays them as additional flow inputs. Note: * To prevent the workflow from running outside of Workflow Studio, modify it to remove its start conditions. * You cannot select a workflow that runs on the Requested Item table. Instead, create a new flow with a Service Catalog trigger. {#flow-logic-call-workflow__ul_m2c_hxf_2sb} |
| Wait? | Workflow that you set to true so that the flow waits for workflow completion before continuing. Only workflows that wait for completion can return certain output values to the flow. Set to false to continue running the flow separately from the workflow. Note: If the workflow is canceled or its context record is deleted prior to the workflow finishing, the flow stops waiting and instead continues running. |
| Current | Current record that the workflow processes. Select a data pill that contains a record from the associated workflow table. |
[ ]

{#flow-logic-call-workflow__table_pft_qpn_p2b}

## Outputs {#flow-logic-call-workflow__section_o51_tqn_p2b}

The flow execution details only display workflow output values that are generated while the
flow is running. If you configure the flow to wait for the workflow to finish, the flow
execution details can display all workflow output values. If the flow does not wait, the flow
execution details only display the workflow output values that were generated before the
Call a Workflow flow logic completes. If Call a Workflow completes before the workflow finishes, the workflow output values stop
updating and only display the last known value.
{#flow-logic-call-workflow__table_c25_yqn_p2b__entry__2}

| Output | Description |
|-|-|
| State | State of the workflow. This value comes from the workflow context record. The state will be Complete if the workflow executes successfully. If the workflow is canceled, the workflow state is set to Canceled. If the context record is deleted prior to the workflow finishing, the workflow state is set to Invalid. |
| Context | Reference to the workflow context record. |
| Result | String that contains the result from the workflow. This value comes from the workflow context record. |
| Return value | String that contains the return_value from the workflow. This value comes from the workflow context record. |
[ ]

{#flow-logic-call-workflow__table_c25_yqn_p2b}  

## Calling the Routine Change workflow

In this example, the flow calls the
Routine Change workflow. The Wait? option is
checked, so the flow pauses until this workflow completes. The Current
field is filled using a data pill representing the record that triggered this flow.

## Execution details {#flow-logic-call-workflow__section_e5q_pjp_s2b}

Figure 1. Call Workflow execution details  
1. The header displays a link so that you can view the workflow progress in the Workflow Editor, the flow logic state, the start time, and the runtime duration.
2. The Workflow Configuration section displays how the flow logic was configured for this flow and the runtime values that were generated.
3. The Workflow Output section displays the output that is generated by the workflow while the flow is running.
{#flow-logic-call-workflow__ol_wtt_scs_r2b}  
Note:  
If you cancel the workflow or delete the context record prior to the workflow finishing, the flow logic state is set to Complete.
**Related concepts**   

* [Assign subflow outputs flow logic](https://servicenow-prod.fluidtopics.net/Vi2xufmkKFPMynJkLOlALA "Specify the data the subflow returns when it completes running. Use subflow output as data for a parent flow or as input for another process.")
* [Do the following until flow logic](https://servicenow-prod.fluidtopics.net/QAQc64OsyoACdx7Me3riLA "Apply one or more actions repeatedly until an end condition is met. You can use the flow data to specify the end conditions.")
* [Do the following in parallel flow logic](https://servicenow-prod.fluidtopics.net/eILn02zBZvbi3Tn7n7lqLA "Run actions and subflows in separate paths within an isolated flow logic block.")
* [Dynamic flows flow logic](https://servicenow-prod.fluidtopics.net/9CA7wcyPkP1MnkHwcFtX5Q "Identify and run a flow or subflow dynamically by using runtime data. Build templates to provide expected inputs for dynamically called flows or subflows.")
* [End Flow flow logic](https://servicenow-prod.fluidtopics.net/NAyoEtyTqpGliQlDlcqNCg "Stop running the current flow. Use End Flow within a branch of the flow to specify an exit condition. For example, end the flow when it reaches a specific If flow logic block.")
* [For Each flow logic](https://servicenow-prod.fluidtopics.net/m2Jd4tAy1wj9Vfu6zJIqGQ "Apply one or more actions to each record in a list of records.")
* [If flow logic](https://servicenow-prod.fluidtopics.net/nR06QTqfpGjIp8_whZe0CQ "Selectively apply one or more actions only when a list of conditions is met.")
* [Make a decision flow logic](https://servicenow-prod.fluidtopics.net/kj1wegOGweMm50e~aPx~aA "You can use the decision table branching logic in situations where multiple conditional paths are required, as an alternative to nested If, Else If, or Else flow logic. For example, if you want to determine what kind of car insurance you need, you can add inputs such as your age, accident history, and car model to the decision table to determine a level of insurance coverage. This logic can save you time and present a more readable format than nested if conditions or switch case statements.")
* [Set Flow Variables flow logic](https://servicenow-prod.fluidtopics.net/taLpFCTeLjMl12m~qAkCGw "Assign a value to one or more flow variables, which store flow data as data pills. Access flow variable values by referring to their data pill.")
* [Try flow logic](https://servicenow-prod.fluidtopics.net/2anCAJO7Iy6D_v~Y9CMVeg "Allow a flow to continue running when an error occurs within a flow logic block. Run a sequence of actions in response to errors within the flow logic block.")
* [Wait for a duration flow logic](https://servicenow-prod.fluidtopics.net/jta33j7A9dgcVulpsFKEdg "Use this flow logic to give your users time to act during automated processes or to wait for a specific date and time to complete actions.")  
**Related reference**   

* [Append to Flow Variables flow logic](https://servicenow-prod.fluidtopics.net/QdizsC8_AAj6fxqxNs3ynQ "Append a value to one or more array of objects flow variables. Use flow data to generate values.")
* [Exit Loop flow logic](https://servicenow-prod.fluidtopics.net/wNRkIzhET_BU_tHJZo0sww "Exit from a flow logic loop when the conditions of an If flow logic are met. Continue running the flow from the next step after the flow logic loop. This flow logic is also known as break.")
* [Get Flow Outputs flow logic](https://servicenow-prod.fluidtopics.net/vKzFDepPhnY3B2SF7MnreA "Retrieve output values generated by dynamic flows or subflows.")
* [Go back to flow logic](https://servicenow-prod.fluidtopics.net/ZBe0On6wxNGHSUgBMlBOTA "Return to a prior step in the flow to repeat a sequence of actions.")
* [Skip Iteration flow logic](https://servicenow-prod.fluidtopics.net/hAlsZiuAyM0sbpeo32QQ4w "Skip the current iteration of a flow logic loop when the conditions of an If flow logic are met. Continue running the flow logic loop with the next item in the list. This flow logic is also known as continue.")

