Bina – AI Form Builder for Contact Form 7 with Drag & Drop, Entries & Styling

Install Bina alongside Contact Form 7, open the Bina menu, and import any form you already have with one click. From there you drag fields into place instead of typing tags like [text* your-name]. The shortcode is still written, correctly, every time you push the form live. You just never have to write it yourself.

Contact Form 7 emails a submission and then forgets it. Bina writes every submission to a table in your own WordPress database as well, so an enquiry that never arrives by email is still there. Entries have read and unread states, search across everything a visitor typed, and one-click CSV export. Nothing is sent to Bina's developers or to anyone else.

Open a form in Bina and use the Appearance panel. Colors, spacing, fonts, borders, corner radius and field height are all controls, with Normal, Hover and Focus states for fields, Normal and Hover for the submit button, and a live preview beside them. The styling is scoped to that one form, so your other forms are untouched, and the markup stays standard Contact Form 7.

Drag a row onto the canvas, drop fields into it, and pull the divider to set the widths. Contact Form 7 has no layout syntax of its own, so this is normally hand-written CSS. Bina writes the markup and the styles for you, and the form is still a plain Contact Form 7 form.

Importing does not touch your live form. It creates a draft. The live form changes when you press Push to Live, and that is when Bina regenerates the markup: fields and options are kept, custom HTML wrappers are rebuilt into Bina's layout. Preview first, and use the 24-hour rollback if anything looks wrong.

No. Bina is a builder that sits on top of it. CF7 keeps handling submission, validation and mail. Deactivate Bina and your forms carry on as normal CF7 forms.

Yes. The version on WordPress.org is completely free and includes the whole visual builder, one-click Contact Form 7 import, entry storage with CSV export, the front-end preview and the styling.

Yes, if you bring your own API key. Describe the form in plain English and Bina asks your provider to draft it. It asks a question or two when the request is genuinely ambiguous, shows you the fields it proposes before anything is created, and lets you ask for changes. Every generation reports what it cost in tokens. OpenAI, Anthropic and Google Gemini all work, and the feature does nothing at all until an administrator saves a key.

Yes. Bina forms stay ordinary Contact Form 7 forms, so you place them on a page exactly as you always have: the shortcode, the Contact Form 7 block, or a form widget in a builder like Elementor or Divi. To be clear about which tool does what, you build and edit the form in Bina, and the page builder only places it on the page. Bina's optional styling is light and only touches the forms it manages.

Yes. Tags from CF7 add-ons are imported, kept intact, and written back exactly as they were on push. You can still edit their name, label, required flag and raw options in the builder.

No. Bina's front-end styling only applies to forms Bina manages. Your other CF7 forms keep the look they have. You can also switch the styles off completely with the bina_load_form_styles filter.

They are kept. Bina round-trips CF7's mail, mail (2) and messages settings on import and on push. You still edit them in the CF7 admin tabs you already know.

By default, nothing. Two optional features can send something, and only once you have switched them on:

1. Anonymous, non-personal usage data (WordPress, PHP and Contact Form 7 versions, the plugin version, and which features get used), if you opt in. You can opt out again at any time.
2. The AI form generator, if an administrator saves an API key for an AI provider. Only the description you type is sent, from your own server to that provider.

It does nothing until an administrator opens Bina, picks a provider (OpenAI, Anthropic or Google Gemini), and saves an API key from their own account. Nothing is sent before that, and deleting the key switches the feature off again. When you generate a form, your server sends the description you typed straight to the provider you chose, using your key. If you ask for changes, the working form structure goes along so the model can edit it. That is the whole of what is sent: no entries, no visitor data, no site content, and nothing passing through Bina's developers. Your usage is billed by the provider you picked and governed by their terms. See the terms and privacy policies for OpenAI (https://openai.com/policies/terms-of-use/ and https://openai.com/policies/privacy-policy/), Anthropic (https://www.anthropic.com/legal/commercial-terms and https://www.anthropic.com/legal/privacy) and Google (https://ai.google.dev/gemini-api/terms and https://policies.google.com/privacy). Your API key is stored encrypted in your own database and is never shown again once saved, beyond the last four characters so you can tell which key it is. If you would rather the feature did not exist at all, define BINA_DISABLE_AI in wp-config.php and it is gone.

Freemius, Inc. The opt-in usage analytics and the deactivation feedback form both go through them. Data is sent only if you opt in, and only the anonymous, non-personal information described above. It never includes your form entries or your visitors' data, and nothing is sent if you skip the opt-in or opt out later. See the Freemius Terms of Service (https://freemius.com/terms/) and Privacy Policy (https://freemius.com/privacy/).

In your own WordPress database, nowhere else. Bina hooks into WordPress's privacy tools, so personal data in entries is included in the Export Personal Data and Erase Personal Data requests under Tools. You can also switch off entry storage for any form with the bina_store_entry filter.

Deactivating changes nothing: your entries stay in the database and your forms keep working as normal Contact Form 7 forms. Deleting the plugin is different. WordPress runs Bina's cleanup, which drops the entries table along with Bina's own settings and drafts. Export your entries to CSV first if you want to keep them.