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


---

# Explore actions

# Exploring actions {#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 Exploring actions

Actions in ServiceNow automate repeatable tasks or operations within flows by running a sequence of steps.
Flows provide inputs to actions and receive outputs in return, enabling streamlined automation of business processes.
Actions are reusable components designed to be added to multiple flows with minimal configuration, boosting efficiency and consistency.
Show full answer Show less  

## Key Features

* **Inputs:** Data variables used by actions, such as references to tables or fields. Inputs become configuration options in Workflow Studio, requiring flow designers to specify values for mandatory inputs. Inputs support advanced configuration like hints, default values, and choice lists to guide users during flow design.
* **Outputs:** Data variables representing the results of an action, which can be used by other actions within the flow.
* **Steps:** Individual reusable operations within an action, such as creating a record. Steps require subject matter expertise in application tables, fields, and business logic. Workflow Studio provides core steps and allows adding application-specific steps via spokes.
* **Action Creation:** Built using Workflow Studio, enabling creation of application-specific or scripted actions that appear code-less in flows. Integration Hub supports building integrations as actions.

## Benefits for ServiceNow Customers

* **Reusable Automation:** Develop actions once and reuse them across multiple flows, reducing duplication and simplifying maintenance.
* **Ease of Use:** Pre-set configurations allow process analysts and flow designers to add actions with minimal setup, without deep coding knowledge.
* **Data Integration:** Actions can accept inputs from other automated operations and pass outputs to subsequent steps, enabling complex data-driven workflows.
* **On-Demand Execution:** Actions can be run on demand, supporting flexible automation scenarios.
* **Integration Support:** Integration owners can utilize data streaming and integration actions to connect ServiceNow with external systems efficiently.  
Actions automate a repeatable task or operation within a flow. Flows run actions by passing them data as inputs. Actions run a sequence of steps to complete the task, and pass data to the flow as outputs.

## Actions overview {#exploring-actions__section_mxy_xhk_f1c}

Automate a repeatable task within a flow as a sequence of related steps. Enable flow authors to add actions to multiple flows with minimal configuration.

A reusable action includes these components.  

Inputs

:   Inputs are data variables used in your action. For example, if an action step creates a record in the incident table, your input might be a reference to the incident table. Once added as an input, the table and its
    fields are available to steps and outputs in the flow.

    Each input you define for an action becomes a configuration option in the Workflow Studio interface. To use the action in a flow, flow designers must define a value for each mandatory input. The more inputs an action has, the more data flow designers must define and the more familiar they must be with the underlying data model to use the action effectively.

    Inputs provide advanced options based on their data type. All inputs have advanced options to add a hint or provide a default value. Use advanced options to guide flow designers through adding and configuring an action to a flow. For example, create a choice input to provide flow designers with a pre-defined list of configuration options to choose from. For more information about the configuration options available to particular data types, see [field types](https://www.servicenow.com/docs/access?context=r_FieldTypes&version=brazil&pubname=brazil-platform-administration&ft:locale=en-US).

Outputs
:   Outputs are data variables that represent the results of the action. These results are available to other actions in a flow.

Steps

:   A step is a single reusable operation within an action. For example, the Create Record step allows action designers to specify the table and field values to use during record creation. Step configuration requires subject matter expertise with application tables, fields, and business logic. Application developers or IT generalists add steps to actions from the Workflow Studio action design environment. Workflow Studio provides a set of ServiceNow core steps to automate ServiceNow AI Platform processes. You can add application-specific steps by activating the associated spoke.

For detailed instructions for creating an action, see [Create an action in Workflow Studio](https://www.servicenow.com/docs/q17a0FcukNw6uRhBhCgF7Q "Create a reusable component to automate one or more steps of a process.").

## Actions benefits {#exploring-actions__section_qxy_xhk_f1c}

Using Workflow Studio, you can:

* Create application-specific actions with pre-set configuration details, enabling process analysts to easily add actions to a flow with little configuration.
* Create scripted actions that appear code-less when added to a flow.
* Build integrations using Integration Hub.
{#exploring-actions__ul_rmb_jg5_kcb}
{#exploring-actions__table_z5v_kfk_f1c__entry__3}

| Benefit | Feature | Users |
|-|-|-|
| Build an automated operation from an existing library of automated steps. | Action | Application developer, integration owner, or process owner |
| Run an automated operation on demand. | Action | Application developer, integration owner, or process owner |
| Use data from other automated operations as inputs. | Action | Application developer, integration owner, or process owner |
| Pass data to other automated operations as outputs. | Action | Application developer, integration owner, or process owner |
| Stream data in a sequence of pages. | Data Stream Action | Integration owner |
[ ]

{#exploring-actions__table_z5v_kfk_f1c}