IvyForms Review: The WordPress Form Builder Rewired for the AI Era

ByBNW TEAM

WordPress does not lack for form plugins. 

Search the plugin directory and you will drown in options — contact forms, survey builders, quiz makers, payment forms. What WordPress has lacked is a form builder that treats Just launched — Amelia’s AI Website Builder for WordPress Most tools are very good at collecting a name and an email and firing off a notification, and then they leave you to wrestle the data into a spreadsheet somewhere else. 

IvyForms was built to close that gap, and in 2026 it has done something few of its rivals have managed: it has made itself genuinely useful to AI agents.

This review looks at IvyForms end to end — the drag-and-drop builder, the plain-language AI form builder, the field types and templates, the integrations, and the headline addition that has people talking: a new MCP (Model Context Protocol) feature that lets AI assistants read and act on your forms, bookings and tables through a single WordPress connection. 

It is an in-depth look, so we also weigh the pricing against the competitors — WPForms, Gravity Forms and Formidable Forms — and we are honest about where a young plugin still has ground to cover.

A form builder from a data company

Alt: Perfect flow in WordPress ecosystem: IvyForms to collect data with forms, Amelia to book appointments and wpDataTables to analyze the data.

IvyForms comes from Melograno Venture Studios, the studio behind three of the most widely used tools in the WordPress professional stack: Amelia (appointment booking), Trafft (scheduling for service businesses) and wpDataTables (tables, charts and data reporting). 

Among them these products serve more than 170,000 WordPress professionals, and that lineage matters. IvyForms was not dreamed up in isolation — by the company’s own account it grew directly out of requests from wpDataTables users who wanted a native way to collect the data they were already visualizing.

“I see IvyForms as the final touch of data management in our data management ecosystem. So now we complete the cycle.”

— Sara Idvorac, Product Owner, IvyForms

That framing tells you everything about the plugin’s philosophy. Where a typical form builder thinks in terms of forms, IvyForms thinks in terms of data. 

A submission is not a notification to be read and forgotten; it is a structured record that can be filtered, exported, pushed into a table, linked to a booking, and increasingly, queried by an AI agent. 

The marketing line on the homepage — “More than a WordPress form builder” — is doing real work rather than posturing.

Building forms with AI in plain language

The first thing most people will notice in the current version is the AI form builder. Instead of dragging every field into place, you can describe the form you want in ordinary language — “a job application form with name, email, a CV upload and three screening questions” — and IvyForms assembles it for you. 

Crucially, the AI does not stop at laying out fields. It can add fields, help configure entry review, and set up notifications, all through the same conversational instructions. For anyone who has spent an afternoon fiddling with field settings, this is the sort of feature that quietly saves hours.

The classic drag-and-drop builder is still there, and it is fast. Reviewers repeatedly single out the one-screen editing experience and the live preview: you build on the left, you see the real form on the right, and you publish or unpublish directly from the forms table. 

One WordPress.org reviewer summed up the reaction that shows up again and again — 

“Really nice plugin, simple to use and the forms look great out of the box”

It is worth being precise about what “AI form builder” means here, because the phrase is used loosely across the industry. 

In many products it amounts to a template picker with a chat skin. In IvyForms the AI is wired into the builder’s own actions — the same operations you would perform by hand are the ones it performs on your behalf — which is why it can go beyond generating a layout to configuring how entries are reviewed and how notifications fire. 

It is the difference between a tool that suggests a form and one that builds it, and it is the natural on-ramp to the deeper MCP capabilities described below: the same plain-language habit you use to build a form is the one you will use to query its data later.

The headline: one MCP connection, a much bigger workflow

Alt: Diagram explaining how IvyForms, Amelia and wpDataTables MCPs work together.

The most forward-looking addition to IvyForms is its support for MCP — the Model Context Protocol — the emerging standard that lets AI assistants talk to applications in a structured, permissioned way. 

On WordPress this works through an MCP adapter that bridges the site’s Abilities API to external AI systems, so an assistant like Claude or ChatGPT can actually do things on your site rather than just describe them, always within the authentication rules and capabilities of the connected user.

What makes IvyForms’ implementation compelling is that it is not a single-plugin trick. Because IvyForms, Amelia and wpDataTables share the same MCP-based architecture, one connection opens a coordinated, three-part workflow that no standalone form plugin can match. Amelia no longer has to work alone:

  • Take action on bookings — Amelia MCP: create appointments, list services and employees, add customers, and assign them to recurring events.
  • Work with submitted information — IvyForms: give AI workflows access to form and entry data, including the information collected before or around a booking.
  • Work with structured data — wpDataTables: query table data and build AI-assisted reporting workflows from booking and form data.

Put those together and the pattern is elegant: collect with IvyForms, book with Amelia, work with the data in wpDataTables — all of it reachable by your AI workflow through the same MCP-based WordPress architecture. 

Examples in action

A concrete example makes it click. A clinic could have a patient fill an IvyForms intake form, book a slot in Amelia, and then ask an assistant, “How many new-patient consultations did we take last week, and which practitioner is busiest?” — with the answer assembled from IvyForms entries and wpDataTables reporting without a human exporting a single CSV. That is the difference between a form plugin that stores data and an ecosystem that lets you act on it.

A second scenario shows the collection side. Picture a marketing team running a lead-capture campaign across several landing pages. An assistant could be asked to “pull every demo request from the last fortnight, drop the obvious spam, and give me a table of company size versus budget.” IvyForms exposes the form and entry data; wpDataTables turns it into the structured table and the reporting; the human never touches the database. Because the whole exchange happens through MCP with the connected user’s WordPress permissions, an assistant can only see and do what that user is already allowed to — the AI inherits your access controls rather than bypassing them.

There is a quieter advantage worth naming, too. This is on-premise data: your submissions live in your own WordPress database, not in a third-party form-SaaS cloud. 

For teams handling personal or regulated information, an AI workflow that reaches your data where it already sits — under your GDPR posture and your permissions — is a materially different privacy story from piping everything out to an external service first. It is a point one Product Hunt reviewer singled out, and it is likely to matter more, not less, as AI agents become part of everyday operations.

IvyForms – the feature set, tier by tier

IvyForms has moved quickly. What began as a lean collector is now a full-featured builder, and the roadmap keeps adding to it. Here is what the plugin covers today.

Fields, logic and form structure

The builder ships with 20+ field types spanning standard inputs (text, email, phone with auto country detection, address fields that split cleanly), advanced fields, survey fields and a digital signature field. Structure is handled by multi-page forms that break long forms into steps to lift completion rates, and by conditional logic that shows or hides fields based on what the user has already answered. For a more human feel there are conversational forms, which present questions one at a time like a chat rather than a wall of inputs.

Templates and customization

A growing library of standard, advanced and survey templates — contact, order, waiver, registration and feedback among them — means most forms start from something rather than a blank canvas. The newer customization and form theme templates give control over layout, colors, labels, spacing and styles, and there is a dedicated Amelia theme that visually matches intake forms to the booking flow. Dark and light modes and fully responsive, mobile-friendly output round it out.

Entries, notifications and anti-spam

This is where IvyForms’ data-first stance pays off. Entry management is available from the start, with no entry-volume caps and no premium paywall on your own inbox — a pointed contrast with builders that meter submissions or lock the entries screen behind an upgrade. You can filter, search, sort visible columns, track unread submissions and inspect metadata such as IP address and browser. Multiple notifications, multiple confirmation messages and thank-you redirects handle post-submit behavior, and spam is covered by reCAPTCHA, hCaptcha and Turnstile. The plugin is GDPR compliant and includes role-based permissions.

Integrations and developer hooks

Beyond the ecosystem trio, IvyForms connects to Google Sheets (with multiple-sheet support), Mailchimp, and a growing set of automation options via webhooks and a REST API for connecting to virtually any external service. It slots into Gutenberg, Elementor and Divi, with AI assistance surfaced right inside the Elementor flow. The company has signalled that Zapier, Slack, advanced integrations, multiple payment methods and calculation fields are on the way — useful to know, and an honest reflection of where the roadmap still has gaps.

Intake forms before booking: the Amelia integration

One integration deserves a closer look because it shows the ecosystem thinking in miniature. The IvyForms + Amelia integration lets you put an intake form in front of the booking process. 

A customer fills the IvyForms form first, then moves to Amelia to choose a service and time; once the booking is confirmed, the submission is created and linked to the booking record. Administrators decide which fields are required before the customer can continue, and if someone abandons the booking, the temporary form data simply expires without cluttering your entries with dead records.

It is the kind of workflow that normally takes two plugins and a fragile bit of glue — meal preferences for an event, consultation goals before an appointment, preparation notes before a service. Here it is native, and notably, the integration is free even for users without a paid IvyForms plan. That generosity is a recurring theme.

What the reviews and ratings say about IvyForms

For a plugin this young, IvyForms has landed well. On Product Hunt it launched to a #2 Product of the Day finish with 298 upvotes and a 5.0 rating — a strong showing in a crowded category. On WordPress.org it holds a perfect 5.0 out of 5 across its early reviews, with 1,000+ active installations and a steady release cadence (version 1.4, updated within the last week at the time of writing).

The qualitative feedback is more telling than the star count. Independent write-ups keep returning to the same point — that IvyForms is solving a data problem, not just a forms problem. 

A HostingAdvice review framed it as the piece that “completes the cycle” between collection and analysis, while a SitePoint tutorial praised the guardrails — required-field validation, email confirmation, phone and address handling — and the fact that full entry access is there “from the get-go” without a paywall. One Product Hunt reviewer put the architectural case plainly:

“The architectural integration within the core WordPress ecosystem bridges the gap between raw data collection and operational data modeling — complete on-premise data security, native database connections to the Melograno ecosystem, and zero entry volume caps.”

— IvyForms reviewer, Product Hunt

Pricing — and why the lifetime deal changes the maths

IvyForms keeps its pricing refreshingly simple. There is a capable free plan, and the paid tiers are separated mainly by how many domains you can use them on rather than by locking core features away tier by tier — a structure that already sets it apart from the incumbents. Current pricing (with launch discounts) runs:

  • Free — €0: full entry management, drag-and-drop, templates, spam protection.
  • Essentials — €29/yr (was €48), one domain.
  • Growth — €59/yr (was €111), three domains.
  • Agency — €99/yr (was €229), unlimited domains — flagged as the best annual deal.

But the number that reframes everything is the Elite lifetime plan: €399 one-time, down from €997 — and it includes all future updates. Pay once, own it, and every feature the roadmap ships (Zapier, Slack, payments, calculations and whatever comes after) arrives at no extra cost. 

In a market that has quietly standardized on annual renewals forever, a lifetime license with guaranteed updates is a genuine outlier.

How it stacks up against WPForms, Gravity Forms and Formidable Forms

The three most-cited premium builders are all subscription-only, and none of them offers a lifetime option. Their unlimited-site tiers renew every year — in perpetuity.

Every feature, every tier — not a feature ladder

IvyForms’ pricing has a quirk that is easy to miss but genuinely matters: you are not climbing a feature ladder. The two models work very differently.

  • The incumbents gate features by tier. Conditional logic sits in one plan, surveys a plan up, payments higher still, white-labeling only at the top — so you often buy a whole plan just to unlock the one feature you actually need.
  • IvyForms scales on domains, not features. The toolset is broadly the same on a single site or unlimited ones. You pay for reach, not for permission to use a field type.

That flips the calculation for two kinds of buyer:

  • Freelancers get an affordable tier that is not a stripped-down tier.
  • Agencies get one predictable line item instead of a matrix of upgrades.

The gap widens when you stop comparing sticker prices and run the unlimited-site cost forward:

    • WPForms Elite — reverts to $599/year after the first-year discount.
    • Formidable Elite (unlimited) — $299.50/year.
    • Gravity Forms Elite (unlimited) — $259/year.
  • IvyForms — €399 once, with all future updates included.

Over three years, an unlimited license from any of the three costs several times IvyForms’ one-time €399 — and IvyForms is the only one of the four where feature access does not climb steeply with the tier. Even the annual plans undercut the field: €29 for a single site sits below Gravity’s $59 entry and roughly level with Formidable’s $39.50, while giving you the same features the top tiers get. For anyone tired of renewal treadmills — agencies especially — the lifetime deal is the headline.

Currencies differ (IvyForms lists in EUR, the others in USD); figures are 2026 list annual prices and renew yearly. IvyForms’ €399 is a one-time payment with all future updates included.

The honest cons of IvyForms

Enthusiasm should not paper over the trade-offs of adopting a plugin this new. Two are worth weighing:

  • Some table-stakes integrations aren’t shipping yet. IvyForms is at version 1.4, having launched in 2026, and a few things competitors treat as standard — Zapier, Slack, native payment gateways and calculation fields — are still on the “coming soon” list. If your workflow depends on collecting payments inside the form today, that gap matters.
  • The review base is small. A perfect 5.0 is easier to hold across a handful of reviews than across the thousands WPForms and Gravity Forms have banked over a decade. Those incumbents also bring vast add-on ecosystems, years of edge-case hardening and enormous communities.

IvyForms is betting on a different strength — tight integration with a proven data and booking stack, plus a forward position on AI — rather than breadth of third-party add-ons. For most users that is a sensible bet, but go in with clear eyes: you are backing a fast-moving newcomer, not a settled veteran.

Who IvyForms is for

It helps to be concrete about the fit. IvyForms is a strong match for:

  • Existing Amelia, Trafft or wpDataTables users. The integrations are native, the intake-before-booking flow is free, and the shared MCP layer turns three tools into one workflow.
  • Agencies and freelancers managing many sites. Unlimited domains for €99/year, or the €399 lifetime license, removes the per-client cost creep that annual per-site pricing inflicts.
  • Teams that care about owning their data. Anyone in health, education, finance or the public sector will value that submissions stay in their own database and that any AI access runs through WordPress permissions rather than an outside cloud.

It is a less obvious pick if you need a very specific third-party add-on today — a niche CRM connector, an established payment gateway, a mature Zapier recipe library — that the incumbents already ship and IvyForms has flagged as “coming soon.” Check the current roadmap against your must-haves before committing. But given the release cadence so far, that gap is closing quickly rather than a permanent ceiling.

IvyForms Form Builder: Is it worth the hype?

IvyForms is one of the more interesting things to happen to WordPress forms in years, precisely because it refuses to think of itself as “just” a form builder. What stands out:

  • A fast, modern builder. The drag-and-drop experience is quick, and the AI form builder is a real time-saver.
  • Generous entry management. Full access to your submissions from day one — no volume caps, no paywalled inbox — where rivals are stingy.
  • The MCP feature and the ecosystem behind it. One connection lets AI agents collect with IvyForms, book with Amelia and report with wpDataTables — a workflow no standalone competitor can offer today, and one that positions the plugin for where the web is clearly heading.
  • A €399 lifetime license with all future updates. Against a field of rivals that will bill you every year forever, the value proposition is hard to argue with.

The bottom line: if you want the biggest, most battle-tested add-on library on the market, the incumbents still have the edge. But if you want a modern, data-first form builder that is already AI-ready and won’t nickel-and-dime you as it grows, IvyForms has earned its place on the shortlist — and its Product Hunt runner-up finish and spotless early ratings suggest plenty of people already agree