Title: FeelFlow Chatbot Author: FeelFlow Inc. Published: 2026-06-29 Last modified: 2026-10-27 --- Search plugins ![](https://ps.w.org/feel-chatbot/assets/banner-772x250.png?rev=3590797) ![](https://ps.w.org/feel-chatbot/assets/icon-256x256.png?rev=3590797) # FeelFlow Chatbot By [FeelFlow Inc.](https://profiles.wordpress.org/feelflow/) [Download](https://downloads.wordpress.org/plugin/feel-chatbot.1.9.1.zip) * [Details](https://tt.wordpress.org/plugins/feel-chatbot/#description) * [Reviews](https://tt.wordpress.org/plugins/feel-chatbot/#reviews) * [Installation](https://tt.wordpress.org/plugins/feel-chatbot/#installation) * [Development](https://tt.wordpress.org/plugins/feel-chatbot/#developers) [Support](https://wordpress.org/support/plugin/feel-chatbot/) ## Description **FeelFlow Chatbot** is the official plugin for connecting your WordPress site to“ FeelFlow”, the AI chat service provided by FeelFlow Inc. It places a small chat widget on your site, and an AI trained on your site’s public content (posts and pages) answers visitors’ questions automatically. This plugin is a client for a cloud-based service (SaaS). A FeelFlow account (a free plan is available) and a widget API key are required to use it. #### Key features * Automatically displays an AI chat widget on your site, with an on/off toggle. * Launcher position: bottom-right (default) or bottom-left, for sites that already have a button in the bottom-right corner. * Inline chat inside a post or page with the `[feel_chatbot]` shortcode or the “ FeelFlow Chatbot” block. Pages with the shortcode or block show the chat there instead of the floating button. * “Logged-in only” mode to show the widget to signed-in users only. * Central configuration of titles, greetings, appearance, language, position, and response settings in the FeelFlow dashboard. * Administrator-only JSON migration for existing WordPress appearance settings; no API keys or user data are exported. * Widget language (Japanese / English) — set explicitly, or auto-detected from your site language. * Provides REST endpoints so the FeelFlow backend can sync your site’s public content. #### What you need * A FeelFlow account (a free plan is available) and a widget API key, which you generate in the FeelFlow dashboard at https://chatbot.feelflow.net ### External services This plugin relies on FeelFlow, a third-party cloud-based AI chat service, to generate AI chat answers for visitors and to index your site’s public content for those answers. The plugin cannot provide its chat functionality without it. This service is provided by FeelFlow Inc.: [Terms of Service](https://id.feelflow.net/legal/terms), [Privacy Policy](https://id.feelflow.net/legal/privacy). The data sent and when it is sent are as follows. This plugin contacts the following FeelFlow domains: * `widget.chatbot.feelflow.net` – serves the chat widget’s JavaScript and CSS ( CDN). * `apiv2.chatbot.feel-flow.net` – the Chatbot API, used for AI answers, content sync, and the admin connection test. * `chatbot.feelflow.net` – the FeelFlow dashboard, where you sign up and obtain a widget API key. It is opened only when you follow the link; the plugin makes no automatic requests to it. 1. Running the chat widget 2. * The widget’s JavaScript and CSS are loaded from the CDN host widget.chatbot. feelflow.net. * When a page with the widget loads, the widget asks the Chatbot API host apiv2. chatbot.feel-flow.net for its display settings. This request carries the site’s public widget API key and the address of the page being viewed (scheme, host and path only; the query string and fragment are not sent), which is used to confirm which site the request comes from and which settings apply to the page. When the chat is shown inside a post or page (shortcode or block), the widget also loads its suggested questions at this point; that request carries only the public widget API key. * When a visitor asks a question, the question text, the conversation ID, the widget language and the site’s public widget API key are sent to the Chatbot API host to obtain an AI answer. When dashboard (central) settings are in use, the page address described above is sent as well. Files the visitor chooses to attach are also sent (attachments are available on the Standard plan or above). If the visitor has opted in to visitor memory (see below), a memory ID is sent with each question. * When a visitor rates an answer, the rating and any comment the visitor writes are sent. When a visitor sends an improvement report on an answer, the report category and short excerpts of the question and of the AI answer are sent. * When a visitor asks to contact a staff member (Enterprise plan, when enabled in the FeelFlow dashboard), short excerpts of the question and of the AI answer are sent together with any contact details the visitor chooses to enter (name, email address, phone number; all optional). * If the widget runs into an error, a technical error report (an error ID, the error details and the page address described above) is sent to the Chatbot API host so that the problem can be fixed. * Only if you turn on “Pass logged-in user attributes to the chat” (off by default): the logged-in user’s display name and role (for example “subscriber”) are also sent with the first question of each conversation (and again if they change), and kept with that conversation only. The email address, login name and user ID are never sent. * Visitor memory (only when the site owner enables it in the FeelFlow dashboard, on the Enterprise plan, and only after the visitor ticks “Remember my previous questions”): a short summary of the visitor’s earlier questions and the page attributes are stored for up to 180 days after the last visit, keyed by a hashed ID. If you turn on “Use the logged-in user as the memory unit”, the ID is a hash of the WordPress user ID made with your site’s secret keys; the user ID, login name and email address are never sent. The visitor can withdraw at any time from the chat, which deletes the stored memory. * When sent: the display-settings request (and, for the shortcode or block, the suggested-questions request) is sent each time a page with the widget (the floating button, the shortcode or the block) loads, and an error report only when an error occurs. If a visitor’s earlier request to delete their visitor memory did not complete, it is retried when a page with the widget loads. Everything else is sent only when a visitor uses the chat. 3. Content sync 4. * This plugin provides authenticated REST endpoints (/feel-chatbot/v1/posts, / pages, /server-info) that the FeelFlow backend (host apiv2.chatbot.feel-flow. net) reads. * These endpoints require a WordPress-authenticated administrator with the manage_options capability. The public widget API key, including the x-api-key and X-MCP-API- Key headers, does not authorize content sync. * Configure an administrator’s dedicated WordPress Application Password in the connection’s Basic authentication fields over HTTPS. Key-only connections return 401 after upgrading. A reverse proxy’s Basic authentication alone is not WordPress authentication. * The FeelFlow backend retrieves the body / title / excerpt / taxonomies (categories and tags) of your published posts and pages, the author information of public content (display name and email address), featured images (URL and alt text), and post custom fields (public metadata whose key does not begin with an underscore), and builds an index for AI answers. * When sent: when a connection has WordPress administrator authentication configured and FeelFlow runs a sync — started from the FeelFlow admin, or automatically on the schedule you set there (Standard plan or above). 5. Admin “API connection test” (Debug page) 6. * On the plugin’s Debug screen, clicking “API connection test” sends the configured widget API key to the Chatbot API health endpoint (path /health on host apiv2. chatbot.feel-flow.net) to verify connectivity. * When sent: only when a site administrator clicks the test button on the Debug page. Service provider and terms: * Provider: FeelFlow Inc. https://feelflow.co.jp * Terms of Service: https://id.feelflow.net/legal/terms * Privacy Policy: https://id.feelflow.net/legal/privacy ## Screenshots [⌊The WordPress connection settings page (API key, enable toggle, central-settings migration).⌉⌊The WordPress connection settings page (API key, enable toggle, central- settings migration).⌉[ The WordPress connection settings page (API key, enable toggle, central-settings migration). [⌊The chat widget displayed on the front end.⌉⌊The chat widget displayed on the front end.⌉[ The chat widget displayed on the front end. ## Blocks This plugin provides 1 block. * FeelFlow Chatbot Shows the FeelFlow Chatbot AI chat inside your content instead of the floating button. ## Installation 1. Upload and activate the plugin. 2. Open the **FF Chatbot** menu in the WordPress admin. 3. Enter the widget API key issued by FeelFlow. 4. Turn on “Enable widget” and save. 5. Visit your site; the chat widget appears in the bottom-right corner. Connection details and WordPress-only controls (logged-in-only display, permitted user attributes, visitor-memory identity) stay in this plugin. Configure titles, greetings, colors, images, language, position, labels, and prompts in the FeelFlow dashboard. For an existing installation, download the migration JSON from this plugin, review and import it in dashboard Widget Settings Installation & connection, then save. The original WordPress options are retained for compatibility until central settings are saved. To show the chat inside a post or page instead, add the `[feel_chatbot]` shortcode or the “FeelFlow Chatbot” block where you want it. ## FAQ ### Is there a cost to use it? The plugin itself is free. Generating answers and syncing content use the FeelFlow cloud service, so a FeelFlow account is required. A free plan is available, which includes up to 10 questions per month, 1 chatbot, and 10 synced documents. Paid plans with higher limits are also available. On every plan, content sync can be started from the FeelFlow admin (incremental after the first run); on the Standard plan or above it can also run automatically on a schedule you set there. See the pricing page for details: https://chatbot.feelflow.net/pricing ### Where do I get an API key? Sign in to the FeelFlow dashboard at https://chatbot.feelflow.net, open the widget settings, and generate a widget API key. Then paste that key into this plugin’s settings screen. ### The widget does not appear Make sure “Enable widget” is on and an API key has been entered. If “Logged-in only” mode is on, the widget is shown only to signed-in users. ### What does “Enable widget” control? It controls the floating chat button on every page of your site. The `[feel_chatbot]` shortcode and the “FeelFlow Chatbot” block render independently of this setting: they show the chat on the pages where you place them even when “Enable widget” is off. ### Can I move the chat button to the bottom-left? Yes. Choose bottom-left in Widget Settings in the FeelFlow dashboard. Existing WordPress position values are retained until you migrate and save central settings. ### Can I place the chat inside a post or page? Yes. Add the `[feel_chatbot]` shortcode, or insert the “FeelFlow Chatbot” block in the block editor. On that page the chat is shown in place and the floating button is not shown. The shortcode and block work even when “Enable widget” is off, so you can show the chat only on the pages where you put it. Only one chat is shown per page; an API key is required (if it is missing, users who can edit posts see a notice in its place), and “Logged-in only” mode still applies. ### Where is visitor data sent? Please see the “External services” section below. ## Reviews There are no reviews for this plugin. ## Contributors & Developers “FeelFlow Chatbot” is open source software. The following people have contributed to this plugin. Contributors * [ FeelFlow Inc. ](https://profiles.wordpress.org/feelflow/) [Translate “FeelFlow Chatbot” into your language.](https://translate.wordpress.org/projects/wp-plugins/feel-chatbot) ### Interested in development? [Browse the code](https://plugins.trac.wordpress.org/browser/feel-chatbot/), check out the [SVN repository](https://plugins.svn.wordpress.org/feel-chatbot/), or subscribe to the [development log](https://plugins.trac.wordpress.org/log/feel-chatbot/) by [RSS](https://plugins.trac.wordpress.org/log/feel-chatbot/?limit=100&mode=stop_on_copy&format=rss). ## Changelog #### 1.9.1 * Security: content sync and post counts now require WordPress administrator authentication. The public widget API key no longer authorizes content export. Before upgrading a key-only connection, configure a WordPress administrator username and dedicated Application Password over HTTPS in FeelFlow. * Docs: the “External services” section now lists exactly what the chat widget sends and when, including the page address sent when a page with the widget loads, feedback and contact requests, and error reports. * Docs: the FAQ and “External services” now mention scheduled content sync on the Pro plan or above. #### 1.9.0 * Redesigned WordPress settings with connection, installation, logged-in-only display and JSON migration cards. Appearance is configured in the dashboard; no theme selector is shown here. * Updated the plugin display name to FeelFlow Chatbot while retaining installed- plugin and saved-option identifiers. * Prevent login-only widget markup from entering shared page caches, and preserve settings when changing debug mode. #### 1.8.0 * New: manage widget presentation and response settings centrally in the FeelFlow dashboard, with a direct link from WordPress. * New: administrator and nonce protected JSON export of existing appearance settings for reviewed import in the dashboard. Credentials and visitor information are excluded. * Compatibility: original WordPress settings are retained and continue to be sent for sites without central settings. Connection details, inline placement, login controls and WordPress integrations remain available. #### 1.7.1 * Maintenance: removed retired V1 plugin notices and diagnostics. The current widget and content sync continue to work with your saved settings. #### 1.7.0 * New: “Use the logged-in user as the memory unit” setting (off by default) for the visitor memory feature. When on, a logged-in visitor’s memory follows them across devices. Only a hash of the user ID (made with your site’s secret keys) is passed; the visitor must still opt in from the chat. * New: the chat’s memory opt-in links to your site’s privacy policy page when one is set (Settings > Privacy). * Note: pages that carry the memory ID are marked as not cacheable (DONOTCACHEPAGE and no-cache headers), like the user attributes in 1.6.0. #### 1.6.0 * New: “Pass logged-in user attributes to the chat” setting (off by default). When on, the logged-in user’s display name and role are passed to the chat so answers can take them into account within the same conversation. No other personal data( such as the email address) is sent. Takes effect on the Pro plan or above; on lower plans the attributes are ignored. * Note: pages that carry the attributes are marked as not cacheable (DONOTCACHEPAGE and no-cache headers). If your caching plugin ignores DONOTCACHEPAGE and serves cached pages to logged-in users, keep this setting off — the attributes are written into the page. #### 1.5.0 * New: launcher position setting. Choose bottom-right or bottom-left; “Auto” (the default) keeps following the FeelFlow dashboard, which is bottom-right unless you change it there. * New: `[feel_chatbot]` shortcode and “FeelFlow Chatbot” block. They show the chat inside your content, and the floating button is not shown on that page. They work even when “Enable widget” is off. * Note: “Enable widget” now controls only the floating button on every page. If the API key is missing, users who can edit posts see a notice where the shortcode or block is placed; visitors see nothing. #### 1.4.0 * New: launcher button image settings. You can now replace the round chat button at the bottom right with your own image, so the button can carry your own shape, colours and wording. Wide images keep their aspect ratio. Leave it empty to keep the default button. * Note: an image with text on it does not follow the widget language setting. Prepare a separate image per language if you need one. * New: the plugin you download from your dashboard now arrives with your API key and chatbot already filled in, so it starts working as soon as you activate it. Your own settings are never overwritten if you activate it again. #### 1.3.1 * Fix: the plugin folder in the ZIP downloaded from the dashboard is now named the same as the WordPress.org one. Previously the two names differed, so WordPress treated them as separate plugins and installing the newer one alongside an older copy could make the site fail to activate it. * New: if two copies of this plugin are installed, an admin notice explains how to remove the old one without losing your settings. #### 1.3.0 * New: greeting message setting. You can now replace the first message shown when the widget opens with your own wording. Leave it empty to keep the wording that comes with the selected theme. #### 1.2.0 * New: step-by-step setup guide on the settings screen, shown until the widget is live. It starts from creating a FeelFlow account, so you can see what to do next even before you have one. * New: an admin notice after activation points you to the setup screen, instead of leaving you to find it yourself. * Improved: the link to the chatbot admin screen now carries the distribution channel, so we can tell where installs come from and fix the steps people get stuck on. #### 1.1.0 * New: widget language setting (Auto / Japanese / English). “Auto” (the default) detects the language from your site locale: Japanese sites get the Japanese widget UI, all other locales get English. The chosen language also applies to AI answers. * Behavior change: sites whose WordPress locale is not Japanese (including the default en_US) now show the widget in English when the language setting is “Auto”. Select “日本語 (Japanese)” in the settings screen to keep the previous behavior. #### 1.0.0 * Initial release for WordPress.org. * AI chat widget display (enable toggle / logged-in-only mode). * Settings for chatbot ID, label, system prompt, and theme. * Content sync REST endpoints for the FeelFlow backend. ## Meta * Version **1.9.1** * Last updated **1 көн ago** * Active installations **Fewer than 10** * WordPress version ** 6.0 or higher ** * Tested up to **7.1.4** * PHP version ** 7.4 or higher ** * Language * [English (US)](https://wordpress.org/plugins/feel-chatbot/) * Tags * [AI](https://tt.wordpress.org/plugins/tags/ai/)[chat](https://tt.wordpress.org/plugins/tags/chat/) [chatbot](https://tt.wordpress.org/plugins/tags/chatbot/)[customer support](https://tt.wordpress.org/plugins/tags/customer-support/) [faq](https://tt.wordpress.org/plugins/tags/faq/) * [Advanced View](https://tt.wordpress.org/plugins/feel-chatbot/advanced/) ## Ratings No reviews have been submitted yet. [Your review](https://wordpress.org/support/plugin/feel-chatbot/reviews/#new-post) [See all reviews](https://wordpress.org/support/plugin/feel-chatbot/reviews/) ## Contributors * [ FeelFlow Inc. ](https://profiles.wordpress.org/feelflow/) ## Support Got something to say? Need help? [View support forum](https://wordpress.org/support/plugin/feel-chatbot/)