Inletbase is a hosted platform for collecting website form submissions and running AI chatbots. You create a form or train a chatbot in the Inletbase dashboard, and everything your site collects arrives in one place where you can read it, reply to it, and keep track of your leads.
This plugin is the official WordPress integration for that platform. Inletbase works with any site that can make an HTTP request, including plain HTML, React, Next.js and Framer, so WordPress is one of several ways to connect. If your site runs on WordPress, this plugin is the shortest route: it connects the forms you already have and installs the chat widget for you, with no theme file to edit and no script to paste.
Collect WordPress form submissions. Point a form on your site at an Inletbase form and each submission is saved to your workspace, along with the page it came from.
Manage your leads in one place. Read submissions, reply by email, set up notifications and workflows, and view everything from every connected site together.
Connect the forms you already have. There is nothing to rebuild. The plugin reads the forms on your site and their fields, then walks you through matching them to your Inletbase form.
Add an AI chatbot to your site. Choose a chatbot you have trained in the dashboard and activate it. The plugin registers your domain and loads the widget.
The plugin talks to Inletbase from your server rather than from the visitor’s browser. Your API key is stored in your WordPress database and sent from PHP, so it never appears in your page source or in the browser console.
For forms, it hooks into the form builders it recognises and captures each submission on the server as the builder processes it. That keeps working when a page is cached, when a theme changes its markup, and when JavaScript is turned off. Your form behaves exactly as it did before: it still sends its own email notifications and still saves its own entries. Inletbase receives a copy of the fields you chose to map.
If a delivery to Inletbase fails for a temporary reason, the submission is queued and WordPress retries it in the background, so a short network problem does not cost you the lead.
For chatbots, activating a bot registers your site domain with Inletbase and adds the widget script to your site footer. One chatbot is live at a time.
The WordPress plugin guide covers each step in detail, including how to connect a custom or hand-coded form with a CSS selector, and what to do if a caching plugin hides the widget. The rest of the Inletbase documentation covers the dashboard side, such as training a chatbot and setting up email notifications.
You need an active Inletbase account, and a form or trained chatbot in your dashboard, before the plugin has anything to connect to. You can create an account at no cost.
The plugin detects forms and reads their fields automatically for:
Submissions from these builders are captured on your server. Elementor forms are matched by their Form Name, so give each Elementor form a name of its own.
Any other form can be connected by hand with a CSS selector, including:
If you maintain client websites, submissions usually end up spread across different inboxes, and a broken email setup on one site can go unnoticed for weeks. Connecting each site to the same Inletbase organisation puts every submission in one dashboard, so you can check them together and give each client access to their own.
Start with the WordPress plugin guide, which includes how to find a CSS selector and the HTML name attribute of a field in the common builders. For anything else, see the documentation or get in touch.
This plugin connects your WordPress site to Inletbase (https://inletbase.com), a third-party Software-as-a-Service platform operated by Byteonic Labs. An active Inletbase account and API key are required for the plugin to function. The plugin cannot capture form data or deploy chatbots without connecting to this external service.
What the plugin sends to Inletbase, and when:
https://inletbase.com/api/v1). Alongside the mapped fields, the plugin sends a small metadata object containing the page URL where the form was submitted, the visitor’s browser user-agent string, and identifiers noting the submission came from the WordPress plugin. This transmission happens at the moment of submission. The same endpoint is used from your WordPress admin to list your forms and chatbots and to register your site’s domain for chatbot whitelisting.https://api.inletbase.com/widget/chatbot.js) on your site’s front end. Visitor messages typed into the chatbot and the AI responses are processed through the Inletbase backend. Your site’s domain is registered with Inletbase for whitelisting when you activate a bot.https://inletbase.com/connect/wordpress to sign in and approve the connection. After you approve, your WordPress server exchanges a single-use code at https://inletbase.com/api/apps/wordpress/exchange to receive a newly generated API key for this site. Only the site URL and a short-lived code are exchanged; no visitor data is involved in this step.Use of the Inletbase service is governed by its Terms of Service and Privacy Policy:
Inletbase transmits form submission data and chatbot conversation messages to the Inletbase platform (https://inletbase.com) via a secure HTTPS connection. For forms, the data from the fields you explicitly map is transmitted, together with metadata about each submission: the page URL it was submitted from, the visitor’s browser user-agent, and identifiers indicating the submission originated from this WordPress plugin. For chatbots, visitor messages and AI responses are processed through the Inletbase backend, and your site domain is registered for widget whitelisting.
You are responsible for disclosing this data processing to your own site visitors in your website’s privacy policy where required by applicable law (including the GDPR, UK GDPR, and CCPA/CPRA). For full details on how Inletbase handles data, see the Inletbase Privacy Policy and Terms of Service.