--- 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 --- # Embedded Task Automation (ETA) # Embedded Task Automation (ETA) in RPA Hub {#ariaid-title1} Release version: Australia Updated March 12, 2026 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 6 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 Embedded Task Automation (ETA) in RPA Hub The Embedded Task Automation (ETA) feature allows ServiceNow users to trigger attended bot processes directly from ServiceNow forms, enhancing user interaction with automations. This provides a seamless experience where users can monitor the automation in real-time without needing to develop separate forms within the automation itself. Show full answer Show less ## Key Features * **Triggering via API:** Initiate automations from various ServiceNow interfaces using API calls to the RPAInstanceFormHooks. * **Dynamic Parameters:** Utilize process field parameters to manage data flow between ServiceNow forms and automations, simplifying information handling. * **New Components:** RPA Desktop Design Studio includes new components like AttendedConfigurations and GetProcessFieldParameters to enhance automation capabilities. * **Terminate Component:** Essential for completing automation executions effectively within attended processes. * **UI Action Creation:** Automatically generates a button on ServiceNow forms to trigger the automation, contingent upon specific conditions. ## Key Outcomes By implementing Embedded Task Automation, ServiceNow customers can expect: * Improved efficiency in automating repetitive tasks directly from existing ServiceNow interfaces. * A user-friendly experience where users are engaged and can observe processes in real-time. * Reduced development overhead as existing ServiceNow screens can be leveraged without the need for new form creation. * Streamlined data handling through dynamic parameter mapping, ensuring a smooth workflow during automation execution. With the embedded task automation feature, trigger attended bot processes (attended automations) from the ServiceNow forms, apart from initiating them from the Attended Robot application. Important: The embedded task automation runs only for published attended bot processes. ## Invoke Embedded Task Automation via API {#embedded-task-auto-rpa__section_bjm_hf1_f1c} 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 about invoking an embedded task automation via an API, see [Invoke Embedded Task Automation via API in RPA Hub](https://www.servicenow.com/docs/EsZDn_XQcZPSf5Ux6t_Zgg "Invoke an attended bot process (attended automation) from the UI experiences by creating an action."). ## Embedded Task Automation overview {#embedded-task-auto-rpa__section_hwf_2hr_zzb} Use the embedded task automation feature to initiate an automation seamlessly from ServiceNow screens in an attended mode. It provides users with a transparent view of the robot executing tasks directly on their machines. This feature provides a user-friendly experience by enabling individuals to observe and monitor the automation process in real-time. ## Why Embedded Task Automation {#embedded-task-auto-rpa__section_ekx_1qm_vzb} Since existing attended automations interact with forms that are built within the automation itself, form development is required. Use the Embedded Task Automation feature for attended automations that use the ServiceNow screens. The Embedded Task Automation feature enables the reuse of the existing ServiceNow screen without a need to develop forms with in automation. ## How Embedded Task Automation works {#embedded-task-auto-rpa__section_bqq_cgv_rzb} Let's consider an employee badge creation use case. 1. In the Service Catalog, a request is created for an employee badge generation. Details such as Requested for and Location are included in this request form, for printing the badge on a third party application. After the badge is generated in the application, the badge ID is populated in the request form. 2. In RPA Desktop Design Studio, build an automation using the new components and publish it to the ServiceNow instance. For more information about the new components, see [Forms](https://www.servicenow.com/docs/OCiEzXWSh3O0fRFNBANcZQ "The Forms components help you to trigger attended automations that are enabled with the Embedded Task Automation."). Ensure to use the Terminate component for each UI action automation logic that helps in completing the automation execution for the respective UI action. For more information about the component, [Use the Terminate component](https://www.servicenow.com/docs/nAg8yxFqwNBwEg6792pDVA "Abort an automation by using the Terminate component in RPA Desktop Design Studio."). 3. In the RPA Hub, create an attended bot process (for example, Employee Badge Generation). For more information about creating an attended bot process, see [Configuring a bot process record in RPA Hub](https://www.servicenow.com/docs/hb2MAhKGRNGZmQ2HlgCy3A "In RPA Hub, you can create a bot process configuration record and assign assets to associate it with a bot process. Or you can just save the bot process configuration record, however it won't be associated to a bot process. It remains orphaned."). 4. To trigger this bot process (automation) from the ServiceNow form, 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 about the bot process form, see [Bot Process form in RPA Hub](https://www.servicenow.com/docs/sxq9e8qhznUmwpOhyrBCGQ#bot-process-form "Use the Bot Process form to associate it to the bot process configuration and populate the remaining fields required for a bot process."). 5. On the Process Field Parameters tab, create dynamic parameters that are used in the automation. Process field parameters are used for setting the value or getting the value of a field on a particular form. Examples of process field parameters are the user's title, first name, last name, and location. These details are used in the automation workflow while generating a badge. For more information about creating process field parameters, see [Create a process field parameter in RPA Hub](https://www.servicenow.com/docs/Am~ess7AgGJgihAfI2v6_g "Define process field parameters (dynamic parameters) that are required in the automation (bot process)."). 6. In the RPA Hub, create an attended configuration record. For more information about creating an attended configuration record, see [Create an attended configuration record in RPA Hub](https://www.servicenow.com/docs/hkmb_~X7RMhAvmfDY88NzQ "Create an attended configuration record in RPA Hub to trigger an attended bot process that is enabled with embedded task automation."). 7. In this attended configuration record, select the table associated with the required form from the Table field, from where this bot process must be triggered. Then, define the criteria in the Conditions field, to trigger the bot process. In this example, set the conditions for approved requests that are required for badge generation. For more information about the Attended Configuration form, see [Attended Configuration form in RPA Hub](https://www.servicenow.com/docs/4ceklVDXN9gU~e~S9YuqkA "Use the Attended Configurations form to associate the table form, from where the automation must be initiated, associate the respective attended bot process, and other related conditions."). 8. On the Field Parameter Mappings tab, map the form fields to the process field parameters that are used in the automations. This process enables an easy data flow during the execution of a bot process. For example, if "Full name" is the process field parameter used in the automation, then map it to the form's 'Name' field. For more information about mapping field parameters, see [Map a table field to a bot process field parameter in RPA Hub](https://www.servicenow.com/docs/8ncSB48alsI2Gvp_Mo3ZnQ "Map form fields of the associated attended configuration table (Table field) to the process field parameters used in the automations. For example, if \"First name\" is the process field parameter used in the automation, then it’s mapped to the form's 'requested_for.first_name' field."). 9. On the Attended Configuration tab, the form is activated by selecting the Activate button. In the background, a UI action (button) is created on the corresponding request form. For more information about activating an attended configuration, see [Activate an attended configuration record in RPA Hub](https://www.servicenow.com/docs/uGdnRSUFLdC3NZ23yHTzzw "Activate an attended configuration record to enable the UI action that triggers the attended automation on the associated ServiceNow form."). 10. 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](https://www.servicenow.com/docs/OTUl9P1QzdZkgr88lsMxXw "Publish a bot process so that you can get it ready to execute a process."). 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 this system property, see [Configure RPA Hub properties](https://www.servicenow.com/docs/wRNW_tXOfpoIyDdWyhc6KQ "You can access system properties for RPA Hub by navigating to All > Robotic Process Automation > Administration > Properties ."). 11. Then, the assigned user can view the UI action (button) (for example, Generate Badge) 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, see [Conditions for the visibility of UI action (button)](https://www.servicenow.com/docs/MaIf9wmLtJw~o9x~Khkt~g "Ensure the following conditions are met to view the UI action (button) on the corresponding ServiceNow form, for the associated table that is selected in the Attended Configuration record."). {#embedded-task-auto-rpa__ul_tzg_ykq_yzb} Figure 1. Configuration of Embedded Task Automation in RPA Hub ## Configuring Embedded Task Automation {#embedded-task-auto-rpa__section_iqz_v3b_d1c} To configure the embedded task automation, see [List of steps for configuring embedded task automation](https://www.servicenow.com/docs/L6LdKozBBoGprn1~o70nfQ "Use this list of steps to guide you through all the tasks for configuring an embedded task automation."). ## New components for Embedded Task Automation in RPA Desktop Design Studio {#embedded-task-auto-rpa__section_b2k_ms3_b1c} The following four new components are added to the new Forms section in RPA Desktop Design Studio. These components are available under the new ServiceNow category in the Toolbox pane. * AttendedConfigurations: Segregate the execution of the automations in a single automation project and call the respective logic according to the action invoked. For more information, see [Use the AttendedConfigurations component](https://www.servicenow.com/docs/ThDtVsRH1xzHMP0UldH3pw "When you use the AttendedConfigurations component, it shows a list of attended configurations associated to the selected same bot process. To select and give control out port for each configuration that routes the automation logic."). * GetProcessFieldParameters: Fetch the values of the ServiceNow form fields associated in the Field Parameter Mapping of the corresponding attended configuration record in RPA Hub. For more information, see [Use the GetProcessFieldParameters component](https://www.servicenow.com/docs/lAiRRQukGEEo15~nEglHTg "Gets the values of the associated Table fields mapped to the process field parameter, that you had configured in an attended configuration record of a bot process. The component returns both the individual values of the parameters and all values as an object. This component reads the value of the associated Table field in the ServiceNow form record."). * GetRecordContextID: Fetch the current record sys_id of the ServiceNow form, from where the automation is triggered. For more information, see [Use the GetRecordContextID component](https://www.servicenow.com/docs/UgerfHBG3YT4tDmW5MYqjA "Get the Sys ID of the ServiceNow form record that is associated to an attended configuration with the GetRecordContextID component in the RPA Desktop Design Studio. Sys ID is the output of the component. For example, Sys ID is used to fetch the attachments in a record."). * SetProcessFieldParameters: Update the values of the ServiceNow form fields associated in the Field Parameter Mapping of the corresponding attended configuration record in RPA Hub. For more information, see [Use the SetProcessFieldParameters component](https://www.servicenow.com/docs/HcvawgJ2xqN_FKDG~SFROg "Sets the values of the associated Table fields mapped to the process field parameter, that you had configured in an attended configuration record of a bot process. This component updates the values of the configured field parameters associated to the Table field in the ServiceNow form record."). {#embedded-task-auto-rpa__ul_jkj_zgd_zzb} ## Terminate component in attended automations {#embedded-task-auto-rpa__section_kfh_kzr_gbc} Use the Terminate component in attended automations to complete the automation execution. For more information about the component, [Use the Terminate component](https://www.servicenow.com/docs/nAg8yxFqwNBwEg6792pDVA "Abort an automation by using the Terminate component in RPA Desktop Design Studio."). ## Launch attended automations from ServiceNow forms {#embedded-task-auto-rpa__section_l2m_2qp_b1c} Learn about the restrictions to launch an attended automation from the ServiceNow forms and launching the attended automations. For more information, see [Attended Robot authentication journey and automation execution in Embedded Task Automation](https://www.servicenow.com/docs/yySaqD8NBa8rTn2z_t_nDQ "Learn about the authentication process in the Attended Robot application and the automation execution, when the automation is triggered from ServiceNow forms."). ## Attended Robot authentication journey and automation execution {#embedded-task-auto-rpa__section_vkj_bjb_b1c} Learn about the authentication process in the Attended Robot application and the automation execution. For more information, see [Attended Robot authentication journey and automation execution in Embedded Task Automation](https://www.servicenow.com/docs/yySaqD8NBa8rTn2z_t_nDQ "Learn about the authentication process in the Attended Robot application and the automation execution, when the automation is triggered from ServiceNow forms."). Important: If a new version exists to the existing automation, to reflect those changes the Attended Robot application must be closed. Until then, it continues to use the existing version, as the Attended Robot application is already launched and running. If a new version of RPA Hub is installed on the instance, to reflect those changes the Attended Robot application must be closed. Until then, it continues to use the existing set of plugins, as the Attended Robot application is already launched and running. ## Runtime Phase of the Embedded Task Automation {#embedded-task-auto-rpa__section_kqk_ynb_d1c} Learn more about the triggering of an attended automation from a ServiceNow form. For more information, see [Runtime Phase of the Embedded Task Automation (ETA)](https://www.servicenow.com/docs/qhyUhBCRjmqGihyjRXI3Vw "Learn more about the triggering of an attended automation from a ServiceNow form."). * **[List of steps for configuring embedded task automation](https://www.servicenow.com/docs/L6LdKozBBoGprn1~o70nfQ)** Use this list of steps to guide you through all the tasks for configuring an embedded task automation. * **[Runtime Phase of the Embedded Task Automation (ETA)](https://www.servicenow.com/docs/qhyUhBCRjmqGihyjRXI3Vw)** Learn more about the triggering of an attended automation from a ServiceNow form. * **[Create an attended configuration record in RPA Hub](https://www.servicenow.com/docs/hkmb_~X7RMhAvmfDY88NzQ)** Create an attended configuration record in RPA Hub to trigger an attended bot process that is enabled with embedded task automation. * **[Activate an attended configuration record in RPA Hub](https://www.servicenow.com/docs/uGdnRSUFLdC3NZ23yHTzzw)** Activate an attended configuration record to enable the UI action that triggers the attended automation on the associated ServiceNow form. * **[Deactivate an attended configuration record in RPA Hub](https://www.servicenow.com/docs/~wTljXewcGkNgAH9ydpw5g)** Deactivate an attended configuration to move the record to inactive state. * **[Edit an attended configuration record in RPA Hub](https://www.servicenow.com/docs/oy4vwYNRu60A_aSUFfvIAA)** Edit an existing attended configuration record in RPA Hub to modify a few details of the record. * **[Delete an attended configuration record in RPA Hub](https://www.servicenow.com/docs/3DfMF2t_CJLoH_jP4dfMVg)** Delete an attended configuration record that you no longer need. * **[Attended Configuration form in RPA Hub](https://www.servicenow.com/docs/4ceklVDXN9gU~e~S9YuqkA)** Use the Attended Configurations form to associate the table form, from where the automation must be initiated, associate the respective attended bot process, and other related conditions. * **[Invoke Embedded Task Automation via API in RPA Hub](https://www.servicenow.com/docs/EsZDn_XQcZPSf5Ux6t_Zgg)** Invoke an attended bot process (attended automation) from the UI experiences by creating an action. * **[Conditions for the visibility of UI action (button)](https://www.servicenow.com/docs/MaIf9wmLtJw~o9x~Khkt~g)** Ensure the following conditions are met to view the UI action (button) on the corresponding ServiceNow form, for the associated table that is selected in the Attended Configuration record. **Related tasks** * [Deactivate an attended configuration record in RPA Hub](https://www.servicenow.com/docs/~wTljXewcGkNgAH9ydpw5g "Deactivate an attended configuration to move the record to inactive state.") * [Delete an attended configuration record in RPA Hub](https://www.servicenow.com/docs/3DfMF2t_CJLoH_jP4dfMVg "Delete an attended configuration record that you no longer need.") * [Edit an attended configuration record in RPA Hub](https://www.servicenow.com/docs/oy4vwYNRu60A_aSUFfvIAA "Edit an existing attended configuration record in RPA Hub to modify a few details of the record.")