powermail for TYPO3

powermail is the production-ready form system for TYPO3

Between the TYPO3 core form framework and full marketing automation tools there is a practical gap: editorial teams want to build forms without code, with conditional logic, file upload, GDPR (UK: UK GDPR) consent, CRM forwarding and clean PDF export. That is exactly what powermail is built for. The extension from in2code is the most widely installed form plug-in in the TYPO3 ecosystem and runs on the majority of all mid-sized and large TYPO3 projects Gosign maintains. Since its first version more than a decade ago, powermail has become the Swiss army knife of TYPO3 form development and remains a valid choice even when the TYPO3 core form framework would theoretically suffice.

Typical use cases range from contact forms to application portals

The most common scenario is trivial but unavoidable: contact forms on corporate websites that send emails to different departments. powermail handles this through conditional recipient routes without any developer intervention. Editors maintain the fields in the backend like a page content element, including order, required fields and validation. A typical corporate installation has three to five form variants: general contact enquiry, press contact, careers, support and product advice. Each variant lands in the right department inbox through its own recipient filter.

Considerably more demanding are multi-step application forms as they are common at public institutions and universities. An application portal asks for master data in step 1, the desired course in step 2, certificates via upload in step 3 and a GDPR consent with link to the privacy policy in step 4. powermail renders all four steps from a single form record and stores the progress between steps in a session, so that applicants can jump back if needed. Conditions show or hide fields depending on previous answers, which keeps complex forms such as scholarship applications or habilitation registrations manageable even with three-digit numbers of field combinations.

A third scenario that sets powermail apart from simpler extensions is integration with CRM and marketing tools. The finisher architecture allows data to be sent in parallel to HubSpot, Salesforce, Brevo or a custom webhook, before the confirmation email goes out. At Gosign, powermail is therefore also the standard tool for lead forms that feed directly into the sales process. On an enterprise project, we connected powermail to Salesforce Marketing Cloud and simultaneously forwarded through a webhook to the internal ticket system, so that sales and support teams could work on the enquiry in parallel.

Technical architecture separates form definition, finisher and template

powermail consists of three conceptual layers: the form definition in the backend, the finishers that run after submission and the Fluid templates that handle rendering. Every layer is extensible without forking the extension. This clean separation makes powermail a robust tool for long-lived TYPO3 projects in which forms are maintained and extended over years.

Forms are stored as records in tx_powermail_domain_model_form. Every form contains pages (steps), every page contains fields. Field types range from text, email, select, radio and file upload through to HTML content and consent checkboxes. Conditional logic is maintained through the conditions module: “Show field B only when field A has the value X”.

Finishers are the actual strength of the extension. The standard finisher sends emails, stores entries in the database and creates PDF exports. Additional finishers can be implemented via FinisherInterface: webhook delivery, CRM sync, Salesforce, SAP handoff. The order of the finishers is configurable, and each finisher can abort the process on error.

Templates live as Fluid files in the extension path and are typically overridden via SiteSet or a custom package. That means: a single global template overlay is enough to give all forms on a website a consistent appearance. Anyone who needs custom templates per form can reconfigure the template paths via TypoScript and maintain a template set per form type.

Common problems involve spam, GDPR and email deliverability

The dominant support topic on public powermail forms is spam. Out of the box, the extension ships honeypot fields, timestamp checks and an optional reCAPTCHA v3 through ext:powermailrecaptcha. Still, spam ends up in the backend if the administration has not enabled the checks. We recommend combining honeypot and reCAPTCHA on every form and additionally using an IP-based rate limit finisher.

The second problem is GDPR compliance. Form consent has to be documented in an audit-proof way: date, version of the privacy policy, IP and user agent. The extension offers the consent storage, which logs consent decisions separately and makes them exportable for audits.

Thirdly, email deliverability is a constant topic. Confirmation emails end up in spam because the sender is not authenticated. SPF, DKIM and DMARC have to be configured correctly at the mail server level, and the powermail configuration should set a Return-Path and a valid Reply-To. For larger installations we additionally recommend a dedicated transactional mail service such as Brevo, Mailgun or Amazon SES, so that the delivery rate does not suffer under the general server reputation.

TYPO3 v12 and v13 are fully supported

powermail is available shortly after every TYPO3 LTS release because in2code actively maintains the extension. The current series supports TYPO3 v11, v12 and v13 in parallel. When upgrading older installations, breaking changes mainly affect custom finisher classes, which have to be moved to the current interface signature, as well as Fluid templates that respond to ViewHelper changes.

Gosign typically migrates powermail installations together with the TYPO3 core upgrade. Before the jump, we check which custom finishers and templates exist, which third-party integrations are wired in and whether outdated plug-in variants are still in use. The migration usually runs without data migration, because the record structure of the form definition remains stable.