BitPoet Date String Helper
A Node With No Inputs That Tells You Today's Date
- datestring
BitPoet Date String Helper has no inputs and one job: output today's date as a string in yyyyMMdd format. That's the whole node. And once you've used it to stop hardcoding dates into filenames, you'll keep it around.
What it's for
The realistic use is filename stamping. Wire its datestring output into the filename_prefix of a Save Image node and every batch you run lands in a dated folder (or at least a dated filename) with zero thought. It's also handy as context for a dynamic prompt or as a marker when you're comparing outputs across sessions. It's not a wildcard and it's not clever - it's a tiny convenience, and that's okay. Not every node needs to be a diffusion model.
How it works
Under the hood it's one line: datetime.today().strftime('%Y%m%d'). Evaluated when the node runs, so it always reflects the machine's local date at execution time, and it re-evaluates on every run - a queue of twenty images all get the same stamp for that run, which is exactly what you want for a batch.
The inputs and output
There are none. No required inputs, no optional inputs. The single output is datestring (STRING), which you wire into anything that takes a string - save prefixes, prompt text, other helpers.
Installing it
Same as the rest of this pack - ComfyUI Manager (search "ComfyUI-bitpoet-IG4Inpaint"), or:
cd ComfyUI/custom_nodes
git clone https://github.com/BitPoet/ComfyUI-bitpoet-IG4Inpaint
Restart ComfyUI. No dependencies, no models. It shows up under BitPoet/helpers in the node menu.
The one gotcha: the name
Look at the class name closely: BitpotDateString. The e is missing - "BitPoet" became "Bitpot" in the registration, and it's shipped that way. In practice this only matters when you're searching: the node menu shows the display name "BitPoet Date String Helper," so you'll find it by typing "Date String" and not care. But if you ever copy a workflow or paste a class name from a forum, use BitpotDateString exactly as written or the node won't resolve. Typo aside, it works fine.
Inputs (0)
No inputs
Outputs (1)
| Name | Type | Description |
|---|---|---|
| datestring | STRING | — |