Testing GamiBot

Install and configure both plugins first, including the shared Langflow API key, ingestion endpoint and webhook secret. Make sure Moodle cron is running.

Prepare a course

1. Open a course's Settings > GamiBot functionalities, enable Add a GamiBot Chat to this course, and save. The course must have its own GamiBot block for file ingestion.
2. Add a visible File or Folder activity containing a test document. Keep the course and section visible. Other activity types are not sent by this ingestion pipeline.
3. If the course already has File or Folder activities, enabling GamiBot queues eligible existing content. You do not need to rename or resave each document.
4. Let Moodle cron run. Uploads and edits across the whole site share a paced queue, so delivery is not necessarily immediate.

From the Moodle root, an administrator can inspect the queue:

php local/gamibot_manager/cli/sync_resources.php --status --courseid=42

Replace 42 with the course ID. If needed, php local/gamibot_manager/cli/sync_resources.php --courseid=42 queues a fresh reconciliation; cron still performs the actual delivery. A cleared queue means the receiver returned HTTP 2xx, so confirm separately that the ingestion service finished indexing the document before testing answers.

If content does not appear, check the scheduled task, its error notifications, the ingestion endpoint and secret, the queue status, and the activity's visibility or availability restrictions. See Data ingestion.

Test the chat

1. Open the GamiBot chat button in the course.
2. Select Clarify Doubts and ask a question about the indexed test document.
3. Return to the main menu, select Summarize Subject, and request a summary of the same topic.
4. Select Create Quizzes, generate a quiz about the topic, submit answers and review the result.

If all three purposes are shown as configured but requests fail, verify the shared Langflow key and the remote service. The configuration indicator is not a live connectivity test.