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

 Release :

    - brazil

ft:locale :

    - en-US

ft:publication_title :

    - Brazil Build workflows

ft:clusterId :

    - crworkflow

bundleId :

    - crworkflow

workflow :

    - Creator


---

# Get Catalog Variables action

# Get Catalog Variables action {#ariaid-title1}

Release version: Brazil  
Updated September 10, 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 Get Catalog Variables action

The Get Catalog Variables action, available in Workflow Studio as a core ServiceNow action, enables you to retrieve values from catalog variables associated with requested items in the Service Catalog.
This action supports selecting variables from multiple template catalog items and variable sets within a flow.
Show full answer Show less  
This action is designed for users with the **flowdesigner** or **admin** roles, who can add and configure it within flows to dynamically fetch catalog variable values at the time the action runs.

## Key Features

* **Input flexibility:** Accepts a requested item record (*screqitem*) to specify the source of variable values.
* **Template catalog items and variable sets:** Allows selection of a catalog item record (*sccatitem*) to define the set of variables available for retrieval. Note that this input doesn't support dynamic pill values.
* **Variable selection:** Lets you choose specific catalog variables via a slush bucket interface, with each selected variable appearing as a data pill for use in subsequent flow steps.
* **Output data pills:** Produces outputs corresponding to each selected catalog variable, typed according to the variable's data type, enabling easy consumption elsewhere in your flow.
* **Dynamic update consideration:** The action returns variable values as they exist when the action runs. To handle changes in variable values after retrieval, you must implement additional logic such as using a Wait For Condition action with change detection and re-invoking this action in the flow.

## Practical Application Example

For instance, you can design a flow triggered by a Service Catalog request that:

* Identifies the catalog item record associated with the requested item.
* Uses conditional logic to check if the item belongs to a specific category, such as Hardware.
* Applies the Get Catalog Variables action to fetch values from selected variables in a template catalog item (e.g., Standard Laptop).
* Utilizes the resulting data pills representing variable values for further processing or decision-making within the flow.

This approach enables precise and dynamic handling of catalog variables associated with requested items, enhancing automation and flow customization based on user selections in the Service Catalog.  
Select variables from multiple template catalog items and variable sets using the Get
Catalog Variables action.

## Roles and availability {#get-cat-variables-flow-designer__section_pwq_rb5_kcb}

Available as a Workflow Studio ServiceNow core action. Users with the flow_designer or admin role can add an action to a flow and define configuration details.  
Note:  
This action only returns the value of catalog variables at the time it was run. If you expect the action to recognize when catalog variable values change, you must build that logic into your flow. For example, use a Wait For Condition action with a changes operator to get catalog variables when a field value changes. If the field value changes, you must add the action in the flow again.

## Inputs {#get-cat-variables-flow-designer__section_ych_jln_lyb}

Provide a value for each input that your flow needs. To add dynamic values, you can also drag and drop pills from the Data panel or select them from the pill picker.{#get-cat-variables-flow-designer__inputs-description}

Submitted Request
:   Data type: Record

    The requested item record from the Requested Item \[sc_req_item\] table for which you want to get catalog variable values.

Template Catalog Items and Variable Sets \[Catalog Items and Variable Sets\]
:   Data type: Record

    The Catalog Item \[sc_cat_item\] record you want to use to populate the catalog variables slush bucket. This input does not support any data pill values.

Catalog Variables
:   Data type: Slush Bucket

    The list of catalog variables whose values you want to get from the requested item record. Each catalog variable that you select is displayed as a data pill in the data pane. You can define flow-specific variables that are displayed in the Available list. To define flow-specific variables, see [Create flow Service Catalog variables](https://www.servicenow.com/docs/BVeN40IwcxlqOFfk44XmTw "Create Service Catalog variables that are only available to a specific Service Catalog flow. Flow-specific variables are available to catalog tasks and actions in the flow.").

## Outputs {#get-cat-variables-flow-designer__section_zch_jln_lyb}

These outputs appear in the Data panel. You can use them as inputs elsewhere in your flow.{#get-cat-variables-flow-designer__outputs-description}

Catalog Variables
:   Data type: Varies by catalog variable type

The data pane displays a separate data pill for each catalog variable selected from the Catalog Variables input. For a list of supported Service Catalog types, see [Supported Service Catalog variable types](https://www.servicenow.com/docs/T~xhefDlKZPYWegl7X6cLg "Workflow Studio supports several Service Catalog variable types for both single-row and multi-row variable sets.").  

## Get catalog variables for hardware items {#get-cat-variables-flow-designer__example_ctt_42p_sbc}

In this example, a flow runs when someone requests an item from the Service Catalog. The first flow step looks up the Catalog item record of the requested item. The If flow logic uses the category value (Sys ID) of the catalog
item to determine if request is for an item in the Hardware category. The Get Catalog Variables action uses the trigger record as the Submitted Request input. The Template Catalog Items and Variable Sets input uses the variables
provided in the Standard Laptop catalog item. All three available catalog variables are selected and displayed as data pills in the data pane.

The flow execution details show that the Submitted Request links to a request for a standard laptop. Of the three catalog variables, the string variable is empty and the two Boolean variables are false.

