內容簡介
FeelFlow Chatbot 是一款官方外掛，能將您的 WordPress 網站連接至 FeelFlow 的 AI 聊天服務。它會在網站上顯示一個小型聊天小工具，自動回答訪客的問題，提升用戶互動體驗。
【主要功能】
• 自動顯示 AI 聊天小工具，具開關功能
• 可選擇聊天小工具的位置（右下角或左下角）
• 支援在文章或頁面內嵌入聊天功能
• 僅對已登入用戶顯示聊天小工具的模式
• 中央配置標題、問候語、外觀等設定
• 提供 REST 端點以同步網站公開內容
外掛標籤
開發者團隊
原文外掛簡介
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, Privacy Policy.
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.
Running the chat widget
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.
Content sync
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).
Admin “API connection test” (Debug page)
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
