Website forms that bring visitor messages to your inbox
Describe the fields, turn on a captcha, and pick what happens on submit: an email to your inbox or a thank-you page. No server code required.
What website forms people build
They all share one build: form fields plus actions on submit. Only the set differs.
Contact form. Name, email, and message fields plus an email to your inbox: everything the visitor typed arrives with the message.
Feedback form. The same fields, plus an autoresponse to the visitor or a thank-you page.
Newsletter signup. One email field and an action that passes the subscriber to your mailing service.
Survey. Fields for your questions; you pick which are required.
Password-protected page. Also a form: visitors log in with a password, and the page opens only for them.
How it works: three steps
1. Create the scenario. A form in DynapiCMS is a scenario: it has an address on your site, fields, and actions on submit.
2. Set the actions. An email to your inbox, a thank-you page, an autoresponse to the visitor, a request to an external service. Captcha and field checks are enabled in the form properties.
3. Publish and receive submissions. The form opens on your site, and every submission lands in the journal: you see whether the email went out or which step failed.
What happens after submission
The email arrives from your domain: the send node carries the settings of your SMTP service. The visitor lands on a thank-you page or gets an autoresponse.
To hand data to an external service, add an HTTP request or a webhook. Telegram chats and CRMs are reached the same way: they expose a webhook endpoint. There are service actions too: reading project content through GraphQL, setting cookies. The full list is in the action reference.
A captcha of your choice keeps bots out: Cloudflare Turnstile, Yandex SmartCaptcha, or Google reCAPTCHA. You enable it in the form settings.
Every submission stays in the journal, broken down by action. Messages and answers live in your project's database; no third-party form service sits in the chain.
A form on an existing website
If your site already runs on WordPress or another platform, there are two ways to add a form.
1. Iframe. Embed the form page into your site: no blocking headers, it opens right inside.
2. Your own HTML form. Markup on your site posts data straight to the project: list the allowed site addresses in the form settings.
What's inside the form on this page
A form that sends email consists of fields and a handler. An HTML template from the internet is fields only — no email ever leaves it. The form on this page is live: it has a handler scenario and a submission journal.
The mechanism — scenarios, submit actions, checks, and publishing — is covered in the documentation.
What's here that other builders don't have
Four concrete differences — measured against the things that most often get in the way when a form lives somewhere else.
| Feature | DynapiCMS | Jotform | Typeform | Tilda | Google Forms |
|---|---|---|---|---|---|
| Data stored in Russia | yes | no | no | no | no |
| Webhook to a custom URL | yes | yes | yes | yes | no native |
| Custom SMTP in the email node | yes | Enterprise only | no | no | no |
| CAPTCHA out of the box | Turnstile | reCAPTCHA | reCAPTCHA | built-in | partial |
SMTP and webhooks are covered in the action reference; CAPTCHA — in the captcha form preset.