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


---

# Look Up Record step

# Look Up Record step {#ariaid-title1}

Release version: Brazil  
Updated September 10, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read  
Look up a record from any table based on defined conditions.

## Roles and availability {#lookup-record-action-designer__section_pwq_rb5_kcb}

Available as an Workflow Studio action step. Users with the action_designer role can create a custom action with one or more action steps.

## Fields {#lookup-record-action-designer__look-up-record-fields}

{#lookup-record-action-designer__table_fdl_yhf_kcb__entry__2}

| Field | Description |
|-|-|
| Table | Select a table from the list. |
| Conditions | Set static or dynamic conditions to filter records. To define a static condition applied each time the action runs, define the conditions with the condition builder. To enable flow designers to dynamically apply conditions, define an input of type Conditions and drag-and-drop the input data pill into the Conditions field. When building a condition that looks up the value of a reference field, use a data pill that explicitly provides the Sys ID value. Ensure the condition has the format \[reference field\]\[is\]\[Reference type data pill-\>Sys ID\]. For example, both the Change and Incident tables contain a reference field to the User table. To look up change records where the requester is the caller from an incident record, create the condition \[Requested by\]\[is\]\[Trigger-\>incident record-\>Caller-\>Sys ID\]. \[Requested by\]\[is\]\[action-\>incident-\>Caller-\>Sys ID\] where incident is an input variable for an incident record. |
| Order by | Determines how to sort results when more than one record matches the defined conditions. Select the field you want to use to sort results. |
| Sort Type | Select whether to sort alphabetically in ascending or descending order. |
| If multiple records are found | Determines what is returned if more than one record matches the defined conditions. * Return only the first record * Fail the step {#lookup-record-action-designer__ul_x5p_kkf_kcb} |
| Don't fail on error | Determines whether to fail the flow if a record can't be found. |
[ ]

{#lookup-record-action-designer__table_fdl_yhf_kcb}

## Outputs {#lookup-record-action-designer__section_ldx_pyb_pmb}

These outputs appear in
the Data panel. You can use them as inputs elsewhere in your flow.{#lookup-record-action-designer__outputs-description}

Record
:   Data type: Record

    Record found based on the
    conditions you specified in the Conditions
    input.

Table
:   Data type: Table

    Name of the table associated
    with the returned record.

Status
:   Data type: Choice

    1 if a record was found
    successfully, and 0 if there was an error.

Error Message
:   Data type: String

    Message containing details about
    why the record could not be found.

    Note:  
    This output's value is only populated if the Status output's value is 0.

## Action error evaluation {#lookup-record-action-designer__id_lg2_4s3_15b}

If this step fails
:   Data type: Choice

    Option to continue running the next step or go to error evaluation. To use the step status code or message for a custom action error condition, see [Action error evaluation](https://www.servicenow.com/docs/DYUWPGHPp4xlTo_Ny0q7aQ "Enable actions to catch step failures and continue running. Identify when specific error conditions occur and return your own action status code, status message, and error state.").

## Example {#lookup-record-action-designer__section_qyb_w35_kcb}