SuperBot AI Chatbot & Live Chat

Descrição

SuperBot AI adds the SuperBot support chat widget to a WordPress site. The widget is configured from your SuperBot workspace at superbotapp.ai, where your full inbox, knowledge, automations, CRM, team, analytics, integrations, and billing tools live.

For WooCommerce, the plugin also exposes secure, read-only feeds that SuperBot can use for product and order-aware support. The catalog supports pagination and optional variation details; order lookup requires both the order number and the exact billing email.

Features

  • One-field widget setup: paste your SuperBot Site ID and the chat widget appears on your public site.
  • Enable/disable switch and per-page hiding by slug or ID.
  • Secure store metadata, catalog, and order-status feeds with a site-specific token.
  • Catalog paging, categories, prices, stock state, images, URLs, SKUs, and optional variants.
  • Order lookup by the order number your customer actually has, including stores that use sequential order numbers.
  • WooCommerce High-Performance Order Storage (HPOS) compatibility.
  • Feed token rotation from WordPress admin if a URL is ever shared accidentally.
  • Works without WooCommerce too: the catalog feed then exposes posts and pages, while order lookup stays disabled.

What the plugin does not do

It stores no customer conversations in your database, creates no tables, and does not track your visitors. It stores three options: your settings, one read-only feed token and the version that last reported its connection. Uninstalling removes all three.

External services

This plugin connects to SuperBot at superbotapp.ai to provide the chat widget.

  • What it does: after you enter a Site ID and enable the widget, public pages load the SuperBot widget script. Messages typed by visitors are sent to and processed by SuperBot.
  • What data is sent and when: no data is sent until you add a Site ID. After that, public pages load the widget when it is enabled, and the plugin sends a short connection notice to superbotapp.ai/api/plugin/status when you save or change the Site ID, once after each plugin update, and when you deactivate or delete the plugin. The notice contains only the event, your Site ID, your site address, and the plugin, WordPress and WooCommerce versions, so your SuperBot dashboard knows which sites are connected. Store feeds are only read when you explicitly copy their private URLs into your SuperBot configuration.
  • Service provider: SuperBot – terms of service, privacy policy.

Imagens de tela

Instalação

  1. Install and activate the plugin through the WordPress Plugins screen, or upload the superbot folder to /wp-content/plugins/.
  2. Sign in at superbotapp.ai and open Dashboard -> Setup Guide to copy your Site ID.
  3. In WordPress, go to SuperBot AI, paste the Site ID, enable the widget, and save.
  4. Optional: copy the Store metadata, Products, and Orders API URLs into SuperBot Dashboard -> Settings -> AI Connect.
  5. Keep those URLs private. If one is ever shared, rotate the feed token from the SuperBot AI settings page and update the dashboard connection.

FAQ

Do I need a SuperBot account?

Yes. The widget and all SuperBot product features are configured in your SuperBot workspace at superbotapp.ai.

Does this work without WooCommerce?

Yes. The chat widget works on any WordPress site. Without WooCommerce, the catalog feed shares published posts and pages, and order lookup is unavailable.

Is customer order data protected?

The feed requires a site-specific private token. It returns order details only when the caller supplies both an order number and the exact billing email. It never returns addresses, payment details, or the billing email itself. Order lookups are also rate limited per IP address, so a leaked token cannot be used to guess which email belongs to which order.

Can I send the token as a header instead of in the URL?

Yes, and it is the better option. Every endpoint accepts X-Superbot-Token. The ?token= form still works because existing connections were set up that way, but a token in a query string ends up in server and proxy access logs.

Does the plugin call external services?

Only after you add a Site ID: public pages then load the widget from superbotapp.ai and visitor chat messages are processed by SuperBot, and the plugin sends a short connection notice (event, Site ID, site address, versions) when you connect, update, deactivate or delete it. See External services.

Can I hide the chat on certain pages?

Yes. Enter comma-separated page slugs or IDs in “Hide on specific pages”.

Can I control where the widget appears in code?

Yes. Return false from the superbot_ai_show_widget filter to suppress it for a request, and use superbot_ai_product_feed_item to adjust a product before it is sent.

Avaliações

There are no reviews for this plugin.

Contribuidores e desenvolvedores

“SuperBot AI Chatbot & Live Chat” é um software com código aberto. As seguintes pessoas contribuíram para este plugin.

Contribuidores

Registro de alterações

1.3.2

  • The settings screen now opens with a three-step checklist (connect your SuperBot account, widget showing on your site, train your AI), each with its status and one button, so it is always clear what to do next.

1.3.1

  • After a site has been connected for a week, the SuperBot AI settings screen shows a one-time note asking for a WordPress.org review. It appears only on the plugin’s own screen, never elsewhere in wp-admin, and either button hides it for good. Nothing is unlocked or withheld either way, and no data is sent.

1.3.0

  • Your SuperBot dashboard now knows which sites are connected: after you add a Site ID, the plugin sends a short connection notice when you connect, update, deactivate or delete it. Nothing is sent before a Site ID is set. Details under External services.

1.2.2

  • Declares compatibility with the WooCommerce block-based Cart and Checkout, so WooCommerce no longer flags SuperBot as incompatible with the default checkout. The plugin does not modify cart or checkout.
  • Adds WooCommerce version headers (tested up to WooCommerce 11.1).
  • Order lookup by a customer-facing order number (from sequential-numbering plugins) now works on stores using the legacy order storage. WooCommerce ignored the previous query there and logged a “called incorrectly” notice; HPOS stores were unaffected.

1.2.1

  • Text domain is now superbot, matching the plugin slug, so the directory can translate the plugin.
  • The failed-order-lookup counter is incremented with a single atomic database statement instead of a read-then-write, so concurrent misses cannot slip past the limit.

1.2.0

  • The widget script is now enqueued through WordPress instead of printed into the footer, so caching and optimisation plugins can recognise it.
  • Admin CSS and JavaScript moved into enqueued asset files; no inline style, script, or event-handler attributes remain.
  • Order lookup now resolves the customer-facing order number, not only the post ID, so stores using sequential order numbers work.
  • Order lookups are rate limited per IP address.
  • The catalog feed now honours page and per_page without WooCommerce; previously it always returned the 100 most recent items.
  • The REST permission check no longer creates a feed token, so an unauthenticated request can no longer cause a database write.
  • Token rotation confirmation no longer travels in a URL parameter.
  • Tested against WordPress 7.1.

1.1.0

  • Added store metadata endpoint, catalog pagination, public catalog fields, optional variant details, and HPOS-safe store data handling.
  • Added feed token rotation and a shared-dashboard connection status card.

1.0.0

  • Initial release: widget injection, settings page, secure products and order-status feeds for AI Connect.