OpenAssistantGPT

OpenAssistantGPT is an AI chat bot tool. A no code builder for RAG chatbots that crawl a website and answer visitor questions through the OpenAI API, with lead capture, API actions, file analysis and embeddable widgets for WordPress, Shopify, Squarespace and Wix.

OpenAssistantGPT is a no code platform for building retrieval augmented (RAG) chatbots that answer questions from content the platform has crawled from a website. The workflow is deliberately short: point the tool at a site URL, let the crawler index the pages, and the resulting agent responds to visitor questions using that material rather than generic model knowledge. Chatbots run on the OpenAI API, with GPT-4, GPT-3.5 and GPT-4o listed as supported models. Beyond the basic crawl and answer loop, the platform adds several layers that matter to a support or sales team. Agent Actions let a bot call an API endpoint with defined URL parameters so replies can depend on live data. Web search pulls in current information the crawl has not captured. Visitors can attach files such as CSV, XML or images for the bot to analyse. A user inquiry feature collects contact details alongside a question, turning conversations into leads. SAML and SSO authentication on the Enterprise tier restricts a private bot to employees. The product targets small businesses, agencies and internal teams that want a support or sales assistant without writing code. It ships as an embeddable widget that works with WordPress, Shopify, Squarespace and Wix, and the underlying SaaS and a separate chatbot SDK are published on GitHub under an open source licence, so developers can self-host or customise instead of staying on the hosted plans. The free tier is a genuine trial rather than a working deployment: one chatbot, one crawler, three files and ten messages per month. Paid plans scale the same counters up, and customization, lead capture, chat disclaimers and white labelling arrive at the Basic and Pro levels. Compared with building on the OpenAI Assistants API directly, it trades flexibility for speed, since crawl, embed and billing are already wired together. Teams with unusual retrieval needs or strict data residency requirements will likely prefer the open source code or a bespoke build.