mailingwork for TYPO3

mailingwork is the GDPR-native newsletter alternative to Mailchimp for TYPO3 projects

Companies that send a professional newsletter but do not want to transfer data to the US almost inevitably end up with a European provider. mailingwork is one of the established German email marketing platforms, with servers in Germany, a German legal entity and a support team that answers GDPR questions in German. The TYPO3 extension mailingwork is registered as a key in the TER, but there is no public version there, and it is not on Packagist either, so what it can do cannot be verified. An integration via the mailingwork API transfers signups and segmentation data between CMS and newsletter system. For TYPO3 projects that need a newsletter solution without legal complications, the combination of mailingwork and TYPO3 is one of the lowest-maintenance options in the German-speaking market.

The comparison with Mailchimp shows the difference: no data processing agreement with a US company, no transfer mechanism to document, no exposure when transatlantic data protection agreements change. The flip side: mailingwork has a smaller feature set than Mailchimp and no comparable ecosystem of third-party integrations. Anyone who needs advanced marketing automation (behavioral triggers, lead scoring, customer journey mapping) is more likely to hit limits with mailingwork than with Mailchimp or HubSpot.

Typical use cases are corporate newsletters, member communication and lead nurturing

The standard scenario is the monthly corporate newsletter for 5,000 to 50,000 recipients. The editorial team maintains content in TYPO3, builds the newsletter in mailingwork and sends it to segmented lists. The integration makes sure that new website signups land in mailingwork automatically and that unsubscribes reach both systems.

The second scenario is member communication for associations and clubs. A professional association with 10,000 members sends circulars, invitations and annual reports. The member data lives in TYPO3 (in fe_users or a custom table), and mailingwork handles delivery. Segmentation by membership type, region or special interest group is controlled via tags that can be generated from TYPO3 categories.

The third scenario is lead nurturing for B2B companies. A machinery manufacturer collects leads through white paper downloads and contact forms on its TYPO3 website. The integration hands the leads to mailingwork together with their source (which form, which page), and mailingwork starts an automated email sequence: welcome email after 1 day, case study after 7 days, invitation to request a quote after 14 days.

The technical architecture connects TYPO3 forms through the mailingwork API

An integration uses the mailingwork API for data exchange. The configuration covers the API endpoint, the access credentials and the mapping of TYPO3 fields to mailingwork contact fields; regular syncs run through scheduler tasks.

Subscriber import follows a clear sequence. A visitor fills in a signup form on the website. TYPO3 stores the data locally and transfers it to mailingwork via API call. mailingwork sends the double opt-in email, and only after confirmation is the subscriber listed as active. It makes sense to log every step in a log table, which matters for GDPR audits: the GDPR requires you to be able to demonstrate each subscriber’s consent, and under the EU ePrivacy rules, marketing emails to individuals need that consent in advance. (US: CAN-SPAM only requires a working opt-out, not prior consent.)

Segmentation works through tags and custom fields. TYPO3 system categories (sys_category) can be passed to mailingwork as tags. That way, website-specific segments such as “Interested in product X” can be used directly for newsletter sends.

Templates in mailingwork are maintained independently of TYPO3. Anyone who wants to pull TYPO3 content into newsletter templates automatically has to build that with the mailingwork API and custom code.

Common problems involve field mapping, double opt-in timing and error handling

Problem one: faulty field mapping. The fields in TYPO3 forms rarely match the contact fields in mailingwork one to one. A form asks for “Organization”, mailingwork expects “company”. Without correct mapping, data lands in the wrong fields or gets lost. The fix: before the integration, create a field mapping document that assigns every TYPO3 field to a mailingwork field, and store that mapping in the configuration of the integration.

Problem two: double opt-in timing. Hours or days often pass between the signup on the website and the click on the confirmation link. If the sync job runs in the meantime and reports the unconfirmed subscriber back to TYPO3 as “active”, the two systems drift apart. The fix: set the subscriber status in TYPO3 to “active” only once mailingwork returns the status “confirmed”.

Problem three: error handling during API outages. If the mailingwork API cannot be reached, the integration has to buffer the signup and retry on the next sync run. Without this retry logic, signups are lost. The solution is a queue that stores failed API calls and repeats them automatically.

A fourth problem shows up in larger installations: reporting granularity. mailingwork provides campaign statistics at recipient level; of these, only overview data can sensibly be shown in TYPO3. For detailed analyses (click heatmaps, open times, device distribution), you have to switch to the mailingwork dashboard. Gosign recommends showing only overview data in the TYPO3 backend and working directly in mailingwork for in-depth analysis.

Version status of the mailingwork extension and the upgrade to v12

As a commercial vendor, mailingwork has a business interest in keeping the TYPO3 integration current, because the TYPO3 market is a relevant sales channel. However, there is no public version of the extension in the TYPO3 Extension Repository, so which TYPO3 versions it supports cannot be checked there. Anyone moving from TYPO3 v10 to v12 or later should therefore clarify the integration with mailingwork or implement it as a custom integration via the API.