---
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


---

# Enable the client callable option on a flow or subflow

# Enable the client callable option on a flow or subflow in RPA Hub {#ariaid-title1}

Release version: Australia  
Updated March 12, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read  
Enable a client script to trigger an RPA Hub flow or
subflow.

## Before you begin

You must do this task in the classic environment.

Make sure that you're familiar with the RPA Hub actions and subflow.
For more information, see [Workflow Studio actions and subflow in RPA Hub](https://www.servicenow.com/docs/CYhtRggnMB2Ebn0VIHcrMQ "Two-way integration of actions and subflows in Workflow Studio and RPA Hub for a seamless robot execution.").

Invoke a flow or a subflow from Workflow Studio by using the InvokeFlow component or InvokeSubFlow component. For more information, see [Use the InvokeFlow component](https://www.servicenow.com/docs/664S~KRjPOY~lX4Gt4LTmw "Invoke or call a flow that is available in Workflow Studio by using the InvokeFlow component of RPA Desktop Design Studio. Generate the context ID of the flow and use the ID in other flow designer components to get the execution status and output.") and [Use the InvokeSubFlow component](https://www.servicenow.com/docs/P1QcTZ9GRwnDoxHMSxkZYA "The InvokeSubFlow component returns the context ID of a subflow in Workflow Studio so you can use it in other components. For example, you can use the context ID to get the execution status or the output of a subflow.").

By default, the flows, subflows, and actions can only be called by the FlowAPI within
a server script. Flow and action designers can make individual flows, subflows, or
actions available to client calls by enabling the Client callable option during
design.

Consider the implications of making a flow or subflow client callable, such as
whether it exposes protected data or bypasses validation logic.

Role required: security_admin

## Procedure

1. Navigate to AllProcess AutomationWorkflow Studio.
2. Open the flow or subflow that you want to make the client callable on.
3. In the More Actions menu, select Manage security.
4. Select Callable by Client API.
5. Add the RPA Flow Designer ACL record that you created earlier to the ACLs field.
6. Select Update.

*[\>]: and then