--- 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 --- # Build actions # Building 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 Building actions Workflow Studio is the default process automation builder within the ServiceNow AI Platform for creating and managing actions, replacing the older Workflow Editor. It enables ServiceNow customers to define, test, and publish reusable automation components that streamline workflows and processes. Show full answer Show less ## Core Features * **Core Actions:** Prebuilt ServiceNow core actions are included with your instance but cannot be viewed or edited in Workflow Studio. Some applications provide spokes with application-specific actions that are typically read-only but can be copied and customized. * **Custom Actions:** Allow creating reusable actions with fixed configurations to simplify flow design when the same logic is frequently used. * **Action Design Environment:** Define inputs, add action steps, test actions with runtime value review, copy existing actions as templates, and publish actions to activate them for use in flows. * **More Actions Menu:** Provides options to copy actions to different applications, enable inline scripting, generate code snippets, manage security settings such as Callable by Client API, and create or edit natural language titles for actions. * **Testing Actions:** Users with actiondesigner or admin roles can test actions by providing inputs. Testing should be done in non-production instances to avoid unintended data changes. * **Roles Required:** Creating custom actions requires the actiondesigner or admin role. * **Action Status Data Pill:** Each action includes an Action Status data pill that provides current runtime details including a code and message, useful for error handling and monitoring. ## Advanced Capabilities * **Reusable Actions:** Convert existing actions (e.g., Ask for Approval) into reusable components that enforce specific behaviors like manager approval. * **Conversational Action Skills:** Build and configure conversational skills linked to actions, allowing multiple skills per action and enabling actions in conversational interfaces. * **LLM Integration:** Configure Large Language Model (LLM) settings to automatically generate descriptive metadata for conversational actions, inputs, outputs, and skills. * **Complex Data Handling:** Use graphical interfaces to manage collections of complex structured data, facilitating clear organization and configuration of data elements relevant to actions. ## Practical Benefits ServiceNow customers can leverage Workflow Studio's action-building capabilities to automate complex processes efficiently, create reusable and standardized automation components, enhance conversational AI experiences, and maintain robust error handling and testing practices. This leads to accelerated workflow development, improved automation consistency, and better integration with AI-powered conversational tools. Workflow Studio is the default ServiceNow AI Platform process automation builder used to create actions. Workflow Studio replaces the Workflow Editor. ## Core actions {#actions__section_pgn_dlb_zkb} ServiceNow Core actions that come with your instance cannot be viewed or edited from the Workflow Studio interface. Some applications include spokes which include application-specific actions. Spoke actions are typically read-only but can be copied and customized. ## Custom actions {#actions__section_ctx_xhl_kcb} Unlike core actions where flow designers must manually configure flow logic, custom actions always use the same configuration when added to a flow. If your flow designers often use an action with the same configuration, you might create a reusable action. ## Action design environment {#actions__section_h4l_j2t_kcb} Create and edit actions by defining inputs and adding action steps. Test actions to verify if they complete successfully and review the runtime values they generate. Copy actions to use existing actions as templates. Publish actions to activate them, which makes them available to activated flows and to preserve their current action steps, variables, and sequence as a snapshot separate from further configuration changes. ## More Actions {#actions__section_zrk_t5k_4fb} Click the More actions icon (![More actions icon]()) to access additional options for the action. Copy action : Create a copy of the open action in an application you specify. Configurations : Enable or disable the Show inline script toggle option. Code Snippet : Generate a code snippet for the action. Manage security : Enable or disable the Callable by Client API option. Manage natural language title : Create or edit an action title with styled or dynamic text. For more information, see [Manage natural language titles](https://www.servicenow.com/docs/WSaLBZRIwojmCouJEi~1Mw "Change the default title for a flow, subflow, or action by adding styled and dynamic text."). ## Testing actions {#actions__section_y2c_jwh_fhb} After adding inputs and action steps, users with the action_designer or admin role can test an action. To test an action, provide the required inputs. Action designers should always test actions on non-production instances containing relevant demonstration data because testing an action can make significant changes to records on your instance. ## Roles {#actions__section_egp_d3l_kcb} To create custom actions, you must have the action_designer or admin role. ## Action status Every action has an Action Status data pill in the Data pane. This object data pill contains the current runtime details about the action. The Action Status object consists of a code and message. Action Status \> Code : Integer data pill containing the code returned by the first matching error condition or the last step run. You can return your own code when you create a custom 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."). Action Status \> Message : String data pill containing the message produced by a matching error condition or the last step run. You can return your own message when you create a custom 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."). * **[Getting started with actions](https://www.servicenow.com/docs/FkJAmFvrxxE_E0W2jNoIUA)** Transform the Ask for Approval action into a reusable action that always requires manager approval. * **[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. * **[Create conversational action skill](https://www.servicenow.com/docs/5TxY9OUH4r2l13E4~MfJig)** Create a skill for the conversational action and make the skill available for users in a conversation. You can have multiple skills for the same action. * **[Configure action conversational settings](https://www.servicenow.com/docs/fSIlMJIzv_O_O6NQSnRu2A)** Configure conversation settings to make an action available to conversational interfaces. * **[Configure LLM to generate descriptions for conversational actions](https://www.servicenow.com/docs/4Sssb3gXaITu1uHeiB0pUQ)** Choose which LLM you want to use by default to generate descriptions for inputs, outputs, and skills for conversational actions. * **[Test conversational action](https://www.servicenow.com/docs/X4pfgtj_moWWGjqtrYtNRA)** Test a conversational action to verify it responds correctly to user inputs and performs the expected operations before deploying it in production. * **[Complex data](https://www.servicenow.com/docs/kOWMv2XXJdAyiN_5ldPysA)** Use a graphical interface to work with collections of complex structured data. Help design users understand the organization of structured data, and add, remove, or configure its individual elements.