Forms – YOWO7

What YOWO7 Forms can do

Four building blocks from the first field to the record — no copy-paste and no second form tool.

Visual editor

Fields, steps and design via drag-and-drop — from text to select to date, live in the preview.

A record, not copy-paste

The form is bound to a CRM object. The submission creates the record or updates it — via an identity property such as email.

Embed and share

Public link, readable slug URL, or embed.js on your site. Submit fires yowo7:form-submitted.

Views and conversion

You see views, conversion and submissions by day, week or month — plus source by surface and referrer.

The editor is the work surface

You drop fields onto the canvas, build steps and see the form live. The checklist shows what is still missing before you publish — design, captcha, target object.

Fields, steps and design in a full-screen editor
Text, email, number, date, select, multiselect and more
Headings and paragraphs between the fields
Live preview without publishing the form
Checklist before the first live run

Preview does not count

The editor preview is for checking. Views and conversion only count on the public page and in the embed.

Publish, embed, share

The form lives on forms.yowo7.com. You share the public link, use a readable slug URL or put the official snippet on your site.

Public page at /f/…
Readable slug URL /{workspace}/{form}
Embed with embed.js and data-yowo7-form
Submit fires yowo7:form-submitted
Unpublish and archive when the form should no longer be live

Official snippet only

Published embeds run through embed.js. A raw iframe on /f/… is blocked — so height and visitor ID stay correct.

The submission is the record

Each form is bound to a CRM object. Fields write into properties. Via the identity property — usually email — you update the same contact instead of creating duplicates.

Bind the form to contact, company, deal or a custom object
Upsert via an identity property, for example email
Submission in the table and on the record
Notify team members by email
No copy-paste from a second form tool

No ticket switch

The submission lands in CRM. A task or a ticket is created only if you set an automation afterwards — not as a switch on the form.

More about CRM

You see what comes in

Performance and submissions sit side by side on the detail. Views, conversion and a chart by day, week or month — plus source by surface and referrer.

Views and conversion rate on public, embed and slug
Chart by day, week or month
Sources: surface and optional referrer host
Submissions as a table with a submitter label
Preview views do not count

One look for every form

Style sets live in Admin. New forms inherit the primary set — including light and dark. You set colors, type and buttons once.

Colors, typography and buttons in one place
Light and dark tokens per set
New forms use the primary set
Live on forms.yowo7.com

Language and prefill

You store copy in several languages. The rendered locale is driven by ?lang= or — in the embed — data-lang. You prefill fields via query or data-yowo7-prefill-*.

Several locales on the form, with a default language
?lang= on the public link, data-lang on the embed
Prefill via query parameter = property slug
In the embed: data-yowo7-prefill-{propertySlug}
Allow prefill per field — sensitive fields stay empty

Automation · Submission

When

Submission received

Then

Note on the contact

Then

Project task

What should happen after submit

The submission sits in CRM. An automation can then write a note or create a task — triggered by forms.submission.received, not by a second switch on the form.

Trigger: submission received
Record ID sits on the submission
Note on the contact, project task, notify the team
No ticket and no task as a form switch

More about automations

Everything in detail

The feature set of YOWO7 Forms to scan — so you can see whether your flow fits.

Editor and fields

Full-screen editor with palette, canvas and inspector
Fields: text, email, number, date, date+time, long text
Yes/no, select, multiselect, language, hidden
Headings and paragraphs as layout blocks
Checklist before publishing

Steps and languages

Multiple steps with next and back
Several locales on the form
Default language plus translations
?lang= on the public link
data-lang on the embed

Surfaces

Public page /f/{publicId}
Slug URL /{workspace}/{form}
Embed via embed.js and data-yowo7-form
Draft preview from the editor
Event yowo7:form-submitted after submit

CRM and submissions

Form bound to a CRM object
Create or update the record (upsert)
Identity property, for example email
Submissions table with submitter label
Submission on the record and in the timeline

Performance

Views on public, embed and slug
Conversion rate
Chart by day, week or month
Source: surface plus optional referrer host
Preview does not count

Look and style sets

Workspace style sets under Admin → Workspace
Light and dark tokens per set
Colors, typography and buttons
New forms use the primary set
Overrides in the form editor

Protection and afterwards

Cloudflare Turnstile or reCAPTCHA v2
Thank-you content or redirect after submit
Prefill via query or embed attribute
Notify team members on a new submission
Publish, unpublish, archive

Automation, API and mobile

Trigger forms.submission.received
Read submissions on the record via Public API and MCP
Scope forms:read, no writes via the API
Forms editor is not in the mobile app
No Support ticket switch on the form

Missing something for your flow? Ask us — we will tell you openly whether and how it works.

And this is one module

Forms are part of YOWO7

The same workspace holds CRM, Inbox, Projects, Automations and more. One login, one data layer, no hand-off between tools.

Core apps

More apps

See what else belongs — or start with forms right away.

Forms FAQ

Yes. You add embed.js and data-yowo7-form, share the public link /f/… or use the readable slug URL. Submit fires yowo7:form-submitted. A raw iframe on /f/… is blocked — published embeds run through the snippet.

Text, email, number, date, date + time, long text, yes/no, select, multiselect, language and hidden fields — plus headings and paragraphs.

Yes. Forms support multiple steps with next and back. The checklist in the editor shows what is still missing before you publish.

Workspace themes for public forms: light and dark, colors, type and buttons. You manage them under Admin → Workspace → Style sets. New forms use the primary set.

With captcha: Cloudflare Turnstile or reCAPTCHA v2 (checkbox). After submitting you show thank-you content or redirect.

Into CRM. The form is bound to an object — contact, company, deal or a custom one. Via the identity property, usually email, the record is created or updated. The submission sits in the table and on the record.

Yes. On the public link via query parameter (property slug, so ?country=DE). In the embed via data-yowo7-prefill-{propertySlug}. You allow prefill per field — sensitive properties stay empty.

Yes. You store locales on the form. The rendered language is driven by ?lang= on the link or data-lang on the embed.

Not as a switch on the form. The submission lands in CRM. An automation with the trigger forms.submission.received can then write a note or create a task. There is no Support ticket switch in the Forms UI.

You use the editor in the browser. The mobile app covers Inbox, CRM, Files and Projects — the Forms editor stays on the desktop. Senders still fill the published form on any device.

Forms that arrive in CRM.

Build the first form, embed it on the site, see the submission on the record — with your real requests instead of sample data.

Get started

Forms belong to the workspace — core systems in the EU.

Forms that land in your CRM