Getform Is Now Forminit: A More Complete Backend for Your Forms

A contact form looks like a small feature until you have to maintain it.

The first version sends an email. Then someone needs attachments. Sales and support need different notifications. A client asks where their enquiries came from. A webhook fails, and you need to find out which submissions reached the destination.

Multiply that across several websites, and forms become an ongoing infrastructure responsibility.

That is the problem we are building Forminit to solve.

Getform.io became Forminit on 14 January 2026. We are the same independent team behind the service that launched in October 2015. The new name came with a major product update, and we have continued expanding the platform throughout the year.

Here is what that means for developers, agencies, and teams shipping custom forms.

Already using Getform? Your endpoints still work

Your existing Getform endpoints continue accepting submissions. You do not need to replace live endpoint URLs or migrate your data because of the rebrand.

For new projects, use the Forminit dashboard and current documentation. To use the newer Forminit form architecture, create a new form and follow the setup guide for your stack.

You can read the original rebrand announcement for the details.

Your frontend, with a complete form backend behind it

Forminit is a headless form backend and API. You control the markup, styling, components, validation experience, and interaction design.

Send your submissions to Forminit, and it handles collection, server-side validation, spam protection, file storage, notifications, and integrations.

That separation matters when the form is part of your product experience. A quote request might need a custom budget selector. A feedback form might use emoji. An application might span several steps and include attachments.

You can build those experiences with the tools you already use, while keeping the submission infrastructure consistent across projects.

Form Blocks give submitted data a useful structure

An email address, a rating, and an uploaded document need different handling.

Form Blocks describe the data you send using field names such as:

Input name	What it represents
fi-sender-email	The submitter's email address
fi-text-projectBrief	A free-text project description
fi-number-budget	A numeric budget
fi-select-projectType	A selected project category
fi-rating-experience	A rating from 1 to 5
fi-file-attachment	An uploaded file

These names tell Forminit how to interpret and display each value. Supported typed fields receive server-side format validation, and the sender block groups contact information into a card in the inbox.

The structure also carries through to API responses, webhooks, and email variables. Your integration can work with a named budget field or sender email consistently.

You still define which fields your application requires and enforce your own business rules. Built-in type validation provides a foundation for that work.

Workflows route submissions and show what happened

A form often serves several purposes. A single enquiry form might receive new business requests, existing customer questions, and partnership proposals.

Workflows let you route those submissions using If / else conditions and connect several actions on a visual canvas.

For example, an agency could configure this flow:

1. Add each project enquiry to Google Sheets.
2. Check the submitted budget.
3. Notify a Slack channel when it exceeds a chosen threshold.
4. Send the submitter an acknowledgement.
5. Pass the enquiry to an internal system through a webhook.

Each submission shows the actions that ran and any reported errors. Once you resolve the cause of a failure, you can retry that action individually. Workflow edits remain in a draft until you publish them.

Email notifications, conditions, and status actions are available on Free. Integrations and autoresponders require Pro or higher.

The Google Sheets integration also lets you map form fields and metadata to spreadsheet columns and send a test row before going live. A team can keep its existing spreadsheet process while submissions arrive automatically.

Analytics connect enquiries to their source

Receiving an enquiry is useful. Understanding where it came from helps you decide what to do next.

Form Analytics brings together submission trends, UTM campaigns, ad click identifiers, locations, devices, and response breakdowns for choice fields.

The browser SDK can capture supported campaign parameters from the page URL and attach them to the submission.

For an agency managing landing pages, this can help answer practical questions:

• Which campaigns generated enquiries?
• Which services are people asking about?
• How does submission volume change over time?
• Which budget ranges appear most often?

That gives the team context alongside the actual responses, without manually adding up every dropdown answer in a spreadsheet.

Workspaces organise forms around clients and teams

Managing forms across client websites brings another challenge: access.

Developers need to configure integrations. The people handling enquiries need to update statuses and leave notes. Some stakeholders only need to view responses.

Workspaces support Owner, Admin, Editor, and Guest roles, with separate forms, API keys, and SMTP configuration for each workspace.

An agency can organise its work around a workspace per client and invite the appropriate people. Editors can handle submissions without changing form settings; Guests have read-only access.

Workspaces are available on the Business plan.

More control over spam, webhook verification, and retention

We have also added capabilities that matter once forms are running in production.

Cloudflare Turnstile. You can add Turnstile to your form and let Forminit verify submission tokens. Verification results are available in the logs, helping you investigate rejected or suspicious traffic. See the Turnstile update.

Signed webhooks. Your application can verify an HMAC-SHA256 signature before processing a webhook. Timestamps and event identifiers support checks against replayed requests and duplicate processing when implemented by your receiver. See the signed webhooks announcement.

Submission retention. Paid plans let you choose how long to retain submissions and their uploaded files. You can keep them until manually deleted, select 30, 90, or 365 days, or set a custom period. Expired submissions and their associated files are deleted automatically. See the retention update.

These features give teams more control over the data they accept, the systems they notify, and the information they keep.

Connecting a form is still straightforward

For a browser-based form, create a form in the dashboard, select Public mode, and replace YOUR_FORM_ID below.

Here is a plain HTML example with a file attachment:

<form
  action="https://forminit.com/f/YOUR_FORM_ID"
  method="POST"
  enctype="multipart/form-data"
>
  <label>
    Your name
    <input name="fi-sender-fullName" autocomplete="name" required>
  </label>

  <label>
    Email address
    <input type="email" name="fi-sender-email" autocomplete="email" required>
  </label>

  <label>
    Tell us about your project
    <textarea name="fi-text-projectBrief" required></textarea>
  </label>

  <label>
    Attach a brief
    <input type="file" name="fi-file-attachment">
  </label>

  <button type="submit">Send enquiry</button>
</form>

For asynchronous submission and an inline success state, use the JavaScript SDK.

If requests go through your own server or API route, Protected mode requires an API key. Keep that key on the server. Both approaches use the same submission API.

Building with an AI coding assistant?

We publish integration skills containing setup instructions, field conventions, and examples for supported stacks.

For an existing HTML form, you can give your assistant a prompt like this:

Connect my existing contact form to Forminit.
Keep its design, fields, and existing behaviour.

Form ID: YOUR_FORM_ID

Read and follow the HTML integration guide:
https://forminit.com/skills/forminit-html/SKILL.md

Add clear loading, success, and error states.

The assistant gets specific integration guidance, while you keep control of the interface it is connecting.

Try Forminit on your next form

Our goal is to make custom forms easier to ship and maintain, whether you are building one website or managing forms across a portfolio of client projects.

The Free plan includes one form, 100 submissions per month, file uploads, 100 MB of file storage, email notifications, and core workflow actions, with no credit card required.

Start for free at forminit.com →

You can also explore the documentation, current plans, and changelog.

If you have used Getform over the years, thank you for helping us get here.

What takes the most maintenance in your form setup today: spam, delivery failures, routing, or managing forms across projects?