About this plugin
LinkFlow integrates advanced AI like ChatGPT into WordPress for smart conversations. It seamlessly hands off to WhatsApp and social platforms when needed, not only boosting satisfaction but also helping you grow your follower count and community.
Key Features:
- 🤖 AI Chatbot Powered by ChatGPT and Leading LLMs
- 🌐 Connect to 20+ Social Platforms like WhatsApp, Messenger, Telegram, and more
- 🧠 Context-Aware Conversations to maintain natural flow
- 📋 Preset Q&A Management for FAQs and common questions
- 🔗 Shareable Chat History Links for seamless agent handoff
- 🔁 Smart Handoff Options between AI and human support
- 🎨 Custom Appearance Settings for colors, position and icon
- ⚙️ Flexible Deployment: floating button or embedded anywhere
- 🌍 Multilingual Support with auto language detection
Use Cases:
- 🛍️ E-commerce: Help with product info, guide purchases, and 24/7 support
- 🏢 Corporate Sites: Answer service questions and collect leads
- ✍️ Blogs: Recommend related content and answer reader FAQs
- 👩⚖️ Professional Services: Assist with bookings, service info, and client questions
Why LinkFlow Chat?
Unlike traditional support plugins, LinkFlow Chat offers AI + Social Media + Human Collaboration in one package. No coding required, and you can start for free!
License
This plugin is licensed under the GPLv2 or later. html.
Support
chat for help.
External services
This plugin connects to third-party AI and supporting services to provide its functionality. We disclose what is used, what is sent, and when, so you can make informed decisions.
-
com)
- What it is used for: Generates AI chat replies when OpenAI is selected as the provider.
- What data is sent: Conversation messages (roles and content, including the current user question, prior context you configure, and a system prompt containing your knowledge base), model parameters (model, max_tokens, temperature). Your API key is sent in the Authorization header.
- When data is sent: When a chat reply is requested or when you run the “Test connection” in settings.
- Terms of use: https://openai.com/policies/terms-of-use
- Privacy policy: https://openai.com/policies/privacy-policy
-
com)
- What it is used for: Generates AI chat replies when Claude is selected as the provider.
- What data is sent: Conversation messages (system, user, assistant), model parameters (model, max_tokens, temperature). Your API key is sent via the x-api-key header; anthropic-version header identifies the API version.
- When data is sent: When a chat reply is requested or when you run the “Test connection” in settings.
- Terms of use: https://www.anthropic.com/legal/terms
- Privacy policy: https://www.anthropic.com/legal/privacy
-
com)
- What it is used for: Generates AI chat replies when DeepSeek is selected as the provider.
- What data is sent: Conversation messages (roles and content), model parameters (model, max_tokens, temperature). Your API key is sent in the Authorization header.
- When data is sent: When a chat reply is requested or when you run the “Test connection” in settings.
- Terms of use: https://www.deepseek.com/terms
- Privacy policy: https://www.deepseek.com/privacy
-
com)
- What it is used for: Licensing, upgrades, and WordPress.org compliance flows for the plugin. The SDK is bundled and may communicate with Freemius if you opt into relevant functionality.
- What data is sent: As part of licensing/updates/opt-in flows, standard site and plugin metadata may be transmitted in accordance with their policies. This plugin sets the SDK to WordPress.org compliant mode.
- When data is sent: During activation/upgrade/licensing flows or when you choose Freemius-powered features.
- Terms of use: https://freemius.com/terms/
- Privacy policy: https://freemius.com/privacy/
Notes:
– You can choose which AI provider to use in settings and supply your own API key. Requests are sent directly from your WordPress site to the selected provider’s API endpoint that you configure (default endpoints listed above).
– Conversation content you submit may be processed by the selected AI provider per their terms. Do not include sensitive personal data unless you have consent and a lawful basis.
– If you disable QR code features or ensure a local QRCode script is present, CDN requests are not made.
Source code and build
org guideline.
-
Frontend chat widget (compiled to assets/dist/ ):
- Source: frontend/src/ (TypeScript/React)
- Build config files included: frontend/package.json, frontend/vite.config.ts, frontend/tsconfig.json, frontend/tsconfig.node.json, frontend/postcss.config.js, frontend/tailwind.config.js, frontend/pnpm-lock.yaml, and related styles like frontend/index.css (when present)
- Build output: assets/dist/
-
Admin UI scripts and styles:
- Human-readable JavaScript: assets/admin/js/*.js
- Human-readable CSS: assets/admin/css/*.css
Build instructions (optional – only needed if you want to rebuild the frontend bundle):
- Ensure Node.js 18+ and npm are installed.
- From the plugin directory, run:
- cd frontend
- npm install
- npm run build
- The production assets will be generated into assets/dist/ per vite.config.ts.
Notes:
– We do not ship node_modules/ in the plugin package. The included frontend/ directory contains only the source and configuration files needed to reproduce the build.
– Third-party libraries used by the frontend include React and qrcode. Their source and licenses are available in their respective repositories.