Create a client callable flow, subflow, or action

  • リリースバージョン: Australia
  • 更新日 2026年03月12日
  • 所要時間:2分
  • Enable a client script to trigger a flow, subflow, or action.

    始める前に

    • Role required: security_admin
    • Consider the implications of making a flow, subflow, or action client callable, such as whether it exposes protected data or bypasses validation logic.

    このタスクについて

    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 the design process.

    手順

    1. Elevate privileges to security_admin.
    2. Navigate to System Security > Access Control (ACL).
    3. Click New.
    4. Create an access control.
      Field Description
      Type client_callable_flow_object
      Operation execute
      Admin overrides Selected
      Name Enter a name for the ACL.
      Requires role Create a role to provide access to the APIs. For example, create a flow_api_access role.
    5. Assign the role to the user you would like to grant access to.
    6. Enable a client script to trigger the flow, subflow, or action.
      1. Open the flow, subflow, or action you want to make client callable.
      2. In the More Actions menu, select Manage security.
      3. Select Callable by Client API.
      4. Add the access control record created earlier to the ACLs field.
      5. Click Update.

    タスクの結果

    The user with the designated permissions can trigger a client callable flow, subflow, or action from a client script using the GlideFlow API.