Actions57
- 1. Manager Actions
- 2. Mouse Actions
- 3. Keyboard Actions
- 4. Browser Control Actions
- 5. Element Actions
- 6. Image Actions
- 7. Others Actions
- 8. Email Actions
- 9. Developer Actions
- 10. General Debug Actions
2. Mouse → move
AI-generatedSummary
Publish an MQTT request that moves the mouse cursor to screen coordinates or an XPath-selected element without clicking. Configure the target worker session with Remote Port; optionally choose a movement duration and style, and set Wait For Response to receive the worker’s reply before continuing.
Inputs
- Topic (required) — MQTT topic used to route the request to a client.
- QoS — MQTT delivery level: 0, 1, or 2; defaults to 1.
- Include Input Items — Optionally attach selected fields from incoming items as payload.inputItems. Defaults to false; specify fields such as id,name or status.detail in Include Input Fields.
- Wait For Response — When enabled, wait for an MQTT response before returning output; defaults to false. Response Timeout (sec), shown when enabled, defaults to 60.
- Delay Next Step (ms) — Delay after publishing, or after receiving the response when waiting. Defaults to rand(200,1000).
- Remote Port (required) — CDP port used to route the request to the intended worker session; defaults to the incoming item's remote_port expression.
- X and Y — Optional horizontal and vertical screen pixel coordinates. Leave either or both empty when targeting by XPath.
- XPath — Optional XPath for the target element. Use it instead of screen coordinates when moving to a page element.
- Duration (ms) — Optional duration for the mouse movement in milliseconds.
- Movement Type — Movement path style: natural (default), linear, or hesitant.
- Central Click — Boolean parameter declared for this operation; defaults to false. Despite its label and description referring to clicking, the operation is a cursor move.
Output shape
An MQTT request result, optionally including the worker response.
The operation publishes a request to the configured topic. With Wait For Response disabled, it continues after publishing; when enabled, it waits up to the configured timeout. The movement itself does not click.
