export_file
Export a Houdini node’s output to a specified file path, optionally across a frame range, and report whether files were actually written or changed.
Instructions
Export a node's output to a file on disk, and report whether it landed.
SOPs are saved directly, LOPs export their USD stage, and a /out ROP is
pointed at file_path and executed (its own output path is restored
afterwards). Reports wrote_files, so success: True means a file appeared
or changed -- not merely that the call returned. A frame_range writes
name.0001.ext per frame and leaves the playbar where it was. A missing
directory is created, as a ROP or a USD export does.
Args: node_path: Path to the node to export. file_path: Destination file path; variables ($JOB) are expanded. For a ROP this overrides its output parameter for the duration of the export. frame_range: Frame range as [start, end] or [start, end, step].
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"node_path": "<node_path>",
"file_path": "<file_path>"
},
"name": "export_file"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| file_path | Yes | ||
| node_path | Yes | ||
| frame_range | No |