LoRA Trigger Lookup (Creepybits)

The fast, offline half of the pack's LoRA-trigger pair. Where LoRA DB Builder goes out to Civitai and builds the trigger-word database, LoRA Trigger Lookup just reads it. Pick a LoRA from the dropdown, and it hands you its trigger words as a ready-to-paste string. No network, no hashing, no waiting - it's a dictionary lookup dressed as a node.

If you've catalogued your LoRAs with the builder, this node is the daily driver. Wire its trigger_words output directly into your prompt string, or use it manually as a cheat sheet that remembers things for you.

How it works

It reads the same assets/Lora_db/lora_triggers.json the builder writes, keys it by LoRA filename, and returns the stored list. Three inputs control the formatting:

• lora_name - dropdown of your LoRA files (same list the builder uses, including the "None" option).
• num_triggers - how many trigger words to output. Default -1 means all of them. Set it to 1 if you only want the primary trigger.
• delimiter - what goes between words in the output string. Default is a comma-space (, ), which is exactly what you want when pasting into a prompt.

Output is a single STRING named trigger_words. Empty string if the LoRA isn't in the database or has no stored triggers - quietly, with the reason logged to the console.

The one thing to get straight

The order of operations: builder first, lookup second. Run LoRA DB Builder once per LoRA you care about (that's what actually fetches from Civitai and populates the JSON). If you skip straight to the lookup, you'll get an empty string for every LoRA, because the database file starts effectively empty. The README's own docs frame it exactly that way: builder is the librarian, lookup is the card catalog.

Also worth knowing: the dropdown only shows the base filename of each LoRA, so two files with the same name in different subfolders are indistinguishable here. And if you edit the JSON by hand, keep it valid JSON - the node handles a missing file gracefully but doesn't repair a corrupted one.

Installing it

Part of ComfyUI-Creepy_nodes:

• ComfyUI Manager: search "Creepy_nodes" and install.
• Manual:

  cd ComfyUI/custom_nodes
  git clone https://github.com/Creepybits/ComfyUI-Creepy_nodes.git
  

Restart ComfyUI. Zero dependencies beyond the Python standard library - this is the rare node that works completely offline.

Troubleshooting

If you get empty output and the console says "LoRA not found in the database," run the builder for that LoRA first. If it says "has no listed triggers," then Civitai genuinely has no trigger words for it - check the model page, and if it's a style LoRA that doesn't need triggers, that's normal. One nice property: because the builder and lookup share one JSON file, anything you add with the builder shows up here without a ComfyUI restart.