Text Add Tokens

WAS Node Suite has its own little templating system built in - you can drop tokens like [time] or [hostname] into a filename or a saved text file and have them resolved automatically when the graph runs. The suite ships four built-in tokens out of the box: [time] (raw system microtime), [time(format_code)] (human-readable, using standard Python datetime formatting - [time(%Y-%m-%d__%I-%M%p)] gives you something like 2026-08-03__07-54PM), [hostname], and [cuda_device] / [cuda_name] for the GPU that's actually running the job. Text Add Tokens is how you extend that list with your own.

Why you'd want a custom token

The built-ins cover time and machine identity, but say you want a token for a project name, a run label, a client identifier, anything specific to your own workflow - something you'd otherwise have to retype into every filename pattern by hand. Define it once with this node and drop [yourtoken] into any filename or saved text anywhere downstream that supports token parsing - the README specifically calls out Save Text File and Save Image as the nodes that consume these tokens, alongside the built-in four.

The only real restriction, per the README, is that a token name can't contain a colon (:), since that character's reserved for the token's own syntax - and it can be a simple regular expression if you need pattern matching rather than a literal string.

Where it fits in a workflow

Typically upstream of a Save Image or Save Text File node, defining tokens once at the top of your graph so every save downstream can reference them consistently - a clean way to keep naming schemes uniform across a batch without hardcoding the same string in five different filename fields.

Installing it

Through ComfyUI Manager: search "WAS Node Suite", install, restart. Manually:

cd ComfyUI/custom_nodes
git clone https://github.com/WASasquatch/was-node-suite-comfyui
cd was-node-suite-comfyui
pip install -r requirements.txt

No external dependency specific to this node - it's part of the suite's core text/token machinery.

Troubleshooting

If a token isn't resolving in your filename, double-check it's actually reaching the Save node downstream in the graph - token definitions need to be wired into the execution path, not just floating unconnected in the workflow. And remember the colon restriction if a token name silently isn't registering.

Suite-wide, the same caution applies as everywhere in this pack: WAS Node Suite hasn't had active development since December 2023, and a ComfyUI core update occasionally breaks the whole suite's startup over a pinned legacy dependency (BLIP support is the recurring offender). If Text Add Tokens is missing from your menu entirely, check your console for an import failure before troubleshooting the token logic itself.