kb-and-settings

tawk.to Knowledge Base & Settings — What's Actually Possible

Be honest with the user about API coverage. tawk.to exposes only a small REST surface; most management is dashboard-only. Never pretend an API exists when it doesn't.

Supported via this plugin's MCP tools

• Reading completed chat lists (tawk_list_chats) — full per-chat transcripts are not yet available (endpoint unverified)
• Listing tickets (tawk_list_tickets)
• Listing properties (tawk_list_properties), agent identity (tawk_me)

Dashboard-only (no public API) — guide, don't fake

Area	Where in the dashboard
Knowledge base articles	Administration → Knowledge Base
Widget appearance/behavior	Administration → Channels → Chat Widget
Departments	Administration → Departments
Triggers (proactive messages)	Administration → Settings → Triggers
Shortcuts (canned replies)	Administration → Settings → Shortcuts
Webhook registration	Administration → Settings → Webhooks
Agents & roles	Administration → Property Members

For these, give the user precise click-paths and, where useful, draft the CONTENT for them (e.g. write the KB article text, trigger copy, or shortcut messages) so they only have to paste it in.

Undocumented endpoints — policy

Community reverse-engineering suggests additional RPC methods exist behind the same API (knowledge base, widget config). This plugin does NOT call them:

• They are unsupported and can break or be blocked without notice.
• If the user explicitly wants to experiment, point them at scripts/spike.mjs as a probing pattern, and make clear it is at their own risk and outside what this plugin supports.

Useful workflows to offer instead

• "Draft a KB article from recent chats": pull recent chat summaries with tawk_list_chats, identify recurring questions, write the article, give the user paste-ready content.
• "Audit ticket backlog": tawk_list_tickets by status, summarize, propose canned replies (shortcuts) the user can add in the dashboard.