---
sourceDocument: Australia Workflow Data Fabric
sourceDocumentLink: https://www.servicenow.com/docs/r/australia/integrate-applications

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia Workflow Data Fabric

ft:clusterId :

    - crint

bundleId :

    - crint

workflow :

    - Creator


---

# Use the GetExtension component

# Use the GetExtension component {#ariaid-title1}

Release version: Australia  
Updated March 12, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read  
Get the extension of a file and know its type as part of an automation Workflow by using the GetExtension component in RPA Desktop Design Studio.

## Before you begin

Role required: none

## About this task

You can configure the properties for the GetExtension component. For more information
about these properties, see [Properties of the File components](https://www.servicenow.com/docs/od6ZfKbAfA7oItV1B9fH1Q "Learn about the properties of the File components in RPA Desktop Design Studio.").

## Procedure

1. In the Toolbox pane, navigate to UtilitiesFile.
2. Drag the GetExtension component to the Design surface.
3. To configure the input fields, see [Configure port properties](https://www.servicenow.com/docs/o6fErdzBCUqYUWlLG1ZZzQ "Configure how data is passed to the input fields of a component or method in RPA Desktop Design Studio.").
4. Connect the data and control ports of the GetExtension component to the corresponding ports of the other component as described in the following table.  
   {#use-utilities-file-getextension__table_jnw_jn1_krb__entry__3}

   | Port type | Purpose of connection | Mandatory? |
   |-|-|-|
   | Data In (Path) | Takes the path to the file and the name of the file from a previously executed component. | Yes |
   | Data Out (Return) | Returns the file extension and passes to the next component. | Yes. To preview the data, right-click the Return field and click Preview Data. |
   | Control In | Connects to the Control Out port of one or more components. | No. Connecting the port is optional. |
   | Control Out | Connects to the Control In port of another component or the default end component. | No. Connecting the port is optional. |
   [ ]

   {#use-utilities-file-getextension__table_jnw_jn1_krb}
5. **Optional:** To test the component, under the DESIGN tab, click Run.

*[\>]: and then