Website forms that deliver messages to your inbox

Describe the fields, pick a captcha, and choose what happens on submit: an email to your inbox, a thank-you page. No server code required.

map[en:This form is live — it is built with DynapiCMS. ru:Форма на этой странице — рабочая, она собрана на DynapiCMS.]

Kinds of website forms

Contact section

Name, email, and message fields. A visitor submits the form and the message lands in your inbox.

Feedback form

Visitors write to you; the form replies with a text auto-response or greets them with a thank-you page. Actions are configured in the same form.

Newsletter signup

A single email field; your newsletter service receives the subscriber via webhook, if you use one.

Surveys and polls

Fields for any questions; you mark which ones are required.

Password-protected page

Password-gated access, built with the same mechanism as forms.

How it works: three steps

Describe the fields

A form in DynapiCMS is a scenario: list the fields and mark the required ones.

Configure submit actions

Email to your inbox, a redirect to a thank-you page, an auto-reply to the visitor, a request to an external service. Captcha and field checks are form settings.

Test and publish

The form runs a dry-run before publishing. After launch, the journal shows every step — where it succeeded and where it failed.

What happens after submit

The email goes to your inbox: the send-email node carries your mail service settings (SMTP), so the message arrives from your own domain. The visitor lands on a thank-you page or gets a text auto-reply. To pass data to an external service, add an HTTP request or a webhook. If messages should reach a Telegram chat or a CRM, the same HTTP action delivers them — these services expose a webhook endpoint. There are utility actions too: reading project content over GraphQL, setting cookies. The full list is in the actions reference.

Bots are stopped by a captcha of your choice: Cloudflare Turnstile, Yandex SmartCaptcha, or Google reCAPTCHA. It is a form setting.

Every submission stays in the journal, broken down by action. Messages and replies live in your project's database — no third-party form service in the chain.

A form on your existing site

If your site already runs on WordPress or another platform, there are two ways to add a form.

The first is to embed the form page in an iframe: no blocking headers, the page opens inside your site.

The second is your own HTML form on the site that posts straight into the project: list the allowed site addresses in the form settings.

A ready form: build it with the 10-minute guide

A form that sends email is fields plus a handler. An HTML template from the internet is fields only — no mail leaves it.

The form on this page is the whole mechanism. The guide "Your first scenario in 10 minutes" takes you from fields to publication. One subscription form becomes a template for the next ones.

Гайд «Первый сценарий за 10 минут»

Поля, капча, письмо на почту и публикация — весь путь формы по шагам.

Открыть гайд

Справочник действий

Письмо, HTTP-запрос, вебхук, страница ответа — все действия формы и их параметры.

Открыть справочник

FAQ

Any of the ones listed above. Email arrives from your own domain — your mail service's SMTP is set in the send-email node.
Yes. Fields, captcha, and actions are configured in the admin panel, and a dry-run before publishing surfaces errors before launch.
A widget lives on a third-party service: email goes through its server and submissions are stored there. Here there is no middleman.
Enable one of the captchas — Turnstile, SmartCaptcha, or reCAPTCHA. Plus submit-time condition checks: required fields and any rules of your own.
Submissions are stored in your project's database. A configured form can be exported as a .dynflow.json file.

Start free

Sign up and your first form will start taking messages. Build it with the 10-minute guide; pick a plan when you need one.

Start free