--- sourceDocument: Australia Build workflows sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/build-workflows Release : - australia ft:locale : - en-US ft:publication_title : - Australia Build workflows ft:clusterId : - crworkflow bundleId : - crworkflow workflow : - Creator --- # Robotic Process Automation (RPA) Spoke # Robotic Process Automation (RPA) Spoke {#ariaid-title1} * Release version: Australia * * Updated March 12, 2026 * * ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 5 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 Robotic Process Automation (RPA) Spoke The Robotic Process Automation (RPA) Spoke in ServiceNow enables flow designers to integrate and manage attended and unattended automation processes within their workflows. This capability allows for user assignment management, work item handling in queues, process job monitoring, and bot process control through a variety of actions and subflows connected to the RPA Hub. Show full answer Show less ## Key Features * **Work Item Management:** Actions to add, update, and fetch work items in queues with support for sensitive data encryption and content size limits, ensuring secure and efficient task handling. * **User Assignment:** Assign and unassign users to attended automation processes or attended robots, facilitating dynamic user involvement in automation. * **Bot Process Lifecycle Control:** Change the lifecycle stage of bot processes (Build, Published, In Maintenance) with appropriate role permissions, and trigger start or stop commands for bot processes, including graceful stopping options. * **Process Job Monitoring:** Fetch created jobs and execution statuses to track automation progress and outcomes within RPA Hub. * **Package Version Management:** Verify the HashCode of manually uploaded automation packages to ensure integrity and import package version attachments automatically for migration between environments. * **Subflows for Automation Control:** Pre-built subflows to start and stop bot processes, import package versions, and handle process jobs, enabling streamlined automation orchestration within ServiceNow workflows. ## Practical Benefits for ServiceNow Customers * Seamlessly integrate robotic automation tasks into ServiceNow workflows, enhancing automation reach and efficiency. * Securely manage sensitive work item data with encryption capabilities, ensuring compliance and data protection. * Maintain control over bot lifecycle and execution status, enabling better governance and operational oversight of automation processes. * Utilize provided inputs and outputs to customize automation flows according to organizational needs with clear feedback on action status and results. * Automate package management and deployment across environments, reducing manual effort and errors during automation lifecycle management. With Robotic Process Automation, your flow designers can use actions to assign and unassign users to and from an attended automation process, add work items to a queue, update work items, fetch process jobs, get the status of a process job, and trigger a bot process. {#rpa-actions__id_x1k_cmt_tsb__entry__4} | Action | Description | Action inputs | Action outputs | |-|-|-|-| | Add WorkItem to Queue Action | Adds WorkItem in a specified queue in the RPA Hub application and returns the WorkItem ID. | * Queue Name: Record * Name: String * Content: String * Type: String * Priority: String.Choice * Stage: String * SLA: Date/Time {#rpa-actions__ul_rjv_jw3_jbb} The maximum limit for Content field (Request Content and Response Content) is 8000 characters. If the Is Work Item Name Sensitive check box on the associated work queue form is selected, the data in the Request Content field is encrypted. Sensitive data with encryption is stored in the work item, so that it can be passed to the RPA Desktop Design Studio or robots. | * Action Status: Object * WorkItemID: GUID * IsNameExists: Boolean * status: String * message: String {#rpa-actions__ul_epw_4w3_jbb} | | Assign User to Attended Automation Process Action | Assigns a user to the attended automation process. | * Process Name: Record * Username: Record {#rpa-actions__ul_r2y_hz3_lrb} | * Action Status: Object * status: String * Message: String {#rpa-actions__ul_awl_3z3_lrb} | | Assign User to Attended Robot Action | Assigns a user to the attended robot. | Username: Record | * Action Status: Object * status: String * Message: String {#rpa-actions__ul_xn5_25y_jsb} | | Change Life Cycle Stage Status of a Bot Process Action | Changes the life cycle stage status of a bot process that is not retired. If a bot process is in Build life cycle stage status, if you have the required role, you can update it to Published state, but you cannot update it to In Maintenance. If a bot process is in Published life cycle stage status, if you have the required role, you can update it to In Maintenance state, and vice versa. | * Process name: Record * Life cycle stage status: Choice {#rpa-actions__ul_snm_zcy_wzb} | * result: String * message: String * Action Status: Object {#rpa-actions__ul_bk2_2dy_wzb} | | Fetch Created Jobs Action | Fetches the process jobs in RPA Hub. | * Process Number: String * Robots: Array\[String\] {#rpa-actions__ul_rsb_jqy_jsb} | * Action Status: Object * Result: String * Jobs: Array\[String\] * startedRobots: Array\[String\] * pendingRobots: Array\[String\] {#rpa-actions__ul_ssb_jqy_jsb} | | Fetch Execution Status Action | Fetches the execution status of a specific process job in RPA Hub. | Process Job Number: String | * Action Status: Object * ProcessJob: Object * Process Name: String * Robot Name: String * State: String * Started At: Date/Time * Completed At: Date/Time * Message: String {#rpa-actions__ul_vk4_2ty_jsb} * status: String * message: String {#rpa-actions__ul_fj5_xz3_lrb} | | Fetch Work Item Status Action | Fetches the status of specific work queue items, asynchronously. | Work Queue Item ID: GUID | * Action Status: Object * Code: Integer * Message: String {#rpa-actions__ul_xzr_4ty_jsb} * WorkItem: Object * sysId: String * name: String * type: String * priority: String * status: String * lockedBy: String * additionalComments: String * requestContent: String * responseContent: String * deferredTill: Date/Time * sla: Date/Time * created: Date/Time * startedOn: Date/Time * completedOn: Date/Time * lastStartedTime: Date/Time {#rpa-actions__ul_ucj_tty_jsb} * status: String * message: String {#rpa-actions__ul_n25_21j_lrb} | | Start Process Action | Triggers a specific bot process in RPA Hub and returns the status. | * Process Name: Record * Robots: Array\[String\] Ignore an entry in this field if a robot pool is assigned to the bot process. When invoking the Start Process Workflow Studio action, the robots that are in the In Maintenance life-cycle stage status are treated as failed robots. {#rpa-actions__ul_qlp_n1j_lrb} | * Action Status: Object * Result: String * Robots: Array\[String\] * Process: String * Failed Robots: Array\[Object\] {#rpa-actions__ul_ojf_41j_lrb} | | Stop Process Action | Stops a bot process. If Graceful Stop is enabled, this action gracefully stops the bot process. | * Process Name: Record * Robots: Array\[String\] * Wait For Graceful Stop: True/False If this check box is selected, then bot process must stop gracefully. For more information about stopping a bot process, see [Stop an unattended bot process in RPA Hub](https://www.servicenow.com/docs/access?context=stop-bot-process&version=australia&pubname=australia-integrate-applications&ft:locale=en-US). For more information about Graceful stop, see [Using Graceful Stop functionality in RPA Hub](https://www.servicenow.com/docs/access?context=graceful-stop-rpa&version=australia&pubname=australia-integrate-applications&ft:locale=en-US). For more information about Robot Pool, see [Robot pool in RPA Hub](https://www.servicenow.com/docs/access?context=robot-pool-rpa&version=australia&pubname=australia-integrate-applications&ft:locale=en-US). {#rpa-actions__ul_j5t_sdy_wzb} | * Result: String * Action Status: Object * Robots: Array\[String\] * Process: String * Failed Robots: Array\[Object\] {#rpa-actions__ul_v43_c2y_wzb} | | Unassign User from Attended Automation Process Action | Unassigns the user from the attended automation process. | * Process Name: Record * Username: Record {#rpa-actions__ul_wvs_z5y_jsb} | * status: String * message: String * Action Status: Object {#rpa-actions__ul_fgg_q5y_jsb} | | Unassign User from Attended Robot Action | Unassigns the user from the attended robot and retires the attended robot. | Username: Record | * Action Status: Object * Status: String * Message: String {#rpa-actions__ul_p5r_s1j_lrb} | | Update Process Parameter Action | Updates the Value field for the process parameter. | * Process: Record * Parameter Name: String * Value: String {#rpa-actions__ul_nqk_c5d_qvb} | * status: String * Action Status: Object * message: String {#rpa-actions__ul_nyk_h5d_qvb} | | Update WorkItem Action | Updates work queue items. | * Queue Name: Record * WorkItemID: String * Stage: String * DefferedTill: Date/Time * Name: String * Priority: Choice * Status: Choice * Request Content: String * Type: String * Remarks: String * SLA: Date/Time * Response Content: String {#rpa-actions__ul_plc_ggk_4tb} The maximum limit for Request Content and Response Content fields is 8000 characters. If the Is Work Item Name Sensitive check box on the associated work queue form is selected, the data in the Request Content field is encrypted. Sensitive data with encryption is stored in the work item, so that it can be passed to the RPA Desktop Design Studio or robots. | * IsNameExist: True/False * Status: String * Message: String * Action Status: Object {#rpa-actions__ul_tk5_qgk_4tb} | | Verify HashCode of a Package Version | Verifies the HashCode of a package version in RPA Hub to validate the HashCode of the manually uploaded automation zip file with the associated package version record. For more information about verifying the HashCode of a package version, see [Verify the HashCode of a package version in RPA Hub](https://www.servicenow.com/docs/access?context=view-hash-code&version=australia&pubname=australia-integrate-applications&ft:locale=en-US). | Package Version: Record | * Action Status: Object * Message: String * isAttachmentValid: True/False {#rpa-actions__ul_rj4_4hq_w1c} | [Table 1. RPA actions] {#rpa-actions__id_x1k_cmt_tsb} {#rpa-actions__id_urw_cmt_tsb__entry__4} | Subflow | Description | Subflow inputs | Subflow outputs | |-|-|-|-| | Import Package Version Attachment Subflow | Imports the package version attachments automatically for a package version. To automatically migrate the package attachment (automation zip file) from a lower (non-production) to a higher (production) environment. For more information about importing a package version attachment in RPA Hub, see [Import a package version attachment in RPA Hub](https://www.servicenow.com/docs/access?context=import-attachment-package-version&version=australia&pubname=australia-integrate-applications&ft:locale=en-US). | * Email: Email * Package Version: Record {#rpa-actions__ul_qjh_wjq_w1c} | After the attachment is uploaded successfully or if an error occurs while uploading the attachment, an email notification (if email is provided as an input) is sent to the user who performs this import attachment action. | | Start Process Subflow | Triggers a specific bot process in RPA Hub. Returns process job details. | * Process Name: Record * Robots: Array\[String\] Ignore an entry in this field if a robot pool is assigned to the bot process. If a process job is not in the Running status, the robot that is associated with the process job is treated as Failed in the Start Process subflow output. {#rpa-actions__ul_a5w_v4q_lrb} | * Failed Robots: Array\[Object\] * Stopped Robots: Array\[String\] * Pending Robots: Array\[String\] * Process Jobs: Array\[String\] * Result: String * Message: String {#rpa-actions__ul_cx1_zgf_prb} | | Stop Process Subflow | Triggers a specific bot process to stop in RPA Hub. Returns robots details and process job status. If Graceful Stop is enabled, this subflow gracefully stops the bot process. | * Graceful Stop: True/False * Process Name: Record * Robots: Array\[String\] {#rpa-actions__ul_kyb_lfy_wzb} | * Failed Robots: Array\[Object\] * Stopped Robots: Array\[String\] * Pending Robots: Array\[String\] * Process Jobs: Array\[String\] * Message: String * Result: String {#rpa-actions__ul_ozb_lfy_wzb} | [Table 2. RPA subflow] {#rpa-actions__id_urw_cmt_tsb}