tawk-to-api-wasp-drone — Claude Code subagent: tawk.to integration
tawk-to-api-wasp-drone — a subagent for tawk.to REST API calls: API key or OAuth2 auth, work with chats, tickets, knowledge base, and webhooks.
AGPL-3.0-or-later ★ 96 updated 2026-10-18
/plugin marketplace add legioncodeinc/vibe-coding-tools
/plugin install growth-and-customer-tools@wasp-nestWhat tawk-to-api-wasp-drone does
The subagent loads the tawk-to-api-stinger skill and calls api.tawk.to/v1 for Property, Widgets, Members, Chats, Tickets, Tabs, Metrics, Contacts, and Knowledge-Base operations. It picks Basic Auth for server scripts and OAuth2 for apps acting on behalf of a user. Before any resource call, it resolves propertyId via property.list; for knowledge base operations, it also fetches siteId from knowledge-base.site.list.
tawk.to's knowledge base accepts an ordered array of typed blocks (header, paragraph, image, code, video, divider, table), not raw markdown. Image and banner blocks need a URL: the subagent uploads files to Cloudflare R2 or DigitalOcean Spaces first, then inserts the public link into the block. Articles are published as draft, verified in the dashboard, then flipped to published via knowledge-base.article.update. The API lacks idempotency keys: retriable writes go through update, not create.
What it helps with
- integrate tawk.to REST API into an app
- create a knowledge base article from content blocks
- sync markdown files into tawk.to knowledge base with hosted images
- set up tawk.to webhooks in both directions
- fetch chat, ticket, and metrics data via API
Example prompts for the agent
- Integrate tawk.to API with Basic Auth, fetch chats for
propertyId - Build a knowledge base article from
docs/faq.md, upload images to R2 - Set up a tawk.to webhook at
/webhook/tawk, verify the signature
How to install tawk-to-api-wasp-drone
1Plugin marketplace
/plugin marketplace add legioncodeinc/vibe-coding-tools/plugin install growth-and-customer-tools@wasp-nest2Manually: put the files in place
.claude/agents/tawk-to-api-wasp-drone.mdFor all projects use ~/.claude/agents/. Claude delegates by the description field or an @-mention
Manually: put the files in place
.codex/agents/tawk-to-api-wasp-drone.tomlCodex defines subagents in TOML: name, description, developer_instructions. Move the Markdown text into developer_instructions by hand. For all projects use ~/.codex/agents/
Manually: put the files in place
.cursor/agents/tawk-to-api-wasp-drone.mdCursor also reads .claude/agents/
Step by step, with commands for each platform: Claude Code subagents: how to create one, call it and keep context clean
Questions about tawk-to-api-wasp-drone
How to install tawk-to-api-wasp-drone in Claude Code?
Run /plugin marketplace add legioncodeinc/vibe-coding-tools, then /plugin install growth-and-customer-tools@wasp-nest. The subagent will appear in .claude/agents/tawk-to-api-wasp-drone.md.
What does tawk-to-api-wasp-drone do?
The subagent calls tawk.to REST API: authenticates with an API key or OAuth2, handles chats, tickets, webhooks, and knowledge base, converts markdown into article blocks.
How does tawk-to-api-wasp-drone publish knowledge base articles?
It transforms markdown into an array of typed blocks, uploads images to Cloudflare R2 or DigitalOcean Spaces, creates the article as draft, then flips it to published after review.