Add API Context

Woes answers developer questions from workspace-scoped source context. A source can be a formal API specification, a documentation site, raw Markdown, SDK examples, a connected GitHub repository, or selected pages from a connected Notion workspace. Teams can also import Confluence spaces or sync HubSpot CRM records when those integrations are connected. Start with the material your support team already trusts. The agent can only be as specific as the source context it can retrieve.

Supported Source Types

Source type	Good for
Auto-detect URL	Letting Woes inspect a URL and choose the safest ingestion path.
OpenAPI	REST endpoints, auth schemes, schemas, request bodies, responses, and examples.
JSON or spec upload	Local OpenAPI, AsyncAPI, Postman, GraphQL, or schema files.
Postman documenter	Public Postman documentation pages and collection-style endpoint groups.
Website crawl	Public docs sites where related pages should be scanned together.
Raw documentation URL	A single guide, reference page, or conceptual documentation page.
Markdown or text	Internal guides, SDK notes, support runbooks, and concise product behavior notes.
GraphQL schema	Query/mutation types, fields, arguments, and schema descriptions.
AsyncAPI	Event, message, and webhook documentation.
SOAP or gRPC docs	Service operations, request/response contracts, and integration notes.
GitHub repository	Default-branch README, docs, specs, SDK examples, and source-adjacent API guidance.
Notion pages	Product notes, FAQs, setup guides, release notes, and support playbooks shared with the Woes Notion integration.
Confluence spaces	Support runbooks, internal troubleshooting guides, release notes, and implementation notes imported from Confluence.
HubSpot CRM context	Operator-only company, contact, deal, and owner context for support triage.

Add a Source

Open Context

Go to Context in the workspace sidebar.

Choose the source type

Select the input path that best matches your material: URL, specification, raw docs, or GitHub repository.

Name the source clearly

Use a name operators will recognize later, such as Public REST API, Billing API docs, Node SDK examples, or Developer quickstarts.

Start ingestion

Woes scans the source, normalizes endpoint and document content, and builds retrieval chunks for the support agent.

Inspect the result

Open the source detail view to review endpoints, generated Markdown, documents, chunk coverage, auth readiness, and source health.

Attach the source to an agent

In Agents, attach the source to the right agent and run context learning.

Source Examples

If you have	Add it as	Helpful follow-up
`openapi.yaml` or `openapi.json`	OpenAPI or spec upload	Check generated endpoint Markdown for auth and examples.
A docs homepage	Website crawl	Keep the crawl scope to the docs domain or path you trust.
A single troubleshooting article	Raw documentation URL	Add tags or folders so operators can find it later.
A private docs repository	GitHub repository	Review the default-branch docs-like files that Woes imports before attaching the source to an agent.
A Notion support playbook	Notion integration	Share the page with the Woes integration, select it from Settings -> Integrations, then attach it to the right agent.
A Confluence runbook space	Confluence integration	Connect Confluence, import the selected space, then review the source in Context.
HubSpot account data	HubSpot integration	Sync CRM records from Settings -> Integrations and use them as operator-only context.
A support runbook	Markdown or text	Keep it concise and remove operator-only secrets before ingestion.

Source Health

Woes shows status and coverage so operators can understand what the agent knows.

State	Meaning
Pending	The source has been created and is waiting to scan.
Processing	Woes is fetching, parsing, normalizing, and chunking the source.
Ready	The source was scanned and has usable content.
Failed	Woes could not safely fetch or parse the source. Review the error and source accessibility.
No endpoints	The source may contain useful docs, but no endpoint-level reference was found.

Ready To Attach

A source is ready for an agent when:

The source status is Ready and any warnings or coverage gaps are understood.
Important endpoint paths and document titles appear in the source detail view.
Generated endpoint Markdown includes auth rules, request shape, response shape, and common errors where available.
A test search for a real customer question returns the expected page or endpoint.

Keep credentials separate from source content. Use source auth settings for test credentials instead of embedding secrets in documentation.

​Add API Context

​Supported Source Types

​Add a Source

​Source Examples

​Source Health

​Ready To Attach

Add API Context

Supported Source Types

Add a Source

Source Examples

Source Health

Ready To Attach