Langflow Connections
The standard GamiBot setup has one tool, Langflow, and three purposes: Clarify, Summarize and Quiz. The Moodle Manager plugin owns the standard flow definitions. Administrators enter one Langflow API key under Site administration > Plugins > Local plugins > GamiBot Manager > Basic settings; they do not have to create three connections or copy flow IDs into the setup form.
The current hosted flows use Qwen3.5 served by vLLM for language generation. Course files are processed separately with Docling, embedded with the nomic-text model through Ollama, and indexed in Qdrant. The exact prompts and retrieval settings remain properties of the deployed flows.
In Manager version 2026091802, classes/local/langflow_setup.php defines:
| Purpose | Run endpoint |
|---|---|
| Clarify | https://langflow.hub.inov-norte.ipp.pt/api/v1/run/f0be7594-16a8-459e-ae96-8b79637fcbbb |
| Summarize | https://langflow.hub.inov-norte.ipp.pt/api/v1/run/28ec36b5-0432-4072-8293-607a6efe1c09 |
| Quiz | https://langflow.hub.inov-norte.ipp.pt/api/v1/run/5fad50dc-438b-4deb-ad6d-274e5d1b8a6b |
Every standard purpose uses the same Domain input TextInput-1NWCq, Course input TextInput-8xdUH and Additional input TextInput-VXxfq. The Additional input currently sends the configured number of questions for Quiz only. These IDs and URLs change with the plugin release when the standard flows change; the shared key is the administrator setting.
Existing installations keep explicit tenant assignments and custom endpoints or input IDs during upgrade. A single legacy key is migrated automatically. If legacy Langflow connections contain different keys, the existing connections keep their credentials until an administrator chooses a shared key; saving it applies that key to all Langflow connections, including custom ones. Only site administrators may edit custom Langflow endpoints, as those endpoints receive the site credential.
The configuration overview reports locally configured purposes; it does not test whether Langflow is reachable. For installation steps see Moodle setup. Course files reach a separate ingestion endpoint, with its own webhook secret and paced queue. See Core technologies for the current service stack.