Forerunner® AI Live Chat
Forerunner AI Live Chat provides a complete, modern chat solution for WordPress websites using n8n or another automation platform. Connect your visitors with AI-powered conversations through webhook integration while maintaining full control over your data and user experience. Key Features AI-Powered Chat – Connect to any AI service via webhook Azure Functions Ready – Full support for Azure Functions with API Key authentication Custom API Headers – Add custom authentication headers (X-API-Key, Bearer tokens, etc.) Flexible Field Mapping – Configure request/response field names for any API format Custom Bot Icons – Choose from built-in icons or upload your own Mobile-Friendly Design – Responsive interface works on all devices Easy Setup – Simple configuration with no coding required Color Customization – Match your brand colors perfectly Webhook Integration – Connect to any external AI service (n8n, Azure, AWS, custom APIs) Configurable Timeout – Set custom timeout for slow AI agents (5-120 seconds) Voice Chat Ready – Compatible with voice chat extensions How It Works Install and activate the plugin Configure your webhook URL in the settings (from n8n or any other webhook-capable service) Customize the appearance, bot name, and messages to match your brand Visitors can start chatting with your AI assistant immediately Webhook Integration This plugin sends chat messages to your specified webhook URL, allowing seamless integration with n8n (our recommended starting point) or any other webhook-capable service. Common use cases include: Azure Functions – Full support with X-API-Key authentication n8n, Zapier, Make (Integromat), or Pipedream workflows OpenAI GPT models and Azure OpenAI Service AWS Lambda with API Gateway Google Cloud Functions Custom AI services and REST APIs Customer support systems CRM integrations Azure Functions Setup For Azure Functions integration: Enter your Azure Function URL in the Webhook Endpoint field Set Authentication Type to “API Key Header” Set Header Name to “X-API-Key” (or your function’s key name) Enter your Azure Function key as the Header Value Configure the Request/Response field names to match your function’s format The plugin connects exclusively to your specified webhook URL to process chat messages. No data is sent to third-party servers without your explicit configuration. Support For support questions, please use the WordPress.org support forums. We monitor these regularly and provide assistance with setup, configuration, and troubleshooting. Privacy This plugin sends chat messages exclusively to your specified webhook URL (for example, n8n, Zapier, Make, Pipedream, or a custom service). No conversation data is stored on your website unless your webhook implementation chooses to do so. The plugin does not collect personal information beyond what visitors voluntarily enter in the chat interface. Third-Party Services This plugin may use the following external services: IP Geolocation Service (ip-api.com) – Purpose: Display visitor location information (country and city) in the admin dashboard – Data sent: Visitor IP addresses only – When: Automatically when visitors access your website with the chat widget active – Terms of Service: http://ip-api.com/docs/legal – Privacy Policy: http://ip-api.com/docs/privacy – Note: This geolocation feature helps website administrators understand their visitor demographics but does not affect the chat functionality. No personal information beyond IP addresses is transmitted to this service. OpenAI Realtime API (api.openai.com) – Purpose: Voice chat functionality for real-time audio conversations – Data sent: Audio streams and voice data during voice chat sessions – When: Only when voice chat is enabled and actively used (requires separate DFO Voice plugin) – Terms of Service: https://openai.com/terms/ – Privacy Policy: https://openai.com/privacy/ – Note: This service is only used when the DFO Voice Realtime plugin is installed and voice chat is enabled. The free version of this plugin has voice features disabled by default. DFO Voice Plugin API (local WordPress REST API) – Purpose: Generate secure tokens for voice chat sessions – Data sent: Session requests and authentication data – When: Only when DFO Voice Realtime plugin is active and voice chat is initiated – Note: This is a local WordPress REST API endpoint, not an external service. No data is sent outside your website. Credits Developed by Design for Online®. Built with WordPress best practices and community feedback in mind.
Top keywords
- chat17×2.56%
- voice14×2.11%
- service12×1.80%
- api10×1.50%
- webhook10×1.50%
- azure9×1.35%
- data9×1.35%
- voice chat8×1.20%
- custom7×1.05%
- ai6×0.90%
- com6×0.90%
- functions6×0.90%
WP SMTP Mailer – SMTP7
WP SMTP Mailer – SMTP7 allows you to configure and send all outgoing emails via a SMTP server (It works like the postman). This will prevent your emails from going into the junk/spam folder of the recipients. Go to Settings > SMTP7 and configure SMTP then post SMTP credentials. You can set the following options: Specify the from name and email address for outgoing email. Choose to send mail by SMTP or PHP’s mail() function. Specify an SMTP host (defaults to localhost). Specify an SMTP port (defaults to 25). Choose SSL / TLS encryption (not the same as STARTTLS). Choose to use SMTP authentication or not (defaults to not). Specify an SMTP username and password. SMTP Testing server : MailMug.net SMTP Testing : https://youtu.be/fAXevTJ0r8I Support : http://www.ciphercoin.com/contact/ Contact Form 7 Not Sending Emails WordPress SMTP Mailer Features Send email using a SMTP sever. You can use Gmail, Yahoo, Hotmail’s SMTP server if you have an account with them. Securely deliver emails to your recipients. Username and password encryption List of SMTP Servers (Outgoing) Gmail :- Host: smtp.gmail.com – Secure(SSL) – Port(465) Gmail :- Host: smtp.gmail.com – Secure(TLS) – Port(587) Outlook.com :- Host: smtp-mail.outlook.com – Secure(TLS) – Port(587) Office365.com :- Host: smtp.office365.com – Secure(TLS) – Port(587) Hotmail.com :- Host: smtp.live.com – Secure(TLS) – Port(587) Yahoo Mail :- Host: smtp.mail.yahoo.com – Secure(TLS) – Port(587) Yahoo Mail :- Host: smtp.mail.yahoo.com – Secure(SSL) – Port(465) Yahoo Mail Deutschland :- Host: smtp.mail.yahoo.com – Secure(SSL) – Port(465) Yahoo Mail Plus :- Host: plus.smtp.mail.yahoo.com – Secure(SSL) – Port(465) AOL.com :- Host: smtp.aol.com – Secure(TLS) – Port(587) AT&T :- Host: smtp.att.yahoo.com – Secure(SSL) – Port(465) NTL @ntlworld.com :- Host: smtp.ntlworld.com – Secure(SSL) – Port(465) BT Connect :- Host: smtp.btconnect.com – No-Encryption – Port(25) BT Openworld :- Host: mail.btopenworld.com – No-Encryption – Port(25) BT Internet :- Host: mail.btinternet.com – No-Encryption – Port(25) Orange :- Host: smtp.orange.net – No-Encryption – Port(25) Orange UK :- Host: smtp.orange.co.uk – No-Encryption – Port(25) Wanadoo UK :- Host: smtp.wanadoo.co.uk – No-Encryption – Port(25) Comcast :- Host: smtp.comcast.net – No-Encryption – Port(587) Yahoo Mail AU/NZ :- Host: smtp.mail.yahoo.com.au – Secure(SSL) – Port(465) O2 Deutschland :- Host: mail.o2online.de – No-Encryption – Port(25) zoho Mail :- Host: smtp.zoho.com – Secure(SSL) – Port(465) T-Online Deutschland :- Host: securesmtp.t-online.de – Secure(TLS) – Port(587) 1&1 (1and1) :- Host: smtp.1and1.com – Secure(TLS) – Port(587) 1&1 Deutschland :- Host: smtp.1und1.de – Secure(TLS) – Port(587) Verizon :- Host: outgoing.verizon.net – Secure (SSL) – Port(465) Verizon (Yahoo hosted) :- Host: outgoing.yahoo.verizon.net – No-Encryption – Port(587) Mail.com :- Host: smtp.mail.com – Secure(SSL) – Port(465) GMX.com :- Host: smtp.gmx.com – Secure(SSL) – Port(465) Yahoo Mail UK :- Host: smtp.mail.yahoo.co.uk – Secure(SSL) – Port(465) Airmail :- Host: smtp.airmail.net – Secure(SSL) – Port(465) Bluewin.ch :- Host: smtpauth.bluewin.ch – Secure(SSL) – Port(465) Eartlink.net :- Host: smtpauth.earthlink.net – Secure(SSL) – Port(587) iCloud Mail :- Host: smtp.mail.me.com – Secure(SSL) – Port(587) Rocketmail :- Host: smtp.mail.yahoo.com – Secure(SSL) – Port(465) Rogers :- Host: smtp.broadband.rogers.com – Secure(SSL) – Port(465) Ameritech.net :- Host: smtp.mail.att.net – Secure(SSL) – Port(465) Pacbell :- Host: smtp.mail.att.net – Secure(SSL) – Port(465) Swbell :- Host: smtp.mail.att.net – Secure(SSL) – Port(465) Bellsouth :- Host: smtp.mail.att.net – Secure(SSL) – Port(465) Flash :- Host:- smtp.mail.att.net – Secure(SSL) – Port(465) Note: These SMTP Ports and Settings may be different depending upon your Host Provider. Please contact your Web Server Host for correct details.