Introducing Vibe Coding for Forms and the New MakeForms AI Co-Pilot

Most form builders still begin with an empty canvas.

You add a field, configure it, add another field, create a rule, preview the form, and return to the editor when something does not work as expected.

The tools may have improved, but the process has remained largely the same.

With Vibe Coding for Forms, the starting point is no longer an empty canvas. It is a conversation.

You can describe the outcome you need in plain English:

• Create a patient intake form for a dental clinic. Collect contact details, medical history, insurance information, current medications, and consent.

MakeForms uses that description to create the form directly inside the builder.

It selects suitable fields, organises them into sections, adds validation, and builds the structure needed for the form to work.

The result is not a static template or a loose collection of suggested questions. It is an editable MakeForms form that can be reviewed, published, connected to integrations, and managed like any other form in your workspace.

A good form depends on context.

Consider a simple request such as:

• Create an employee onboarding form.

That form could be for full-time employees, contractors, interns, or international hires. It might need banking details, tax information, identity documents, equipment requests, or none of these.

Instead of filling those gaps with arbitrary assumptions, MakeForms can ask follow-up questions before it builds.

It may ask who will complete the form, which documents need to be collected, whether different employee types require different questions, or what should happen after submission.

Each answer affects the form that is created.

A form for a contractor may request a contract end date. A form for a new employee may collect payroll details. A form for an international hire may include visa and work authorisation questions.

The conversation gives MakeForms the context it needs to build the right workflow, not simply a plausible-looking set of fields.

Real-world forms rarely show every question to every person.

A patient may need to provide more information after selecting a medical condition. A business customer may need to enter a company registration number. A job applicant may see different questions depending on the role they choose.

Conditional logic makes these experiences possible, but configuring it manually can quickly become time-consuming.

MakeForms can now create that logic as part of the form-building process.

You can describe the behaviour you want:

• If the respondent is applying as a company, ask for the registered business name, tax number, and proof of registration. Individual applicants should not see those questions.

MakeForms creates the relevant fields and connects the rules between them.

The AI considers how the form should behave as a whole. It can create separate paths, reveal follow-up questions, divide long forms into steps, and apply validation based on earlier answers.

The logic is not added after the form is built. It becomes part of the form from the beginning.

The AI Form Builder creates the form in a separate AI-powered experience.

As it works, you can see the structure being generated based on your prompt and the answers you provide. Fields, sections, steps, validations, and conditional logic are assembled into a complete first version of the form.

Once the form is ready, you can open it in the main MakeForms editor.

From there, you have two ways to continue.

You can use the regular editor to make changes manually, or use the MakeForms AI Co-Pilot to update the form through conversation.

You might ask the Co-Pilot to:

• Split this into four shorter steps.
• Move insurance information after medical history.
• Add an emergency contact section.
• Ask for supporting documents only when the insurance provider is not listed.
• Make the phone number optional but verify the email address.
   

The AI Form Builder helps you create the first version. The Co-Pilot takes over once the form is inside the editor, helping you refine, restructure, and maintain it without manually changing every setting.

The AI Form Builder creates the first version of your form in a separate AI-powered experience.

As it works, you can see the structure taking shape based on your prompt and the answers you provide. Fields, sections, steps, validations, and conditional logic are assembled into a complete form.

Once it is ready, you can open the form in the main MakeForms editor.

That is where the MakeForms AI Co-Pilot takes over.

The Co-Pilot works inside the editor and understands the form that is already there, including its fields, sections, steps, validation rules, and conditional logic.

You can ask it to:

• Split this into four shorter steps.
• Move insurance information after medical history.
• Add an emergency contact section.
• Ask for supporting documents only when the insurance provider is not listed.
• Make the phone number optional but verify the email address.

The Co-Pilot applies these changes directly to the existing form.

This becomes especially useful when a change affects more than one part of the form.

A field may control another section, appear in conditional logic, affect a calculation, or send data to an integration. What sounds like a simple edit can require several connected changes behind the scenes.

The Co-Pilot considers the existing structure before making an update.

A marketing team can shorten a lead form without rebuilding its qualification flow. An operations team can update an onboarding process while keeping its existing logic intact. A healthcare organisation can add new intake questions without disrupting the paths already used by different patients.

The AI Form Builder helps you create the first version. The AI Co-Pilot helps you continue improving it once it reaches the editor.

Vibe Coding for Forms and the AI Co-Pilot solve two different parts of the same problem.

Vibe Coding helps you move from an idea to a working form.

The AI Co-Pilot helps you continue improving that form after it exists.

A team can begin with a short description, answer a few questions, and generate the first version. They can then review it, make manual edits, or continue refining it through conversation.

Months later, when the workflow changes, the same team can return to the form and ask the Co-Pilot to update it.

There is no separate AI builder, export process, or generated copy to manage.

Everything happens inside MakeForms.

Forms do more than collect information.

They send confirmations, notify teams, deliver receipts, share documents, and keep customers informed about what happens next.

These messages often carry important information, and the sender matters.

An email from your own domain is easier to recognise and more consistent with the rest of your customer experience.

MakeForms has supported custom SMTP connections for businesses that want to send email through their own infrastructure. But traditional SMTP setup can require server addresses, ports, usernames, passwords, and encryption settings.

For many teams, configuring the connection takes longer than it should.

We are introducing a simpler way to connect the services businesses already use.

Mailgun users can now connect their account using an API key.

MakeForms retrieves the sending domains available in the account and lets the user select the domain they want to use.

There is no need to manually enter the SMTP host, port, username, password, or security configuration.

Add the key, choose the domain, and begin sending.

SendGrid can also be connected using an API key.

Once the account is connected, MakeForms displays the verified sending domains available through SendGrid. Select the appropriate domain and use it for form notifications.

This makes it easier for teams to use their existing email infrastructure without repeating a technical setup they have already completed elsewhere.

Teams that use Microsoft Outlook can connect their account directly to MakeForms.

Notifications are then sent through the connected Outlook account using the organisation’s email address, sender identity, and domain.

There are no SMTP credentials to copy and no mail server settings to configure.

Connect the account and select it as the sender.

Businesses with their own email servers or specialised requirements can continue using Custom SMTP.

The direct integrations do not replace the existing setup. They add faster options for teams that use supported providers.

Direct connections for Gmail, Zoho, and Yahoo are also planned.

The aim is to provide one place where teams can choose how every MakeForms email is sent, whether through a direct account connection, an email delivery provider, or their own SMTP server.

When we introduced our first AI form-building experience in 2022, AI could help turn a description into a starting point.

The technology can now do much more.

It can ask for missing context. It can reason about structure. It can build logic, understand an existing form, and apply changes through conversation.

That changes the role of a form builder.

Instead of beginning with individual fields and settings, teams can begin with the outcome they are trying to achieve.

Describe the patient intake process.

Explain how a vendor should be approved.

Outline the information needed from a new employee.

Tell MakeForms how different customers should move through an application.

The product handles more of the construction, while the user remains in control of the result.

That is Vibe Coding for Forms.

And it is now part of MakeForms.

Vibe Coding for Forms, the MakeForms AI Co-Pilot, and the new email connections are now available in MakeForms.

Users can create a new form through the AI Form Builder, open an existing form to work with the Co-Pilot, and configure supported email providers from the email connection settings.

Mailgun, SendGrid, Outlook, and Custom SMTP are supported, with more direct email connections planned.