外掛標籤
開發者團隊
原文外掛簡介
ZenQori AI Chatbot adds a lightweight chat widget to WordPress. You provide the production webhook URL from an active n8n Chat Trigger workflow and the plugin sends visitor messages directly to that endpoint.
The plugin includes its own local JavaScript and CSS. It does not load executable code from a third-party CDN.
Features:
Connect to an n8n Chat Trigger production webhook.
Custom chat title and welcome message.
Custom input placeholder and primary color.
Bottom-left or bottom-right placement.
Persistent browser session ID so n8n memory nodes can associate messages with a session.
No ZenQori account is required to use the WordPress plugin.
External service
This plugin connects to an external webhook URL configured by the WordPress administrator. It is designed for n8n Chat Trigger endpoints, which may be hosted by n8n Cloud, by the site owner, or by another hosting provider.
When the chatbot is enabled and a visitor sends a message, the visitor’s browser sends the following data to the configured webhook endpoint:
The visitor’s chat message (chatInput).
A randomly generated browser session identifier (sessionId).
The action name (sendMessage).
ZenQori does not receive or process chat messages. Messages are sent directly from the visitor’s browser to the webhook URL selected and configured by the website administrator.
Because the webhook destination is selected by the administrator, the site owner is responsible for reviewing the privacy policy, terms, data location, retention, and legal basis applicable to that endpoint and any AI/model services used by the connected workflow.
n8n website: https://n8n.io/
n8n privacy policy: https://n8n.io/legal/privacy/
n8n terms: https://n8n.io/legal/
ZenQori information: https://zenqori.com/
This plugin is an independent integration and is not affiliated with or endorsed by n8n.
Privacy
The plugin stores a randomly generated chat session identifier in the visitor’s browser local storage. It does not create a WordPress database record for visitor chat messages.
When a visitor submits a message, the message and session identifier are sent to the webhook URL configured by the site administrator. The external workflow may process, store, forward, or enrich this data depending on its configuration. Site administrators should disclose this processing in their own privacy policy where required.
