Enable the client callable option on a flow or subflow in RPA Hub

  • Release version: Australia
  • Updated March 12, 2026
  • 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.

    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 and Use the InvokeSubFlow component.

    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 All > Process Automation > Workflow 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.