Formerize docs

Build, test, and publish a form.

Design your form, publish it, and receive responses without building a backend.

Quickstart

  1. Sign in and create a form with a Contact, Sales inquiry, or Waitlist template.
  2. Change the fields, styling, and confirmation message in the builder.
  3. Preview the form as a visitor. Preview responses are not saved or emailed.
  4. Check the owner email, then use the explicit publish action. A published form sends live entries to that verified owner email.
  5. Use the Dashboard to copy the generated HTML for your site or share the hosted form link.

Expected result: keep a draft while you are testing. Publish only when the owner email and live destination are correct.

Drafts, previews, and live forms

StateWhat it meansNext step
DraftThe form is editable and not live.Test it or continue editing.
PreviewA local preview of your draft. It does not save responses or send email.Check the fields and completion message.
PublishedEntries from the hosted link or installed HTML are live.Check entries and delivery history in the Dashboard.

Publishing can be unavailable when live delivery is not configured for the workspace. Keep the form as a draft and contact the form owner.

Install a published form

Open the form in the Dashboard after it is published. Copy the dashboard-generated HTML into your site, or use the hosted link as the destination you share. Do not hand-write a different set of input names: the installed fields must match the published form.

Expected result: a live submission gets an acceptance response from Formerize. Acceptance does not mean that an email has been delivered.

Check delivery

Open the form’s entries and delivery history in the Dashboard. These are separate steps in the path from a visitor to an inbox.

EvidenceWhat it proves
Accepted entryFormerize accepted the visitor’s entry. It is not proof of email delivery.
Provider resultThe email provider accepted the delivery request or reported a failure.
Mail-server eventA delivered, bounced, or complained event is evidence reported after the provider sends the message.

Fix common problems

ProblemWhat to do
Missing or invalid fieldComplete the required field named by the form, then submit again.
Temporarily rate limitedWait a moment, then retry the same form.
Form quota reachedThe form is not accepting entries. Contact the form owner.
Delivery failed, bounced, or complainedThe owner should open delivery history and use the reported state to check the destination mailbox.
Hosted form is unavailableAsk the owner to check that the form is still published and that the link is correct.

For agents and developers

Use the canonical Agent Skill for the supported workflow and safety rules. The agent start guide is a shorter setup path. The machine-readable API contract is OpenAPI.

Human templates are also available at Contact forms, Lead forms, and Waitlists.