--- 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 --- # Workflow Studio actions and subflow # Workflow Studio actions and subflow in RPA Hub {#ariaid-title1} Release version: Brazil Updated September 10, 2026 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 6 minutes to read Two-way integration of actions and subflows in Workflow Studio and RPA Hub for a seamless robot execution. ## Flows and actions overview {#rpa-hub-actions__section_gqr_gbj_lrb} The flows and actions are built using ServiceNow Workflow Studio, so make sure you're familiar with the [Building actions in Workflow Studio](https://www.servicenow.com/docs/access?context=actions&version=brazil&pubname=brazil-build-workflows&ft:locale=en-US) and [Building subflows in Workflow Studio](https://www.servicenow.com/docs/access?context=subflows&version=brazil&pubname=brazil-build-workflows&ft:locale=en-US) basics. ## Invoke flows or subflow {#rpa-hub-actions__section_aft_5gv_ksb} Invoke the flow or subflow via RPA Desktop Design Studio, Unattended Robot, or Attended Robot. For more information, see the topics listed in [Flow Designer components](https://www.servicenow.com/docs/I3yYlFaC3Sej0OKFNosczg "The Flow Designer components let you invoke flows, subflows, and actions from Workflow Studio and use them as part of a workflow. You can also use these components to determine a flow's output or execution status."). ## Enable the client callable option for a flow or subflow {#rpa-hub-actions__section_cy1_myp_w1c} Enable a client script to trigger an RPA Hub flow or subflow. For more information, see [Enable the client callable option on a flow or subflow in RPA Hub](https://www.servicenow.com/docs/S7Od9i42bcl1UXywJz4qJA "Enable a client script to trigger an RPA Hub flow or subflow."). ## RPA Hub actions {#rpa-hub-actions__section_g5y_vjh_g5b} The following table shows the detailed descriptions, action inputs, and action outputs of RPA Hub actions. {#rpa-hub-actions__table_efr_qkt_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-hub-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-hub-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-hub-actions__ul_r2y_hz3_lrb} | * Action Status: Object * status: String * Message: String {#rpa-hub-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-hub-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-hub-actions__ul_snm_zcy_wzb} | * result: String * message: String * Action Status: Object {#rpa-hub-actions__ul_bk2_2dy_wzb} | | Fetch Created Jobs Action | Fetches the process jobs in RPA Hub. | * Process Number: String * Robots: Array\[String\] {#rpa-hub-actions__ul_rsb_jqy_jsb} | * Action Status: Object * Result: String * Jobs: Array\[String\] * startedRobots: Array\[String\] * pendingRobots: Array\[String\] {#rpa-hub-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-hub-actions__ul_vk4_2ty_jsb} * status: String * message: String {#rpa-hub-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-hub-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-hub-actions__ul_ucj_tty_jsb} * status: String * message: String {#rpa-hub-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-hub-actions__ul_qlp_n1j_lrb} | * Action Status: Object * Result: String * Robots: Array\[String\] * Process: String * Failed Robots: Array\[Object\] {#rpa-hub-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/urCbR5d8TpabdgI7W6Uvvg "Stop the unattended bot process to abort the automation by the selected robot. If robot pool is enabled for a particular bot process, then the execution is stopped for all the robots of the robot pool."). For more information about Graceful stop, see [Using Graceful Stop functionality in RPA Hub](https://www.servicenow.com/docs/qO7buUTEf8w9CUEoDLp3lQ "Graceful Stop functionality provides a capability for robots to exit the automation smoothly. You can define a secure termination point within an automation process. It also enables you to perform clean-up tasks such as closing in-use applications. It is applicable for assigned robots as well as robots in a robot pool."). For more information about Robot Pool, see [Robot pool in RPA Hub](https://www.servicenow.com/docs/9HFTScMf6pPb6kCE6wD4Cg "Create a robot pool in RPA Hub to distribute and manage the workload among multiple unattended robots for unattended bot processes."). {#rpa-hub-actions__ul_j5t_sdy_wzb} | * Result: String * Action Status: Object * Robots: Array\[String\] * Process: String * Failed Robots: Array\[Object\] {#rpa-hub-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-hub-actions__ul_wvs_z5y_jsb} | * status: String * message: String * Action Status: Object {#rpa-hub-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-hub-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-hub-actions__ul_nqk_c5d_qvb} | * status: String * Action Status: Object * message: String {#rpa-hub-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-hub-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-hub-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/zdSfLHhNxIauHu3xjIgusg "Verify the HashCode of a package version in RPA Hub so that you can validate the HashCode of the manually uploaded automation zip file with the associated package version record."). | Package Version: Record | * Action Status: Object * Message: String * isAttachmentValid: True/False {#rpa-hub-actions__ul_rj4_4hq_w1c} | [Table 1. RPA actions] {#rpa-hub-actions__table_efr_qkt_tsb} ## RPA Hub subflow {#rpa-hub-actions__section_r4w_yjh_g5b} The following table shows the detailed description, action input, and action output of RPA Hub subflow. {#rpa-hub-actions__id_f1t_skt_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/S05Y3oyaUd~bspSg_KyecQ "Import package version attachments automatically instead of manually uploading a package version attachment, by selecting the Import Attachment button on a package version."). | * Email: Email * Package Version: Record {#rpa-hub-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-hub-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-hub-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-hub-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-hub-actions__ul_ozb_lfy_wzb} | [Table 2. RPA subflow] {#rpa-hub-actions__id_f1t_skt_tsb} * **[Enable the client callable option on a flow or subflow in RPA Hub](https://www.servicenow.com/docs/S7Od9i42bcl1UXywJz4qJA)** Enable a client script to trigger an RPA Hub flow or subflow.