

Drag-and-drop form builder with live preview
Formatrica is a WordPress form builder with built-in email delivery. Create forms visually, store submissions in WordPress, protect them from spam, and send notifications through WordPress mail, custom SMTP, or supported email provider APIs without installing a separate mail plugin.
Formatrica can handle both the form and its notification delivery. You can use the standard WordPress mail system, connect to your own SMTP server, or send directly through supported email provider APIs.
That means you do not need to install a separate SMTP or email-delivery plugin just to reliably send Formatrica notifications.
Supported delivery methods include WordPress wp_mail(), custom SMTP, Postmark, Amazon SES, Mailgun, SendGrid, Brevo, SMTP2GO, and Mailpit for local development.
Formatrica does not phone home. External services are contacted only when you explicitly enable and configure them for a form — see the External services section below.
Full guides, hook/filter reference, and REST API docs live at docs.nexusplugins.com.
Formatrica does not contact any external service by default. Each service below is used only when a site administrator explicitly enables and configures it for a form.
When a CAPTCHA provider is enabled, the visitor’s browser loads the provider’s widget and, on submission, the visitor’s IP address and a verification token are sent to the provider for scoring. Providers: Google reCAPTCHA v3 (Terms | Privacy), Cloudflare Turnstile (Terms | Privacy), and FriendlyCaptcha (Terms | Privacy).
When a third-party email provider is configured, each notification email (recipient, sender, subject, and the submitted form data) is sent to that provider’s API. Providers: SendGrid (Terms | Privacy), SMTP2GO (Terms | Privacy), Mailgun (Terms | Privacy), Postmark (Terms | Privacy), Brevo (Terms | Privacy), and Amazon SES (Terms | Privacy). Custom SMTP and Mailpit send to your own mail server; the default WordPress provider uses wp_mail() with no external API call.
When an integration is enabled, form submission data (form title, submitted field values, and field metadata) is sent to the configured endpoint on each submission. Zapier, Make.com, and custom webhooks also include the submitter’s IP address and user agent.
Local data: submissions are stored in a custom table on your site; IP storage can be full, anonymised, or off; automatic deletion can be enabled per your retention setting; API keys and secrets are encrypted at rest and never exposed in the admin UI or REST responses.