Skip to main content

​
Knowledge Base Overview

The Woes knowledge base is the source of truth for grounded AI support. It is not just a collection of articles; it is an API context layer built from docs, specs, repositories, examples, auth rules, schemas, and endpoint-level Markdown.

​
What You Can Add

​
Source Lifecycle

1

Add a source

Use Add API Context or Sources to submit a URL, spec, repository, imported Notion page, imported Confluence space, or pasted content.
2

Watch ingestion

Woes scans the source, extracts usable content, builds Markdown, chunks it for retrieval, and publishes searchable context.
3

Attach it to agents

Use Agents to decide which agents can answer from the source.
4

Test answers

Ask realistic customer questions and verify the agent uses the right evidence.
5

Maintain coverage

Rescan sources when docs change and review Knowledge Base Gaps.

​
What Makes Good Context

  • Specific endpoint descriptions.
  • Authentication rules and examples.
  • Request and response examples.
  • Error codes and troubleshooting details.
  • SDK examples with language names.
  • Product concepts customers commonly ask about.
  • Versioning and deprecation notes.

​
Safety Rules

Do not use the knowledge base to store raw customer secrets, private tokens, or operator-only credentials. Source auth credentials used for testing are stored separately from source content and should never be copied into public docs. URL ingestion and website crawling are bounded by safe-fetch, same-origin, size, time, and request-count controls. Public docs publication is sanitized and available only for ready source material. HubSpot CRM records are different from normal knowledge-base sources: they are operator-only account context and are not used as customer-facing widget answer evidence by default.
Last modified on July 4, 2026