Short answer: there is no "Contentful chatbot plugin" — Contentful is headless, so the chatbot installs in the frontend that renders your content. Asyntai is our pick for that job in 2026: one framework-agnostic script for Next.js, Nuxt, Gatsby, Astro, Remix or plain React, answers drawn from your own published content, per-visitor language detection for multi-locale spaces, and (on Pro) a direct feed from the Contentful Content Delivery API. Chatbase, YourGPT, Voiceflow, Intercom and ChatBot.com round out the shortlist below.
Why there is no such thing as a Contentful chatbot plugin
Search for a chatbot on almost any traditional CMS and the answer is a plugin: something you install inside the admin panel, which then injects a widget into the pages the CMS generates. Contentful breaks that mental model on purpose. It is a headless content platform — a structured content repository with an API on the front of it. Your entries, assets and locales live in a Contentful space, but the HTML your visitors actually see is produced somewhere else entirely: a Next.js app on Vercel, a Nuxt app on Netlify, a Gatsby build, an Astro site, a Remix server, or a React SPA calling the Content Delivery API at runtime.
That architecture has a direct consequence for chatbots. A chat widget is a piece of the rendered page, and Contentful never touches the rendered page. So the question "which chatbot integrates with Contentful?" really splits into two separate questions, and any tool you shortlist needs a good answer to both:
- Can it embed in my frontend? The widget has to drop into whatever framework renders your Contentful content — ideally as one script tag that survives client-side routing, hydration, and static or incremental rendering without special casing.
- Can it ingest the content that lives in Contentful? Your product data, help articles, FAQs and localized copy sit behind the Content Delivery API. A chatbot that cannot reach that content will greet visitors politely and know nothing about your business.
This guide evaluates six tools against exactly those two criteria. It is written for the people who actually do this work — developers wiring a widget into a layout file, and content teams who want the bot to answer from the entries they publish — because "AI chatbot for Contentful" is a search the big vendors barely acknowledge. If you want the product-page version of the pitch, see our AI chatbot for Contentful page; what follows is the full comparison.
Quick comparison table
| Tool | Embed on a headless frontend | Getting Contentful content in | Pricing |
|---|---|---|---|
| AsyntaiEditor's pick | One JS snippet; documented setups for Next.js, Nuxt, Gatsby, Astro, Remix, React | Indexes rendered pages + direct Content Delivery API feed (Pro) | Free (100 msgs/mo); Starter $39/mo (2,500); Standard $139/mo (15,000); Pro $449/mo (50,000) |
| Chatbase | Script tag or iframe embed | Crawls site URLs, accepts document uploads | Message-credit plans; check the vendor's current pricing |
| YourGPT | Script embed | Website crawling and document ingestion | Tiered plans; check the vendor's current pricing |
| Voiceflow | Web chat widget embed after you build the agent | Knowledge base uploads and API integrations you build yourself | Builder-platform tiers; check the vendor's current pricing |
| Intercom | Messenger JS snippet | Fin AI agent draws on help-center and imported content | Per-seat plus per-resolution AI pricing; check the vendor's current pricing |
| ChatBot.com | JS widget embed | Website scan plus visual flow builder | Tiered plans; check the vendor's current pricing |
Feature and pricing notes as of July 2026. Vendors change plans often — verify on each vendor's site. Asyntai pricing is USD; EUR pricing is also available on our pricing page.
The 6 AI chatbots for Contentful sites, compared
Asyntai
Hosted AI chatbot that installs as a single script in any frontend framework and answers using your own content — including the content sitting in your Contentful space.
Asyntai treats the headless setup as the normal case rather than an edge case. The install is one async script tag placed in whatever renders your Contentful content, and the Contentful installation guide has copy-paste snippets per framework: the Script component in app/layout.tsx for Next.js (with strategy="lazyOnload" so it stays off the critical path), app.head.script in nuxt.config.ts for Nuxt, gatsby-ssr.js for Gatsby, and public/index.html or a small useEffect component for React SPAs. Because it is a client-side script that mounts after hydration, it behaves identically whether your pages are statically generated, incrementally revalidated or fully server-rendered.
On the content side, the AI answers using your own content: it indexes the pages your frontend publishes from Contentful, plus any documents you upload. For structured data — a product or faq content type, say — the Pro plan adds Real-Time Data Feed Max, which accepts a Contentful Content Delivery API URL directly. The CDA token is read-only and safe to expose, so no middleware is required for the basic feed. And since Contentful spaces are so often multi-locale, it matters that the widget detects each visitor's language and replies in it.
Pros
- One snippet, documented for Next.js, Nuxt, Gatsby, Astro, Remix and React
- Answers using your own content — pages rendered from Contentful plus uploaded docs
- Direct Contentful CDA feed for any content type (Pro plan)
- Detects and replies in each visitor's language — a fit for multi-locale spaces
- Loads after the page is interactive; no hit to Lighthouse or Core Web Vitals
- Free plan with 100 messages/month; flat pricing from $39/month, no per-seat fees
Cons
- The Contentful CDA feed sits on the Pro plan, not lower tiers
- Structured feeds in a custom shape (e.g. product cards) may need a small reshaping proxy
- No native Contentful App marketplace listing — install is frontend-side by design
Chatbase
AI chatbot builder that ingests website URLs and documents, then embeds via a script tag or iframe.
Chatbase builds an AI agent from sources you point it at — site URLs, uploaded files, pasted text — and gives you an embed code for the resulting bot. Because the embed is a plain script tag, it drops into a headless frontend the same way any third-party script does. Content from Contentful reaches it indirectly: you feed Chatbase the URLs of your rendered pages and it crawls them.
How it differs from Asyntai: Chatbase has no Contentful-aware ingestion path; structured content types reach the bot only after they have been rendered into crawlable pages. Plans are metered in message credits — check the vendor's current pricing. Asyntai adds the direct Content Delivery API feed and per-framework install docs.
Pros
- Straightforward URL and document ingestion
- Simple script/iframe embed works on any frontend
Cons
- No direct path from Contentful's API to the bot
- Message-credit metering requires watching usage
YourGPT
AI chatbot platform with website crawling, document ingestion and a script-based widget embed.
YourGPT follows a similar pattern: train an agent on crawled pages and uploaded documents, embed it with a script tag. It offers multilingual replies and a range of channel integrations. On a Contentful stack it behaves like any generic script — you place it in your frontend layout and it appears on rendered pages.
How it differs from Asyntai: like Chatbase, YourGPT sees your Contentful content only through the rendered site, not through the Content Delivery API. Its documentation is framework-generic rather than headless-specific. Pricing is tiered — check the vendor's current pricing.
Pros
- Crawling plus document upload for knowledge
- Multilingual reply support
Cons
- No Contentful API ingestion
- Generic install docs — you translate them to your framework yourself
Voiceflow
Conversation-design platform for building custom AI agents, with a web chat widget you embed once the agent is built.
Voiceflow is a different shape of product: a canvas for designing agent behavior step by step, with knowledge-base uploads and APIs that let developers wire in external data. That flexibility cuts both ways on a Contentful stack. A team with engineering time can build an agent that queries the Content Delivery API through custom functions; a team that just wants a widget answering from published content will spend days in the builder before anything ships.
How it differs from Asyntai: Voiceflow is a build-it-yourself platform; Asyntai is a deploy-it-today product. With Voiceflow, the Contentful connection is something you engineer. With Asyntai, page indexing is automatic and the CDA feed is a paste-a-URL setting. Voiceflow's tiers are platform-based — check the vendor's current pricing.
Pros
- Deep control over agent logic and integrations
- Developer APIs can reach any data source, Contentful included
Cons
- Significant build time before launch
- Contentful integration is custom work, not a built-in path
Intercom
Customer service platform whose Fin AI agent rides on the Intercom Messenger, installed via a JavaScript snippet.
Intercom is a complete support platform — inbox, help center, workflows — with the Fin AI agent layered on top. The Messenger installs on a headless frontend via a JS snippet, so the embed itself is not a problem. Fin answers from your Intercom help-center articles and content you import into the platform, which means your Contentful content typically gets duplicated into Intercom rather than read from the source.
How it differs from Asyntai: Intercom is a support suite priced per seat with additional per-resolution charges for Fin — check the vendor's current pricing. Asyntai is an AI chatbot with flat per-message pricing that reads content where it already lives: your rendered pages and, on Pro, the Contentful API itself.
Pros
- Full support platform around the AI agent
- Snippet install works on any frontend
Cons
- Per-seat plus per-resolution costs stack up
- Content usually has to be duplicated into Intercom's knowledge system
ChatBot.com
Chatbot platform combining a website-scan AI knowledge source with a visual flow builder, embedded via a JS widget.
ChatBot.com pairs an AI knowledge layer built from a scan of your website with a drag-and-drop flow builder for scripted paths. The widget embeds through a JavaScript snippet, so a headless frontend can host it without trouble. As with the other crawlers on this list, it learns your Contentful content by scanning the pages your frontend renders.
How it differs from Asyntai: ChatBot.com leans on designed flows plus a site scan; Asyntai leans on retrieval from your own content with no flow-building required, adds per-visitor language detection, and offers the direct Contentful CDA feed on Pro. ChatBot.com's plans are tiered — check the vendor's current pricing.
Pros
- Flow builder for deterministic, scripted journeys
- Website scan bootstraps the AI knowledge
Cons
- Flow design adds setup effort before value
- No Contentful-specific ingestion path
How to choose a chatbot for a headless stack
The usual chatbot checklists were written for monolithic platforms. On a Contentful stack, three criteria dominate everything else:
- Framework-agnostic embed. The widget must be one plain script that behaves in Next.js App Router and Pages Router, Nuxt, Gatsby, Astro, Remix and a bare React SPA — and keeps behaving through client-side navigation. Bonus points if the vendor documents each framework rather than handing you a snippet and a shrug. Ask specifically about hydration: a widget that mounts before hydration completes can hurt INP.
- Content ingestion that reaches Contentful. Every tool here can crawl a rendered page. The differences appear with structured content: entries that are not rendered as standalone pages, content types like
productorfaqwhose fields matter individually, and drafts vs. published states. A direct Content Delivery API path (or at minimum, clean re-crawling on publish) keeps the bot in sync with your space instead of with a stale snapshot. - Locale support that matches yours. Contentful teams tend to run more locales than average — that is often why they chose Contentful. The bot should detect the visitor's language and answer in it, drawing on whichever localized pages your frontend serves, rather than forcing one bot per locale.
Secondary questions worth five minutes each: does pricing scale with messages (predictable) or with seats and AI resolutions (less so)? Can you deploy today, or is there an agent-building phase first? And can the widget ID live in an environment variable like NEXT_PUBLIC_ASYNTAI_ID so your staging and production environments stay separate?
How to install an AI chatbot on a Contentful website
Concretely, here is the Asyntai install — the same pattern applies to any script-based widget. Full per-framework snippets live in the Contentful installation guide.
Step 1 — put the snippet in your frontend layout:
- Create a free Asyntai account and copy your embed code from the dashboard. It is a single async script tag with your widget ID.
- Add it to the file that wraps every page of the frontend rendering your Contentful content:
- Next.js: the
Scriptcomponent inapp/layout.tsx(App Router) orpages/_app.tsx(Pages Router), withstrategy="lazyOnload"so it loads after the page is interactive - Nuxt 3:
app.head.scriptinnuxt.config.ts - Gatsby:
gatsby-ssr.jsviaonRenderBody, or the load-script plugin - React SPA (CRA/Vite):
public/index.htmlbefore</body>, or a smalluseEffectcomponent - Vue 3 / static HTML calling the CDA: the plain script tag before
</body>
- Next.js: the
- Deploy or restart your dev server, open the site in an incognito window, and confirm the widget appears and answers.
Step 2 (optional, Pro plan) — feed Contentful content types to the bot directly:
- In Contentful, copy your Space ID (Settings → General settings) and create a Content Delivery API key (Settings → API keys). Use the delivery token — it is read-only and safe in a URL; never the management token.
- Note the content type ID you want to expose (Content model → the content type — e.g.
product,article,faq). - Build the feed URL:
https://cdn.contentful.com/spaces/YOUR_SPACE_ID/entries?access_token=YOUR_CDA_TOKEN&content_type=product&limit=1000 - Paste it into Real-Time Data Feed Max in your Asyntai dashboard. For product-card formatting, a small proxy (a Cloudflare Worker works well) can flatten Contentful's envelope shape; the Real-Time Data Feed Max for Contentful guide includes a ready-made example, plus the
skip-parameter pattern for spaces over 1,000 entries.
For a broader walkthrough of embedding chat on any site — headless or not — see our guide on how to integrate an AI chatbot in a website, and for what the widget itself does once installed, what an AI chat widget is.
What Contentful teams actually use a chatbot for
Documentation and help-content sites
A large share of Contentful spaces power docs, knowledge bases and marketing sites. Visitors rarely read those pages linearly — they arrive with one question. A chatbot that answers using your own published content turns a hundred help articles into a single conversational entry point, without anyone maintaining a separate FAQ tree.
Multi-locale and multi-brand estates
Teams pick Contentful precisely to run many locales or many brand sites off one content model. A widget that detects the visitor's language and answers from the localized content each frontend serves means one chatbot configuration covers the whole estate — no per-locale bot cloning.
Headless commerce catalogs
When product data lives in a product content type, "is this in stock?" and "what sizes does this come in?" are API questions, not page questions. Exposing that content type through the Content Delivery API feed lets the bot answer from live entry fields rather than from whatever happened to be rendered at build time.
Deflecting developer-facing questions
SaaS companies on Contentful-backed marketing sites field a steady drip of "does your API support X?" and "where is the changelog?" A bot that has indexed the docs answers those instantly, and the humans only see the conversations that genuinely need them.
What you'll actually pay
- Asyntai: free for 100 messages/month. Paid plans are flat: Starter $39/month for 2,500 messages, Standard $139/month for 15,000, Pro $449/month for 50,000. No per-seat fees; the Contentful Content Delivery API feed is part of the Pro plan. EUR pricing is also available — see our pricing page.
- Chatbase: message-credit plans — check the vendor's current pricing.
- YourGPT: tiered plans — check the vendor's current pricing.
- Voiceflow: builder-platform tiers, and budget the engineering hours for the agent build itself — check the vendor's current pricing.
- Intercom: per-seat plans plus per-resolution charges for the Fin AI agent — check the vendor's current pricing.
- ChatBot.com: tiered plans — check the vendor's current pricing.
One structural note for headless teams: your frontend hosting already scales with traffic, so a chatbot that meters by seat or by AI resolution adds a second, harder-to-forecast variable cost. Flat per-message pricing keeps the chat line item boring — which is what you want it to be.
Frequently asked questions
Does Contentful use AI?
Contentful offers AI features for editors — AI-assisted content generation and automation inside the editorial workspace — but it does not include a visitor-facing chatbot. If you want an AI assistant that answers questions for people browsing your site, you add a third-party chatbot to your frontend framework.
Is there a chatbot plugin for Contentful?
Not in the traditional sense, and there cannot be one. Contentful is headless: it stores and serves content over an API but never renders your pages. A chatbot must appear in the rendered page, so it installs in your frontend — Next.js, Nuxt, Gatsby, Astro, Remix or React — as a script, not as a Contentful App.
How do I add an AI chatbot to a Contentful website?
Add the chatbot's JavaScript snippet to the layout file of the frontend that renders your Contentful content: app/layout.tsx in Next.js (via the Script component), nuxt.config.ts in Nuxt, gatsby-ssr.js in Gatsby, or public/index.html in a React SPA. Deploy, and the widget appears on every route. No Contentful configuration is required.
Can the chatbot read content stored in Contentful?
Yes, two ways. First, a chatbot like Asyntai indexes the pages your frontend renders from Contentful, so published content reaches the bot automatically. Second, on the Pro plan, Asyntai's Real-Time Data Feed Max can consume a Contentful Content Delivery API URL directly, exposing any content type — products, articles, FAQs — as live structured data.
What is the best AI chatbot for Contentful in 2026?
Asyntai is our pick for Contentful-powered sites: a single framework-agnostic script for Next.js, Nuxt, Gatsby, Astro, Remix and plain React, answers using your own content, replies in the visitor's language for multi-locale spaces, and reads Contentful content types directly via the Content Delivery API on the Pro plan. Chatbase, YourGPT, Voiceflow, Intercom and ChatBot.com are the alternatives most teams shortlist.
How much does an AI chatbot for a Contentful site cost?
Asyntai has a free plan with 100 messages per month; paid plans are flat-rate — Starter $39/month for 2,500 messages, Standard $139/month for 15,000, Pro $449/month for 50,000 — with no per-seat fees. The other vendors each publish their own pricing models; check the vendor's current pricing before committing.
Conclusion
The absence of a "Contentful chatbot plugin" is not a gap in the ecosystem — it is the ecosystem working as designed. Contentful handles content; your frontend handles the page; the chatbot belongs in the frontend. Once you frame it that way, the shortlist gets simple: pick the tool whose script embeds cleanly in your framework, whose knowledge actually reaches the content in your space, and whose locale handling matches the reason you went headless in the first place.
By those criteria, Asyntai is the pick for most Contentful-powered sites in 2026 — one snippet documented for every major framework, answers drawn from your own content, per-visitor language detection, and a direct Content Delivery API feed on Pro for the structured content types that never appear as crawlable pages. Voiceflow suits teams that want to engineer a fully custom agent, Intercom suits teams buying a whole support suite, and Chatbase, YourGPT and ChatBot.com are workable generic embeds. Start with the Asyntai chatbot for Contentful, wire the snippet into your layout file, and you will have a working assistant before your next deploy finishes.