Ino Get Lora Path Name Trigger Word

LoRA filenames are where trigger words go to hide. You download a character LoRA, glance at the file, and the activation token is buried in a name like karlakush2org_v001.safetensors - and unless you add karlakush2org to your prompt, the LoRA does almost nothing. Ino Get Lora Path Name Trigger Word does the one thing nobody wants to do by hand: it parses a LoRA file path and hands you the ID, the name, and the trigger word as separate strings.

It's a pure string utility, no network, no model loading. Give it a lora_path (a string, typically the absolute path or a rel path you already have from a download or file node) and it returns three outputs: lora_id, lora_name, and lora_trigger_word.

How it works

The mechanism is deliberately simple - and worth knowing, because it defines what this node can and can't do for you.

• lora_id is the parent folder's name (flux1dev, for example, in .../loras/flux1dev/karlakush2org_v001.safetensors).
• lora_name is the file stem - everything before the extension.
• lora_trigger_word is the filename stem split on _ and taking the first chunk.

So karlakush2org_v001.safetensors → lora_name karlakush2org_v001, trigger word karlakush2org. That works great when the convention holds (name a LoRA triggerword_anything.safetensors), which is exactly how the majority of Civitai LoRAs are named. Where it breaks: trigger words with spaces or dashes, or files named without any _ split at all. No amount of cleverness fixes those - the node trusts the filename convention.

Inputs and outputs

• lora_path - the only input, a string.

Outputs: lora_id, lora_name, lora_trigger_word - all strings.

Where it wires in

The natural pattern: you've got a LoRA path from a download node (like InoHandleDownloadModel) or a file-helper node; feed it here; route lora_trigger_word into whatever builds your prompt, and lora_name into a loader that needs a display name. It's also handy for logging - one node turns an opaque path into something you can print or save with the workflow.

Installing it

Part of ComfyUI-InoNodes. ComfyUI Manager → search "ComfyUI Ino Nodes" → install → restart. Manual:

cd ComfyUI/custom_nodes
git clone https://github.com/nobandegani/ComfyUI-InoNodes
cd comfyui_ino_nodes
pip install -r requirements.txt

Restart after. No API keys, no extra downloads - this is about as dependency-light as the pack gets. (It does want a current ComfyUI on the V3 schema, same as everything else here.)

Common issues

The big one is expecting it to read a trigger word from the model's metadata. It can't - it reads the filename. If your LoRA's trigger word isn't the first _-delimited chunk of the filename, this node will return the wrong word and your prompt will silently underperform. Also note lora_id is just the parent folder name, not a Civitai model ID - don't mistake it for something you can use in an API call. When the convention holds, it's the fastest way in the pack to keep prompts and LoRAs in sync; when it doesn't, trust the Civitai page instead.