RH Anything to String

RH_Utils is the little adapter node with a big wildcard input. It takes anything - an int, a float, a seed, a string, whatever's on the wire - and spits out a string. That's it. It looks trivial, and it is, but it's the kind of node you need precisely once and then can't finish the graph without.

It ships in ComfyUI_RH_APICall, the pack that runs workflows on the RunningHub cloud and pulls the results back into your local ComfyUI. Why does a cloud-workflow pack include a type-converter? Because of how you drive those cloud workflows. You override their values with the pack's NodeInfoList node, and that override's value field is a string - even when the thing you're setting is a number like a seed or a step count. So when you've got a numeric value coming from somewhere else in your graph and you need to pipe it into an override, you run it through this node first to turn it into text the override will accept.

How it works

The input type is a literal wildcard - the pack marks it *, meaning it accepts any ComfyUI type. The node stringifies whatever it receives and outputs that text. A seed integer becomes "12345", a float becomes its text form, a string passes through as itself. There's no formatting to configure; it's a straight cast to string.

The inputs and output that matter

• anything (any type) - the value to convert. Wire in a seed, a number, a computed value, anything you want as text.

The output is STRING - the text version of that value, ready to feed into a NodeInfoList override's value field, a text combiner, a display node, or anywhere a string is expected.

Installing it

Comes with the pack, which is light to install since the generation runs on RunningHub rather than your machine:

• ComfyUI Manager: search ComfyUI_RH_APICall, install, restart.
• Manual: cd ComfyUI/custom_nodes && git clone https://github.com/HM-RunningHub/ComfyUI_RH_APICall, then restart ComfyUI.

No API key needed for this node on its own - it's pure local conversion. The key only matters once you reach the nodes that actually talk to RunningHub.

Where it fits, and where people overthink it

There's not much to break here. The one thing worth saying is why you'd bother: it exists to bridge a numeric or non-string value into a place that demands text, and in this pack that place is almost always a cloud-workflow override. If you're wiring a seed generator or a math node's output into a NodeInfoList entry and it won't connect, drop RH_Utils in between and the types line up. If you're already working with plain text, you don't need this node at all - it's only there for the conversion. Think of it as the small piece of tape that makes two otherwise-incompatible sockets fit.