Press Page Button

Description

Requests that the page hosting a Web Chat widget perform a named button action. The activity sends a pressButton client action; the host page's handler decides whether to accept the request and execute the action.

Tool only: Available under Web Automation in the Conversational Agent Tools picker. It is hidden from the canvas toolbox and cannot be added as an ordinary workflow step. Supported only in Web Chat.

Prerequisites

Configure a Web Chat Trigger and Conversational Agent, embed the widget in the target page, and implement the host page's client-action handler. See Web Chat Page Actions for setup and shared tool settings.

Input

Property	Type	Required	Description
Button Name	string	Yes	Name of the requested button action. Sent as Button, with surrounding whitespace trimmed. Supports Literal, an expression, or FromAI. Use the exact name declared by the host page.

There is no confirm input, flag, or output on this activity.

Outputs

Output	Type	Description
Client Action	string	Always pressButton. Serialized as ClientAction.
Button	string	The button that was requested.
Status	string	Always Requested. The page may ask the user to confirm. Tell the user what to expect.
Error Message	string	Standard error output for a failed run.

Example successful client-action payload:

{
  "ClientAction": "pressButton",
  "Button": "submit",
  "Status": "Requested. The page may ask the user to confirm. Tell the user what to expect."
}

The widget delivers this payload unchanged as a.payload, with a.action set to pressButton.

Example

1. On the Conversational Agent's Tools connector, select Web Automation > Press Page Button.
2. Set Button Name to FromAI.
3. Instruct the agent when it should request the page's declared submit action.
4. When appropriate, the agent calls the tool with Button set to submit.
5. The host handler validates the action name and form. If the application requires confirmation, the handler presents its own confirmation control before submitting.

Confirmation belongs to the host page

Neither the activity nor the widget allowlists button names or enforces confirmation. The status text is guidance for the model, not a gate on execution. The host must implement any validation, confirmation dialog, or requirement for an actual user click.

If a host declares confirm: true in its context, that is metadata for its own handler. A handler that ignores it can execute the action immediately.

Delivery and limitations

When the input is FromAI, the pipeline builds the result JSON without resuming the workflow. A blank or missing argument returns {"error":"Missing argument Button"} and is not relayed to the page. A Literal or expression input uses the normal tool lane and emits the same client-action JSON shape.

Delivery is fire-and-forget: the host's acceptance or rejection is not returned to the agent. Status does not confirm that the button was pressed or that the operation completed. Client-action calls do not speak a tool acknowledgement, even when one is configured.

Related

• Fill Form Field
• Web Chat Page Actions