Nodes/ComfyUI Telegram Suite/Any To INT πŸ”½
ComfyUI Node

Any To INT πŸ”½

The converter that restores a number after a trigger

By SwissCore92Β·Created about a year agoΒ·Updated 2 months agoΒ· 9
Any To INT πŸ”½
  • any
  • INT

Any To INT takes any input and labels its output as an INT. It's a pure type cast - the number (or whatever came in) passes through untouched. That sounds useless until you hit ComfyUI's strict type checking while trying to order your workflow with the Telegram Suite's trigger system, at which point this little node quietly saves the day.

The trigger dance, in one paragraph

The Telegram Suite uses wildcard-typed trigger inputs and outputs to force nodes to run in a specific order (see the Send Chat Action article for the full story). The problem: a trigger output is typed *, and ComfyUI won't let you plug a * wire into a port that expects INT - say, a sampler's seed. Any To INT is the bridge: feed the wildcard trigger output in, get a properly-typed INT out, wire that into your seed. Same signal, acceptable type. This direction (Any β†’ typed) is the one you'll use after a trigger output; the reverse converter, INT To Any, belongs to the old "convert before the trigger input" workflow that the README says is no longer required.

When you'd actually reach for it

  • Restoring an INT that went through a trigger, so a seed or a batch-size port accepts it.
  • Adapting a * output from any other node into an INT input without caring what the value is.
  • Generally unblocking a wire that refuses to connect because of a type mismatch.

One input (any), one output (INT), no settings. If the incoming value isn't really an integer, nothing blows up - ComfyUI is checking the declared type, and the node is telling it "this is an INT now." The value is whatever the upstream node produced.

The honest take

You will not use this node every day, and you shouldn't. It's plumbing for the pack's execution-ordering trick, and its real value is understanding why it exists: the suite ships twenty of these converters precisely because the author found triggers to be the only reliable way to control execution order, and strict typing demanded the adapters. If you never play with triggers, you'll likely never touch this node - and that's fine.

Install

The standard pack install:

cd ComfyUI/custom_nodes
git clone https://github.com/SwissCore92/comfyui-telegram-suite.git
cd comfyui-telegram-suite
pip install -r requirements.txt

Or find "ComfyUI Telegram Suite" in ComfyUI Manager. No extra dependencies, no model files - the whole converter family is just a few classes in the pack's converters.py, and install is shared across all of them.

CategoryTelegram Suite πŸ”½/converters

Inputs (1)

NameTypeDefaultDescription
any*β€”

Outputs (1)

NameTypeDescription
INTINTβ€”