Summary
The HolderChat WordPress Connector connects your WordPress site to HolderChat: it creates a chatbot, syncs published pages and posts as knowledge, shows the chat widget on your site, and embeds the full HolderChat dashboard inside WP Admin.
Prerequisites
- WordPress site with admin access
- HolderChat Connector plugin installed and activated
- HolderChat platform (hub) reachable at holderchat.com
Architecture
| Component | Where it runs | Role |
|---|---|---|
| holderchat-connector | Your WordPress site | Setup, sync, widget, settings |
| holderchat-connector-hub | holderchat.com | Secure API bridge to Django |
| Django backend | HolderChat servers | Bot storage, AI, rebuild |
| Chat widget | Loaded from holderchat.com /dynamic/get.js | Visitor chat UI |
Your WP site → Hub REST API → Django → Chatbot knowledge
Your WP frontend → get.js widget → Django chat API
What gets synced
- Published pages and posts (default types)
- HTML converted to plain text for the knowledge base
- Unpublished, trashed, or deselected content is removed from knowledge
WordPress content is separate from dashboard Knowledge Sources (websites/files). Connector bots primarily learn from WP pages unless you add more sources in the embedded dashboard.
External service and privacy
The plugin requires holderchat.com. When you click Create Chatbot or sync runs, data is sent to HolderChat:
| Data sent to HolderChat | When |
|---|---|
| Site domain and site name | Provision |
| Page/post title, URL, plain text, modified date, language | Sync |
| Connection credentials (site ID, secret, API token) | Provision and API calls |
| Data loaded from HolderChat | When |
|---|---|
Chat widget script (get.js) and bot token | Frontend |
| Embedded dashboard URL | WP Admin Dashboard tab |
Visitor messages typed in the chat widget are sent to HolderChat for AI replies (not stored only on your WordPress server).
On first setup, the plugin shows an External service notice. Suggested privacy policy text is added to WordPress Settings → Privacy when the plugin is active. For anonymization options, see /documentation/privacy-settings/.
Plugin admin tabs
| Tab | Purpose |
|---|---|
| Setup | First-time Create Chatbot, content tree, resync, external service notice |
| Dashboard | iframe of HolderChat edit UI; Refresh dashboard if embed fails |
| Settings | Widget, auto-sync, AI chunking, debounce, account link |
What triggers a rebuild
| Event | Rebuild |
|---|---|
| Initial Create Chatbot | Yes (after full sync) |
| Edit published page (auto-sync on) | Debounced rebuild (~90s default) |
| Sync all content now | Yes |
| Toggle widget on/off | No |
Deactivation and uninstall
| Action | Local WordPress | HolderChat cloud |
|---|---|---|
| Deactivate plugin | Settings kept; widget and auto-sync stop | Bot and data remain |
| Uninstall plugin | Connection options removed from database | Bot and data remain until you delete via dashboard or contact support |
Limitations
- One bot per connected WordPress domain
- Only configured post types sync (default: page, post)
- Shortcode-only or empty pages may produce little or no knowledge
- Requires HolderChat hub and Django API online
Troubleshooting
Symptom: Plugin cannot connect
Cause: Hub unreachable or API down.
Fix: Verify holderchat.com is reachable from your server.
Symptom: Dashboard tab blank
Cause: Embed token expired or blocked by CSP.
Fix: Open HolderChat → Dashboard tab → click Refresh dashboard. Log into holderchat.com in the same browser if prompted.