Remote Desktop ActionInstall

Summary

Lists screen recordings for a remote desktop session. In 'run' mode it executes the action immediately and returns the API response containing the recordings. In 'build' mode it queues the action for later batch execution and returns the session object with the updated queued_actions list.

Inputs

• sessionId (required) — Session ID from a Session node (e.g., $json.session?.id). Used to identify the remote desktop session whose recordings are listed.
• mode — Determines whether the action runs immediately or is queued for batch execution. 'Run' executes now and returns the result; 'Build' adds the action to a queue for later execution and returns the updated session object with queued actions. Options: run (default), build.

Output shape

Depends on the mode.

When mode is 'run', the node returns the raw API response from POST /sessions/{sessionId}/run (typically an array of recording objects). When mode is 'build', the node returns an object containing session_id, queued_actions (array of queued action objects), and queued_count (number of queued actions).

Examples

Example 1: Immediately list recordings and continue processing them.

Set mode to Run (default). Provide a Session ID from a preceding Session node.

Example 2: Accumulate multiple actions (e.g., launch app, list recordings, take screenshot) and execute them later in a batch.

Set mode to Build. Connect to a Session node to provide sessionId. The node will append the screen.list_recordings action to the session's queued_actions array. A separate node (e.g., Remote Desktop Action with mode Run on a queued batch) would later process the queue.