Knowledge
Overview
Reusable knowledge pointers for widgets, workflows, and bots—scoped per project/team.
What it is
Knowledge is your project’s shared library of reusable sources that Calypso can reference across:
- Workflows (editor) — e.g. the Knowledge bot node
- Web widgets — Q&A experiences and grounded answers
- Agents — better drafting and faster, more accurate responses
In the product UI it appears as Knowledge base: a single place to curate what the system is allowed to “know”.
What to store here (and what not to)
Store information that should be consistent, reviewable, and reusable:
- policies (refunds, hours, shipping, eligibility)
- product/plan details and pricing rules
- onboarding steps and troubleshooting playbooks
- canonical links to the “source of truth” pages
Avoid:
- secrets (API keys, credentials)
- personal data you wouldn’t want repeated in an automated reply
- rapidly-changing info with no single canonical source
Knowledge item types
Calypso supports three knowledge item types:
- Files: uploads (PDFs/docs/attachments) that go through ingestion
- Websites: curated URLs with an AI-generated summary + tags
- Q&A: curated “intent” snippets (question, objective, answer, optional action)
Each item has:
- a type (file / website / Q&A)
- a status (
activeorarchived) - tags for grouping and filtering
Scope and ownership
Knowledge is team-scoped (project-owned). In practice that means:
- you curate knowledge per team/project to avoid cross-context contamination
- workflows and bots should only pull from the knowledge items in that same scope
Recommended setup order
- Add a small set of Q&A for the critical answers you must get right (hours, pricing, refunds).
- Add websites that represent your canonical sources (docs, policies, product pages).
- Upload files for internal playbooks and long-form references.
- Connect sources in workflows using the Knowledge bot node (and keep a clean Inbox handoff boundary).