Templates

A template is a pre-tuned bundle of fields, theme tokens, and settings that you can apply to a new form in one click. The point: get something publishable in five seconds instead of fifteen minutes.

You don't have to use a template — Empty form is always an option — but for the most common shapes, picking one saves you from rebuilding the same thing again.

Built-in templates

You'll see these on the New form screen:

Contact

The classic. Name, email, message. Honeypot on by default. Sensible theme. Works as either hosted or legacy.

Fields: name (text, required), email (email, required), subject (text), message (textarea, required).

Newsletter

Single-field email-capture. Designed to embed in a marketing page or use as the public hosted form on a "subscribe" landing page.

Fields: email (email, required), consent (consent checkbox for GDPR — required if your from_email lands in the EU).

Feedback

Quick rating + comment. Useful for in-app feedback widgets.

Fields: rating (radio, required, 1–5), comment (textarea), email (email, optional follow-up).

Support

A ticket-shaped form with category and priority. Pairs nicely with a webhook into your help-desk tool.

Fields: name, email (required), category (select: bug, feature, question, other), priority (radio: low, normal, high), subject, description (textarea, required), attachments (file, multiple, optional).

Demo request

For SaaS landing pages. Captures qualifying info upfront.

Fields: name, work_email (email, required), company, team_size (select: 1–10, 11–50, 51–200, 200+), use_case (textarea), consent (consent checkbox).

What hydrates

When you pick a template, the new form is created with:

• Fields — every field, in order, with validation, options, defaults pre-filled.
• Theme — the template's color, radius, font, spacing tokens. You can change these immediately.
• Settings — sensible defaults for the submit-button label, success message, multi-step layout (most templates are single-step).
• Honeypot — on, with the default _gotcha field name.
• Notifications — your own account email is added as the default recipient. Edit it after creation.
• Spam stack — defaults match the template's risk profile (Newsletter has tighter custom-rule defaults, for example).

What does not hydrate from a template:

• Captcha keys — you have to add your own hCaptcha or reCAPTCHA secret per form.
• Webhooks — every webhook is a deliberate choice.
• Custom rules beyond the defaults the template ships.
• Akismet keys — same logic as captcha.

Remixing a template

Pick the template, then change anything you want. Templates aren't locked. Once the form is created they're just normal forms. Add or remove fields, change the theme, swap settings.

There's no link back to the template — editing the template doesn't propagate. The template is a one-shot starter.

Saving your own templates

Not in the product yet. If you build the same custom form twice, two options today:

1. Duplicate — every form has a Duplicate action in the kebab menu. Copies fields, theme, settings, custom rules. New endpoint, new public_id.
2. Export schema, re-import — GET /forms/{form} returns the schema as JSON. POST /forms with that JSON creates a new form with the same shape.

Custom templates as a first-class feature is on the roadmap.

What's next

• Form builder → — modify the template
• Field types → — add fields the template doesn't ship
• Themes → — restyle the template's look