Web Automation

1. The agent submits a workflow and receives a remote task id.
2. The task pauses while the browser workflow runs. A live browser preview can appear in the task feed.
3. When the workflow finishes (success, failure, or cancel), the agent resumes with the result and an optional screenshot.

​

Inputs

• endpoint_name: Workflow endpoint name in the browser automation service, for example verify_patient_eligibility.
• input_parameters: Key/value parameters for the workflow. An empty list is rejected because the remote workflow usually needs portal details, patient fields, or other workflow-specific inputs.

• web_ui_integration_id: Binding for a connected Web UI connector. The agent does not fill this directly — select a Web UI connection in Customer Portal Connection on the configured tool.
• secure_parameters: TOTP / authenticator material when the workflow requires MFA.
• use_proxy: Routes the workflow through a proxy when the remote service supports it.
• timeout_minutes: Maximum minutes the workflow may run. Defaults to the workspace web-automation timeout when omitted. This is also the ceiling the remote service enforces, so it must exceed the workflow’s total wall-clock time including any sleep or poll steps — a workflow that waits 20 minutes for a report needs more than 20 here. Set too low, the run is killed without reporting back and a later step fails on missing output rather than on a timeout.

​

Live browser preview

​

Web UI connector credentials

​

Admin setup

1. Basics — a stable service key (for example bswhealthplan_ui), a display name, optional icon, and enabled flag. Disabled definitions do not appear on the connectors page.
2. Validation workflow — optional workflow endpoint used to test credentials. If blank, new connections become active immediately. If set, new connections start as pending_validation until a successful callback or refresh marks them active.
3. Credential fields — the form users fill when creating a connection. Typical fields are username, password, and optionally a TOTP secret. Mark password/TOTP fields as sensitive.
4. Workflow mapping — maps saved credential fields to workflow parameters as either an input parameter or Secure TOTP.
5. Validation static params — optional non-secret constants such as portal_url, tenant, or practice_id sent only during validation.

​

TOTP mapping

{
  "name": "totp_secret",
  "label": "TOTP Secret",
  "type": "password",
  "required": false,
  "sensitive": true,
  "order": 3
}

{
  "username": "username",
  "password": "password",
  "totp_secret": {
    "parameter": "auth_code",
    "type": "totp",
    "digits": 6
  }
}

​

Configuring an agent tool

1. Open the agent’s tool configuration.
2. Add or edit a configured tool using await_web_automation_workflow.
3. Set endpoint_name to the workflow endpoint, for example practice_test_login.
4. Select the active Web UI connection in Customer Portal Connection.
5. Add input_parameters only for workflow inputs that are not credentials, such as patient_id, member_id, or date_of_service.

​

Input parameters vs connector credentials

[
  { "key": "member_id", "value": "M12345" },
  { "key": "date_of_service", "value": "2026-05-27" }
]

​

Validation status

​

When authoring agent instructions

• Name the exact endpoint_name the browser service exposes.
• List the parameters the agent must collect before calling the tool.
• Tell the agent to use ask_user when required portal credentials, patient identifiers, or MFA material are missing.
• Set timeout_minutes high enough for the portal workflow, especially when human MFA, slow payer portals, or sleep/poll steps are involved. It bounds the remote run as well as the wait, so a value below the workflow’s real runtime kills it.