Skip to main content
The Utility node runs a fixed, deterministic helper: no AI model, no randomness. You pick one operation from a dropdown, and the node’s handles and settings reshape to match it. Same inputs always produce the same output, which makes Utility nodes the reliable glue between model-driven steps. Like other processing nodes, a Utility runs once per input item group. One incoming video extracts one audio file; three batched videos make Extract Audio run three times. If Compose Text receives lists on multiple variable handles, the combinations multiply.

​
Operations

Pick the operation from the Utility dropdown at the top of the node’s settings panel. The two available operations are:
Pulls the audio track out of a video and outputs it as a standalone audio file.
  • Input: one video — upload it directly in the panel, or connect a video output to the Video handle.
  • Output: one MP3 audio file on the Audio handle.
  • Settings: audio format (MP3) and bitrate in kbps (32–320, default 96).
  • Videos with no audio stream fail with a clear error.
Combines connected text inputs into a single text output using a reusable template.
  • Write a template and insert variables like {{input_1}}. Each variable you add creates its own text input handle on the left.
  • Use Add input to append the next variable (input_1, input_2, …) to the template automatically.
  • At run time, each variable is replaced by the text connected to its handle. The default template is {{input_1}}\n{{input_2}}.
  • Output: the composed string on the Text handle.

​
Inputs

Inputs depend on the selected operation. Extract Audio Compose Text

​
Outputs

​
Settings

​
When to use

  • Extract Audio — feed a video’s soundtrack into a transcription or audio model, or output the audio on its own.
  • Compose Text — merge several text streams (prompts, model outputs, captions) into one block with fixed wording around them, without spending a model call.

​
Connects to

  • Extract Audio: upstream a video source (an Input or model node); downstream a transcription model, audio model, or User Result node.
  • Compose Text: upstream any text-producing nodes into each variable handle; downstream a model prompt or a User Result node.
For the exact fan-out rules, see Lists & single values.
Extract Audio runs on the server and supports the node’s standalone Run action. Compose Text is resolved locally as part of the graph and does not support a single-node run.

​
Next steps

Workflow overview

How nodes, handles, and connections fit together.

User Result node

Capture a utility’s output as a workflow result.