The Python Script node

The Python Script node runs a Python script as one step of a CloudRadial AutomationAI workflow, dispatched to a Python runner. It works the same way as the PowerShell Script node, differing only in the language and the runner flavor that executes it. This article is for workspace users with the Admin role or higher who build workflows in the Designer.

• Reading Input and Emitting Output
• Configuration Fields

Reading Input and Emitting Output

Add a Python Script node from the Scripts section of the palette and edit it in the Designer's code editor. The runner SDK provides two functions:

• get_input(...) — reads the input passed to this step. Call it with a name to read one value, or with no argument to read the whole input bag (a missing key returns None).
• set_output(...) — sets this step's output. Pass a dict; it becomes the node's JSON output object.

user_id = get_input("userId")
all_input = get_input()

set_output({ "users": users, "count": 2 })

How input reaches a node and how other nodes reference this node's output are covered in the article on passing data between nodes with input and output JSON.

Configuration Fields

The Python Script node carries the same configuration fields as the PowerShell Script node:

• Name — the node's display label on the canvas
• Timeout (seconds) — how long the step may run, from 1 to 1800 seconds (default 1800)
• Retry count — how many times a failed step is retried, from 0 to 5 (default 0)
• Explicit parameters bindings — a list of name-and-expression pairs the script reads by name with get_input

The same step timeout model applies: a 5-minute default and a 30-minute hard cap. Split work that would exceed 30 minutes across multiple nodes. See the PowerShell Script node article for the full treatment of these shared fields.