Which GitHub documents can the support agent use?

Import one .md, .mdx or .txt file at a time by giving the repository and the file’s path. Each file can hold up to 50,000 characters and goes into support knowledge only. The sales agent never sees GitHub imports.

Public repositories need no token. Ask us before relying on a private repository, because access is set up on our side for each workspace.

Every import and every re-sync, even of unchanged text, saves the document unapproved, so someone checks it before the agent uses it. A sync runs only when you ask for one, from the dashboard, the REST API or the sync_github tool. Nothing syncs automatically when you push.

How does the widget go on your website?

Paste one script tag into your site, just before the closing </body> tag. It carries only your public workspace ID, and data-channel="sales" loads the sales agent instead of support. Provider keys stay on our servers and never appear in the embed.

Each agent has one label, colour and set of approved sources, so every page that loads the same embed shows the same widget. Both widgets can share a page, stacked in the bottom-right corner. Calls start only from the website origins you list, up to 10 for each agent.

The widget has no JavaScript API, SDK or npm package. The developer docs have the full snippet and the rules for allowed origins.

Can your coding tools manage the agent?

Yes. A remote MCP server and a REST API take a workspace token and work on the same records as your dashboard. Ten working MCP tools cover settings, knowledge, approval, conversations, conversation insights and installation, and get_installation returns your embed code. An eleventh, import_website, is listed but switched off. The REST API manages settings, sources, approvals, GitHub syncs and tokens, reads conversations with their transcripts and automatic insights, and returns your workspace ID, allowed origins and whether calls are on.

A token gives full management access to one workspace, so give it only to trusted tools and revoke it when you no longer need it. Adding a source never approves it, whether it comes from the dashboard, MCP or the REST API. Any token can approve, so decide who approves before you hand one over.

What doesn’t it connect to?

These aren’t available today, so plan around them before you start.

  • Help desk, CRM, calendar, Zapier or Slack connections, webhooks and custom tools or actions.
  • Website URL import, which is switched off. Add website content as a sales note instead.
  • File uploads such as PDF or Word, and Notion, Confluence or Google Docs connectors. Paste the text into a manual source instead.
  • Outbound events. To pick up new conversations, read the workspace through the REST API or MCP.

Common questions

Can I import my whole website?

Not at the moment. Website URL import is switched off in Kawl Now, so copy the website content you want the sales agent to use into sales notes, then review and approve each one before the agent can use it.

Are there ready-made help desk or CRM connectors?

No. Kawl Now imports support docs from GitHub, installs on your website with the embed, and lets your own tools manage it through MCP and the REST API. A help desk, CRM or calendar connection would need separate work, and it doesn’t send webhooks.

Do GitHub docs sync automatically when we push?

No. Kawl Now syncs a GitHub file only when you ask, from the dashboard, the REST API or the sync_github MCP tool. Every sync, even of unchanged text, sets the document back to unapproved, so someone checks it before the support agent uses it.

Can I upload PDFs or connect Notion?

No. Kawl Now has no file uploads or document connectors, so paste the text into a manual source of up to 50,000 characters, or keep it as Markdown in GitHub and import that file for the support agent.