--- sourceDocument: Brazil Workflow Data Fabric sourceDocumentLink: https://www.servicenow.com/docs/r/integrate-applications Release : - brazil ft:locale : - en-US ft:publication_title : - Brazil Workflow Data Fabric ft:clusterId : - crint bundleId : - crint workflow : - Creator --- # Create an unattended robot # Create an unattended robot in RPA Hub {#ariaid-title1} Release version: Brazil Updated September 10, 2026 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 3 minutes to read Create an unattended robot in RPA Hub to run the unattended bot process. ## Before you begin Configure the related system property to view the activity stream. For more information, see [Display an activity stream for bot processes and robots in RPA Hub](https://www.servicenow.com/docs/fiPv3UMydpZ1uDxdATjl7Q "Configure the system property to display an activity stream for bot processes and robots in RPA Hub."). Make sure that the sn_rpa_fdn.enable_unattended_robot_user_mapping system property is set to True to allow only the authorized users to access the robot and robot assets. This system property enables the User field on the Unattended Robot form. If you have the admin role, you can edit this system property. By default, this property is set to True. Role required: sn_rpa_fdn.rpa_release_manager or sn_rpa_fdn.rpa_admin ## About this task A robot runs a bot process, which is an automation. An unattended robot can execute an unattended bot process, which is an automation that requires no human intervention. By using the Unattended Robot application, you can enable an unattended robot to execute an unattended bot process that is triggered either by a schedule, API, or manually set. You can map multiple unattended robots as high density robots to one virtual machine. For more information, see [High density robots in RPA Hub](https://www.servicenow.com/docs/1VGKwsule~nBzfKBsbVfUw "Execute multiple automations (bot processes) simultaneously and independently on a single Windows Server machine using high density robots."). ## Procedure 1. Navigate to AllRobotic Process AutomationRPA Hub Workspace. 2. Create an unattended robot from either the list icon or from the plus icon. | Option | Action | | Create an unattended robot from the list icon | 1. Select the list icon (![List icon.]()). 2. On the Lists tab, under Administration, select Robots. 3. Select New. {#create-unattended-robot__ol_akt_kxm_frb} | | Create an unattended robot from the plus icon | 1. Select the plus icon (![Plus icon.]()). 2. Select New Robot. {#create-unattended-robot__ol_q5l_1cn_frb} | |-|-| {#create-unattended-robot__choicetable_kgc_jxm_frb} 3. On the form, fill in the fields. {#create-unattended-robot__table_pyx_mhd_4qb__entry__2} | Field | Description | |-|-| | Name | Unique name of the unattended robot. | | Robot Type | Type of the robot. Unattended: Robot for an unattended automation. | | Machine Name | Computer name of the physical or virtual machine on which the Unattended Robot application is installed. This field appears only when Unattended is selected from the Robot Type field. The machine name is a string-type field that you use when you don't want to enable the sn_rpa_fdn.enable_unattended_robot_machine_name_lookup system property. If you enable the sn_rpa_fdn.enable_unattended_robot_machine_name_lookup system property, this string type field changes to a reference type field on the robot form. The machine name fetches the unique value references from the Configuration Item (CI) tables that are defined in the sn_rpa_fdn.machine_name_reference_fields system property. The bot process table (cmdb_ci_rpa_process) and robot table (cmdb_ci_rpa_robot) are excluded from the search results when you provide the names of the CI tables to reference the unattended robot's machine name in the sn_rpa_fdn.machine_name_reference_fields system property. The Machine Lookup value change scheduled job validates the values in the Machine Name Lookup field and Machine Name field. For more information, see the Scheduled jobs installed section in [Components installed with RPA Hub](https://www.servicenow.com/docs/NAeFM2PIGM02bILx6uLrwA "Several types of components are installed with the activation of the RPA Hub plugin, including tables, user roles, and scheduled jobs.") and [Configure RPA Hub properties](https://www.servicenow.com/docs/wvt1K0et9MQR9HvlKLOUyw "You can access system properties for RPA Hub by navigating to All > Robotic Process Automation > Administration > Properties ."). | | High density robot | Option to create multiple robots with the same machine name. The machine must support multiple user sessions at the same time so that you can run multiple automations simultaneously. This field appears only when Unattended is selected from the Robot Type field. | | Screen resolution | Screen resolution used by a high density robot while establishing the RDP connection before executing the automation. High density robots can operate with different screen resolutions for each robot on the same machine without any issues if they are running different bot processes. However, if all high density robots on the same machine are executing the same process and utilizing Computer Vision actions, they must maintain the same resolution. Otherwise, the automation may fail. This field appears only when the robot is marked as high density robot. Note: You can change the default value of the screen resolution using the sn_rpa_fdn.robot_screen_resolution RPA Hub system property. | | User | Authorized user who can access this robot. If you're upgrading to Xanadu, the User field is automatically mapped with the user name (the user) who has recently created the process job for the selected unattended robots. If no process jobs are found for a selected robot, the robot is moved to the In Maintenance status. An RPA release manager must manually map the appropriate users to the robots. Note: This field appears when the sn_rpa_fdn.enable_unattended_robot_user_mapping system property is enabled. | | Department | Associated department of the robot. This field is automatically filled in with the information that is based on the department in the associated Attended Robot User's record. The value in this field corresponds to the value at the time that the Robot record is created and isn't based on real-time data. | | Description | Brief description of the robot. | [Table 1. Robot form] {#create-unattended-robot__table_pyx_mhd_4qb} 4. Select Save. 5. **Optional:** In the Activity and Compose fields, view the activity of the form, work notes, and additional comments. ## What to do next Install Unattended Robot. For more information, see [Install Unattended Robot](https://www.servicenow.com/docs/u7TNde_4fPJ399ezP8DoTQ "You can install the Unattended Robot application in your Windows machine if you have the admin role.") Set up the Unattended Robot application. For more information, see [Set up Unattended Robot](https://www.servicenow.com/docs/CeL_wmz~elWuU7OhYB2oPw "Set up the Unattended Robot application to establish a connection between a robot and the ServiceNow RPA Hub instance."). Create a bot process. For more information, see [Configuring a bot process record in RPA Hub](https://www.servicenow.com/docs/Fh5n_jyVL~kis5vxVwxTSQ "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."). **Related tasks** * [Edit an unattended robot in RPA Hub](https://www.servicenow.com/docs/~JjqJIqP9boa02HU306KOA "Edit an existing unattended robot in RPA Hub to modify a few details of the robot, convert the robot to a high density robot, and view the robot state.") * [Retire a robot in RPA Hub](https://www.servicenow.com/docs/2EvvFQRxI8Ze0UbvPGn_Lw "Retire a robot to turn it off. It is one of the life-cycle stages of a robot. After you retire a robot, it cannot be used further.") **Related topics** * [View Audit History](https://www.servicenow.com/docs/access?context=c_HistorySets&version=brazil&pubname=brazil-platform-security&ft:locale=en-US) *[\>]: and then