Knowledge Sources
Wallu answers from the knowledge you give it. The more relevant content it has, the more questions it can handle on its own.
You can mix and match three sources:
| Source | What it is | Best for |
|---|---|---|
| Documents | Websites, PDFs, text, imported Discord channels, Git repositories | The bulk of your knowledge - docs, guides, policies |
| #wallu-knowledge channel | A Discord channel your staff post answers in | Keeping answers fresh without leaving Discord |
| FAQs | Hand-written question/answer pairs | Exact, important answers and short commands |
Import your website or help center as a document, and/or use a #wallu-knowledge channel so your team can keep answers up to date right from Discord. Add a handful of FAQs only for answers that must be word-for-word.
Modern document search is very accurate, so you no longer need to hand-write an FAQ for every question. FAQs are still useful - they're just optional, and a good way to get started or to pin down exact wording.
📄 Documents
Documents are the main way to give Wallu knowledge. It reads them and extracts whatever is relevant to each question. You can add a website, paste text, import a Discord channel, or connect a Git repository.
🌐 Web Documents
Import content straight from a website - ideal for documentation sites, help centers and product pages.
- Go to Documents → "Add new document" → "Website".
- Enter the URL.
- Optionally enable "follow links on first page" to also import linked pages. Only links on the same domain are followed (
docs.example.comandexample.comcount as the same site), so links out to other sites are skipped. - Choose which channels can use this document, then save. Wallu processes it automatically.
Tips:
- Only import websites you have the rights to use.
- Some sites can't be imported: social media (YouTube, X/Twitter, Facebook, Instagram, Reddit, TikTok, Twitch, LinkedIn, ...) blocks our crawler, and Wikipedia is not allowed - other wikis work fine. Age-restricted and otherwise unsafe sites are not imported either.
- Re-import schedule: every 14 days on free plans, every 3 days on paid plans.
- Use the description field to clarify anything the page leaves implicit.
- A direct link to a PDF works as a website document too (paid plans). PDFs are re-read every 30 days, since they rarely change.
- Got a list of URLs? Use Mass-import Websites in the same dialog to add them all at once.
Firewalls are the most common cause. Allow the user agent WalluBot/1.0 (+https://wallubot.com). Our crawler's IP can change, so don't rely on IP allowlisting.
📝 Text Documents
Paste content directly - great for policies, procedures and custom guides.
- Go to Documents → "Add new document" → "Text Document".
- Paste your content, add a clear title, and choose channel access.
- Save - there's no processing delay.
You can also drop text files (.txt, .md, .yml, .json, …) into the same dialog to turn each one into a document.
Tips:
- Write full sentences and paragraphs; avoid tables, terse lists and lots of line breaks.
- Link out for things that change often (prices, dates) so the answer never goes stale.
- Include a YouTube link and Wallu pulls the video's transcript into the document, so a tutorial video becomes searchable knowledge (paid plans, see Video transcripts).
- Paste an attachment tag to have Wallu send an image or file along with the answer.
💬 Discord Documents
Import an existing channel or category so Wallu learns from real messages - this also powers the #wallu-knowledge workflow.
- Go to Documents → "Add new document" → "Discord Channel".
- Pick the channel or category and a time range (e.g. last 30 days) to skip stale content.
- Optionally filter by user or role so only trusted answers are imported (e.g. your staff role), and enable "Include referenced messages" to import the question a staff answer replies to.
- Save. Wallu re-syncs roughly every 24h (paid) or every 7 days (free) - and a change in a normally-quiet channel (e.g. an #faq or #announcements) is usually picked up automatically within the hour; run
/syncfor an immediate update.
🧑💻 Git Repositories
Connect a GitHub repository and Wallu can answer from your actual code when your documentation falls short - default values, error strings, edge cases. Private repositories are supported with a read-only token. See Git Repositories & Deep Search.
📝 FAQs (Frequently Asked Questions)
FAQs are hand-written question/answer pairs. Wallu checks them first, so they're the most predictable source - perfect for answers that must be exact.
- Open the FAQs page and click "Add FAQ".
- Write the question the way a user would ask it, plus the answer.
- Save, then test it in Discord and try a couple of rephrasings.
Keep "Advanced FAQ AI" enabled so Wallu matches paraphrased questions, and link out in the answer when details change often.
Keeping knowledge accurate
✅ Do
- Write clear, complete sentences - more context beats short keywords.
- Keep one topic per document or message.
- Link to a page for frequently changing info instead of repeating it everywhere.
- Test with real questions and refine.
❌ Avoid
- Contradictory information across sources (a common cause of wrong answers).
- Ultra-short, fragmented notes - expand them into a sentence or two.
- Stale content - remove or update anything out of date.
Troubleshooting
- Wallu can't find something? Check the content actually covers the question, and that the document shows as Processed with no errors.
- Wrong or outdated answers? Remove contradictions and update old content. FAQs override documents, so use one to force an exact answer.
- Answers too vague? Add more detail and concrete steps, or split a big topic into focused pieces.
More fixes in the troubleshooting guide. Still stuck? Join the Discord community or email [email protected].