Building actions

  • Release version: Australia
  • Updated March 12, 2026
  • 2 minutes to read
  • Summarize
    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 primary AI Platform process automation builder in ServiceNow for creating and managing actions, replacing the older Workflow Editor. Actions automate specific steps within workflows and can be core, spoke, or custom. Core actions are built-in and not editable via Workflow Studio, while spoke actions are application-specific and usually read-only but can be copied and customized. Custom actions are reusable components configured once and used repeatedly in flows to streamline automation.

    Show full answer Show less

    Action Design and Management

    In Workflow Studio, you create and edit actions by defining inputs and adding action steps, then test them to ensure proper execution and review runtime outputs. Actions can be copied as templates and published to activate them, preserving their current configuration separately from future edits.

    The More actions menu offers additional options such as copying actions to different applications, enabling inline scripts, generating code snippets, managing security settings like client API access, and editing natural language titles to improve action clarity.

    Testing and Roles

    Testing actions requires the actiondesigner or admin role and should be performed on non-production instances with relevant data to avoid unintended changes. Testing involves providing required inputs and verifying that the action completes successfully.

    Action Status Monitoring

    Each action includes an Action Status data pill showing runtime information with a code and message indicating success or error states. Custom error codes and messages can be defined to enhance error handling and troubleshooting within actions.

    Getting Started and Advanced Features

    • Create reusable actions: Convert existing actions like "Ask for Approval" into reusable components with fixed configurations.
    • Create conversational action skills: Develop skills linked to actions that users can interact with via conversational interfaces, including multiple skills per action.
    • Configure conversational settings: Make actions accessible within conversation-based workflows.
    • Leverage large language models (LLMs): Select default LLMs to generate descriptions for conversational actions’ inputs, outputs, and skills.
    • Work with complex data: Use graphical tools to manage collections of structured data, simplifying design and configuration of nested data elements.

    Practical Benefits for ServiceNow Customers

    This capability enables ServiceNow customers to build efficient, reusable automation components that streamline process workflows, enhance conversational experiences, and improve error handling. Workflow Studio’s interface and tools support both simple and advanced automation needs, empowering action designers to create robust, testable, and maintainable actions that can be deployed safely and effectively across their ServiceNow environment.

    Workflow Studio is the default ServiceNow AI Platform process automation builder used to create actions. Workflow Studio replaces the Workflow Editor.

    Core actions

    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

    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

    Action Designer interface

    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

    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.

    Testing actions

    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

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