Published Wed Mar 25 2026 08:00:00 GMT+0800 (中国标准时间)
selectionChatwootDify
Chatwoot Captain or bolt-on Dify? Choosing your AI brain
Chatwoot's built-in Captain can reply with an LLM directly — but it trades off against a bolted-on Dify Agent Bot. Clear criteria here.
Two integration shapes#
Shape A — Built-in Captain#
- Configure model and KB inside Chatwoot
- Enable Captain on an inbox
- No new services
Shape B — External Dify as Agent Bot#
- Deploy Dify separately
- Create a Chatwoot Agent Bot pointing at Dify
- Dify owns all AI logic
6-axis comparison#
| Axis | Captain | External Dify |
|---|---|---|
| Deploy | No new component | Adds Dify |
| Workflow complexity | Simple replies | Branching, tool calls |
| Multi-LLM | Supported but limited | First class |
| KB | Basic | Rich chunking, versioned |
| Observability | Chatwoot logs | Dify trace timeline |
| Cross-product reuse | Bound to Chatwoot | Many products can call Dify |
How I decide#
Captain if:
- Team < 5, limited ops
- Needs are “doc Q&A + simple replies”
- No complex tool calls
- Pilot phase, prove ROI first
External Dify if:
- Multiple products (not just Chatwoot) consume the AI
- Complex workflows (orders, refunds, escalation)
- Multiple LLMs co-exist (model per scenario)
- KB needs strict versioning
Migration path#
The common path is Captain → Dify. Validate ROI with Captain, scale up with Dify.
To migrate:
- Copy Captain’s assistant prompt into a Dify chatbot
- Export the Chatwoot Help Center docs and import into a Dify dataset
- Turn Captain off on the inbox, enable Agent Bot pointing at Dify
Usually under a day.