--- sourceDocument: Zurich Workflow Data Fabric sourceDocumentLink: https://www.servicenow.com/docs/r/zurich/integrate-applications Release : - zurich ft:locale : - en-US ft:publication_title : - Zurich Workflow Data Fabric ft:clusterId : - crint bundleId : - crint workflow : - Creator --- # Publish a bot process # Publish a bot process in RPA Hub {#ariaid-title1} * Release version: Zurich * * Updated July 31, 2025 * * ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 3 minutes to read Publish a bot process so that you can get it ready to execute a process. ## Before you begin Ensure that the associated package version complies with the code quality check system property sn_rpa_fdn.restrict_package_by_severity, to verify if the code quality check is enabled in the RPA Hub instance. For more information about the system property, see [Configure RPA Hub properties](https://www.servicenow.com/docs/NfHnour51qgq7chO39QlsA "You can access system properties for RPA Hub by navigating to All > Robotic Process Automation > Administration > Properties ."). For more information about the compliance rules, see [Code quality check compliance for RPA Hub](https://www.servicenow.com/docs/LwiUX2ONcGTOYk2gmQJQwQ "View a list of compliance rules that the Code Quality Check feature follows if a bot process is published from RPA Hub."). Ensure that you complete the following tasks to publish an unattended bot process in the order that they're presented. 1. Create a bot process. For more information, see [Configuring a bot process record in RPA Hub](https://www.servicenow.com/docs/zcOQRESx0Tj3~SpRxb0GTg "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."). 2. Associate a credential group. For more information, see [Associate a credential group to a bot process in RPA Hub](https://www.servicenow.com/docs/Q9aQz~aWz93SDzrD3GRsog "Enable a robot to perform an automation in RPA Hub by mapping a credential group to an unattended bot process."). 3. Assign a robot to a bot process. For more information, see [Assign a robot to a bot process in RPA Hub](https://www.servicenow.com/docs/h2krRFDyw47vaAn9Mo3CiA "Assign a robot to an unattended bot process to execute the automation (package) that is mapped to it."). 4. Assign a process robot credential within a bot process. For more information, see [Assign a process robot credential within a bot process in RPA Hub](https://www.servicenow.com/docs/b0YwdUiKAedXqqy2E5E7~Q "Assign a process robot credential within an unattended bot process so that the selected robot can perform the automation in the Windows machine."). 5. Verify that all the assigned robots are mapped to a credential group. {#publish-bot-process__ul_mhp_2w4_dwb} Ensure that you complete the following tasks to publish an attended bot process in the order that they're presented. 1. Create a bot process. For more information, see [Configuring a bot process record in RPA Hub](https://www.servicenow.com/docs/zcOQRESx0Tj3~SpRxb0GTg "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."). 2. Assign an attended user or group to an attended bot process. For more information, see [Assign an attended user or group to an attended bot process](https://www.servicenow.com/docs/T_PrEOD1DZRdbjh_0ytgXQ "Assign an attended user or group to an attended bot process in RPA Hub, so that your user or group can access and execute this automation on Windows machines."). {#publish-bot-process__ul_egc_sw4_dwb} If you are publishing an unattended bot process that is assigned to a robot pool, then ensure that the following conditions are met: * Associate a queue to the bot process. For more information, see [c to the bot process from the related list](https://www.servicenow.com/docs/ot9exgrY74Oe2zt2ypP6Xg "Associate a queue to a bot process in RPA Hub so that the bot process can interact with this queue. You can associate a bot process to multiple queues. If the bot process is enabled for robot pool, then only one queue (that is not associated with any other bot process) can be mapped to the current bot process."). * The queue is not associated to another bot process. * The bot process is not associated with multiple queues. * Assign a process robot credential to each robots of the robot pool within a bot process. For more information, see [Assign a process robot credential within a bot process in RPA Hub](https://www.servicenow.com/docs/b0YwdUiKAedXqqy2E5E7~Q "Assign a process robot credential within an unattended bot process so that the selected robot can perform the automation in the Windows machine."). {#publish-bot-process__ul_mld_gdr_5xb} If you are publishing a bot process that is enabled with external credential, then ensure that the associated external credential vault is active. This scenario is valid if one or more Robot Credentials, Application Credentials, or TOTP Authenticators are associated with inactive External Credential Vault record. For more information about the external credential settings in Robot Credentials, Application Credentials, and TOTP Authenticators, see [Create a robot credential in RPA Hub](https://www.servicenow.com/docs/FAbWTHaH3HfSSExBoaQMaw "Create a robot credential so that the unattended robot can log in to a Windows machine and perform the automation."), [Create an application credential in RPA Hub](https://www.servicenow.com/docs/Y9HuIFnWYbcizXXMhdgXqw "Create an application credential to add the application user name and password. An unattended robot can use this application credential to log in to an application when the automation is executed."), and [Create a TOTP authenticator in RPA Hub](https://www.servicenow.com/docs/ivYWw814bNoDTtWI1Zm7eg "Map a multi-factor authentication (MFA) authenticator record with a seed in a robot credential. This mapping results in creating a Time-based One-time Password (TOTP) authenticator record in RPA Hub."). Role required: sn_rpa_fdn.rpa_release_manager, sn_rpa_fdn.rpa_developer, sn_rpa_fdn.rpa_support_user, or sn_rpa_fdn.rpa_admin ## About this task Publishing a bot process is one of the life-cycle stages of a bot process. For more information, see [Life-cycle stage statuses (LLCS) of a bot process in RPA Hub](https://www.servicenow.com/docs/p26FkAu18DyGjxaKV9Wk3g "The State transition of a bot process guides you through the stages of its life cycle."). ## Procedure 1. Navigate to AllRobotic Process AutomationRPA Hub Workspace. 2. Select the list icon (![List icon.]()). 3. On the Lists tab, under Build, select Bot Process. 4. Open a bot process that you want to publish. Tip: To modify the details of a bot process, change the life cycle stage of the bot process to In-maintenance. For more information, see [Edit a bot process in RPA Hub](https://www.servicenow.com/docs/Ej8r8rNBEifVIMduE065XQ "Edit an existing bot process in RPA Hub to modify a few details."). 5. In the form header, select Publish. Warning: After you publish a bot process, you can't change or delete the entries in the bot process form, associated business applications, robots, process credential mappings, process robot credential sets, and schedules. ## Result After you publish a bot process, the added schedule (if any) takes effect. If there is no schedule, the published bot process is ready to be triggered by the API. *[\>]: and then