---
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
---
# Create an attended configuration record
# Create an attended configuration record in RPA Hub {#ariaid-title1}
Release version: Australia
Updated March 12, 2026
 1 minute to read
Create an attended configuration record in RPA Hub to trigger an attended bot process that is enabled with embedded task automation.
## Before you begin
Familiarize yourself with Embedded Task Automation concepts. For more information, see [Embedded Task Automation (ETA) in RPA Hub](https://www.servicenow.com/docs/eF6bSd361W_d5xgrlFaVIg "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.").
Verify that you've completed the tasks that are related to configuring the Embedded Task Automation in RPA Hub. For more information, 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.").
Create an attended bot process. 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.").
Verify that the Enable Embedded Task Automation check box is selected in the associated attended 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.").
Verify that the Robotic Process Automation (RPA) developer (sn_rpa_fdn.rpa_developer) is in the Managed by Group list of the associated bot process.
Role required: sn_rpa_fdn.rpa_release_manager, sn_rpa_fdn.rpa_developer, or sn_rpa_fdn.rpa_admin
## Procedure
1. Navigate to AllRobotic Process AutomationRPA Hub Workspace.
2. Select the list icon (![List icon.]()).
3. Create an attended configuration record from either the menu list or from an attended bot process record's related list.
| Option | Action |
| Create an attended configuration record from the menu list | 1. On the Lists tab, under Build, select Attended Configurations. 2. Select New. {#create-attended-config-rpa__ol_gr4_mn2_vzb} |
| Create an attended configuration record from an attended bot process record's related list | 1. On the Lists tab, under Build, select Bot Process. 2. Open an attended bot process that you want to create and associate an attended configuration to. 3. On the Attended Configurations tab, select New. {#create-attended-config-rpa__ol_ir4_mn2_vzb} |
|-|-|
{#create-attended-config-rpa__choicetable_fr4_mn2_vzb}
4. On the Attended Configuration form, fill in the fields.
For more information, 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.").
5. Select Save.
{#create-attended-config-rpa__steps_tmd_qhv_rzb}
* **[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.
**Related concepts**
* [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.")
**Related tasks**
* [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.")
* [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.")
* [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).")
**Related reference**
* [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.")
* [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.")
*[\>]: and then