No-code & read-only alternatives
Not every store can run a producer package. These paths get your catalog and content into VoiceBot with no code on your side — you install something or point us at a URL, and VoiceBot does the rest. They are read-only with respect to your store: VoiceBot ingests and reads your content, and never writes back to it.
Both paths feed the same ingested catalog that every producer feeds. The conversation engine then reads it through a stable, passive provider — it answers from your data but never calls your store's API live.
WordPress / WooCommerce plugin
The recommended no-code path for WordPress stores. Install the VoiceBot sync plugin, paste a
one-time pair code, and it handles the rest — a full snapshot followed by automatic deltas as your
products and pages change. Under the hood it speaks the exact same
signed ingest protocol as the code producers (HMAC-signed pushes,
NDJSON snapshots, /events deltas), so you get the full entity coverage — products, variations,
categories, pages, menus, forms — without touching code.
This is "no-code" from your side: you never write a mapping or run a script. The plugin is the producer.
Managed crawler
The zero-integration fallback for any public site, when you can't install a plugin or run a
producer. You give VoiceBot a URL and it crawls your public pages on a schedule, building page and
menu entities from what it reads. It is deliberately conservative:
- Robots-respecting. It loads and obeys
robots.txtbefore fetching. - Sitemap-driven. It discovers URLs from your sitemap rather than guessing.
- Same-site only. Fetches are constrained to your registrable domain, with SSRF guards that reject internal/loopback hosts.
- PII-redacted. Extracted text is run through a redaction pass before it is stored.
The crawler is best for content (about pages, policies, FAQs, navigation). For a live, structured catalog — prices, stock, variations — a producer or the WooCommerce plugin is far more accurate, because it reads your real data rather than scraping rendered HTML.
How to choose
| Your situation | Use |
|---|---|
| WordPress / WooCommerce store | The WordPress/WooCommerce plugin |
| Laravel app | The Laravel producer |
| Node.js backend | The Node producer (@monoverse/voicebot-node) |
| Python backend | The Python producer (monoverse-voicebot — from source; PyPI release in progress) |
| Any other backend | A custom producer against the protocol reference |
| Can't run or install anything | The managed crawler |
Next steps
- Backend — get your catalog in — the code producers.
- Ingest Protocol Reference — what every path sends under the hood.
- Architecture — where ingest sits relative to the widget and mobile.