List of steps for configuring embedded task automation

  • Release version: Zurich
  • Updated July 31, 2025
  • 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 List of steps for configuring embedded task automation

    This guide outlines the sequential tasks required to configure embedded task automation within ServiceNow using the Zurich release. Following these steps enables you to build, associate, and deploy attended bot processes integrated with ServiceNow forms and interfaces, thus automating tasks efficiently.

    Show full answer Show less

    Configuration Steps

    • Understand Embedded Task Automation concepts: Begin by familiarizing yourself with ETA principles to effectively build and manage automations.
    • Create and publish automation: Use RPA Desktop Design Studio with new components such as Forms to build automations and publish them to your ServiceNow instance.
    • Configure attended bot process: Create a bot process linked to the published automation package; enable embedded task automation to access additional configuration tabs.
    • Define dynamic parameters: On the Process Field Parameters tab, set up parameters that the automation will use dynamically.
    • Create and map attended configuration: Establish an attended configuration record and map form fields to the process parameters via the Field Parameter Mappings tab.
    • Activate attended configuration: Activate this record to enable UI actions on ServiceNow forms, allowing users to trigger the attended automation.
    • Trigger automation via API: For advanced integrations such as Workspace or playbooks, create actions that call the RPAInstanceFormHooks API to invoke automations.
    • Assign users and manage licensing: Assign RPA Assisted Users or groups to the attended bot process. Understand the system property controlling auto-assignment of attended robots to ensure proper license availability.
    • Publish the bot process: Publish the bot process along with the associated package from RPA Desktop Design Studio.
    • User interaction: Assigned users will see a UI button on the relevant ServiceNow forms that, when clicked, triggers the attended bot process. The button’s visibility depends on specific conditions.

    Practical Benefits

    By completing these configuration steps, ServiceNow customers can embed automated task workflows directly into their existing processes and interfaces. This enables efficient, user-triggered robotic process automation that enhances productivity and reduces manual effort, all managed within the ServiceNow platform.

    Use this list of steps to guide you through all the tasks for configuring an embedded task automation.

    Complete all the tasks for a step before moving on to the next step.

    Do the steps in the order that they’re presented.

    Table 1. List of steps for configuring an embedded task automation
    Task Reference
    1) Familiarize yourself with Embedded Task Automation concepts. For more information, see Embedded Task Automation (ETA) in RPA Hub.
    2) Build an automation by using the new components in RPA Desktop Design Studio and publish it to the ServiceNow instance.

    For more information about the new components, see Forms.

    For more information about publishing the automation RPA Desktop Design Studio, see Publish an automation project in RPA Desktop Design Studio.
    3) Create an attended bot process. Associate it with the package that is published in step 2. For more information, see Configuring a bot process record in RPA Hub.
    4) Select the Enable Embedded Task Automation check box in the associated attended bot process form.

    On enabling this check box, two additional tabs, Process Field Parameters and Attended Configuration, are available on the bot process form.

    		 For more information, see Bot Process form in RPA Hub.
    5) On the Process Field Parameters tab, create dynamic parameters that are used in the automation. For more information, see Create a process field parameter in RPA Hub.
    6) Create an attended configuration record. For more information, see Create an attended configuration record in RPA Hub.
    7) On the Field Parameter Mappings tab, map the form fields to the process field parameters that are used in the automations. For more information, see Map a table field to a bot process field parameter in RPA Hub.
    8) Activate an attended configuration record to enable the UI action that triggers the attended automation on the associated ServiceNow form. For more information, see Activate an attended configuration record in RPA Hub.
    9) To trigger a bot process (automation) from a Workspace, a playbook, or any other service portal, you can create corresponding actions and call the RPAInstanceFormHooks Application Programming Interface (API). For more information, see Invoke Embedded Task Automation via API in RPA Hub.
    10) To publish the bot process, assign the user with RPA AU (RPA assisted user) in the Assigned User or Assigned Group field in the Attended Users/Groups tab of the attended bot process record.

    If the auto assignment system property sn_rpa_fdn.allow_rda_robot_auto_assignment is false, the attended robot record is available for the assigned RPA Assisted User.

    If the auto assignment system property is true, an attended robot license is available to auto create an attended robot at the time of triggering.

    For more information about assigning the user with RPA AU, see Assign an attended user or group to an attended bot process.

    For more information about this system property, see Configure RPA Hub properties.
    11) Publish the bot process with the corresponding package published from the RPA Desktop Design Studio. For more information, see Publish a bot process in RPA Hub.
    12) The assigned user can view the UI action (button) on the corresponding ServiceNow form. Using this button, the user can trigger the attended bot process (attended automation). There are certain conditions to view this button (UI action). For more information about the visibility conditions, see Conditions for the visibility of UI action (button).