Inxmail for TYPO3

Inxmail is the enterprise newsletter platform that connects natively to TYPO3 editorial teams

Companies with more than 50,000 newsletter recipients, strict compliance requirements and an existing TYPO3 website face a concrete decision: Mailchimp, with data processed in the US and the GDPR risk that comes with it, or a German solution that integrates directly into the existing content infrastructure. Inxmail Professional is that solution: servers in Germany, certified data processing and a TYPO3 extension that controls subscriber lists, templates and campaigns directly from the CMS.

The TYPO3 extension synchronizes subscriptions in both directions: new subscribers from TYPO3 forms land in Inxmail lists automatically, and unsubscribes in Inxmail are mirrored back to TYPO3. For marketing teams, that means one data source, no manual exports and no risk of outdated lists. In practice, this eliminates the most common newsletter mistake: sending to an outdated recipient list that still contains contacts who have already unsubscribed.

Typical use cases cover B2B newsletters, transactional emails and event communication

The main scenario is the classic B2B newsletter for companies with 10,000 to 500,000 recipients. The editorial team maintains content in TYPO3, and the extension transfers teasers and links into Inxmail templates automatically. Marketing managers segment recipients by industry, region or interest and send variants tailored to each audience. Open rates and click data flow back into the TYPO3 backend through the API, so the editorial team can see how individual articles perform.

The second scenario is transactional emails triggered by user actions on the website. A registration confirmation, a download link or an order confirmation isn’t sent through the local mail server but through the Inxmail infrastructure with guaranteed deliverability. SPF, DKIM and DMARC come preconfigured in Inxmail, which improves deliverability considerably compared with a standard PHP mailer.

The third scenario is event communication for companies that regularly run trade fairs, webinars or conferences. The invitation, reminder and follow-up emails are configured as trigger-based campaigns in Inxmail and set off by events in TYPO3, such as a registration through a powermail form. The trigger logic also supports more complex sequences: an invitation four weeks ahead, a reminder one week ahead, a confirmation the day before and a feedback request two days after.

Technical architecture connects TYPO3 frontend forms with the Inxmail REST API

The extension uses the Inxmail REST API for communication between TYPO3 and Inxmail Professional. At its core, the integration consists of three modules: a subscriber sync service, a template sync module and a campaign trigger.

The subscriber sync runs as a scheduler task that reconciles new subscriptions, changes and unsubscribes between TYPO3 and Inxmail at configurable intervals (typically every 5 to 15 minutes). The sync direction is configurable: one-way (TYPO3 to Inxmail) or two-way. With two-way sync, conflicts are resolved by timestamp, and the more recent record wins.

The template sync module transfers sections of TYPO3 pages as newsletter content. Editors flag content elements in the TYPO3 backend as “newsletter-ready”, and the extension renders these elements into an Inxmail-compatible HTML template. That spares the team from maintaining website content and newsletter content twice.

Authentication uses API keys configured in the TYPO3 Extension Manager. All API calls run over HTTPS, and the extension logs every sync run in a dedicated log table, which matters for compliance audits. The log entries contain timestamps, the number of synchronized records, errors and warnings, so an audit can show exactly when which data was transferred.

Common problems involve sync conflicts, template rendering and API rate limits

The most frequent support topic is sync conflicts in two-way synchronization. If a subscriber is changed in TYPO3 and in Inxmail at the same time, the data can become inconsistent. The solution: define a clear sync direction. In 90% of cases, TYPO3 is the leading source for master data and Inxmail the leading source for engagement data (opens, clicks, bounces).

The second problem is HTML rendering differences between the TYPO3 frontend and email clients. A content element that displays correctly on the website can look different in Outlook or Gmail. The extension does convert TYPO3 HTML to inline CSS for email compatibility, but complex layouts with Flexbox or Grid have to be simplified for email clients. We recommend testing newsletter templates separately, ideally with a tool such as Litmus or Email on Acid.

The third problem is API rate limits during large sync runs. If you synchronize 100,000 subscribers at once, you can hit Inxmail’s API limit. The solution: batch-based sync with a configurable batch size (recommended: 500 records per API call) and exponential backoff on rate-limit responses.

TYPO3 v12 is supported by the official extension, v13 needs to be checked

Inxmail maintains the TYPO3 extension actively, because the TYPO3 market is a relevant sales channel for Inxmail Professional. The current version supports TYPO3 v11 and v12. When upgrading from v10 to v12, the main work is adapting the scheduler task configuration, because TYPO3 v12 changed the scheduler API. API authentication and subscriber sync remain stable.

There is no official release for TYPO3 v13 yet. Companies planning a v13 upgrade should clarify availability with Inxmail early on, because enterprise newsletter integrations are among the most critical dependencies in a CMS upgrade. As an interim solution, the integration can run through a custom middleware layer that talks to the Inxmail API directly, without the extension. Gosign has built this solution for clients who wanted to move to v13 before the official extension was available. The custom layer also needs less maintenance, because it only calls the API endpoints that are actually used and carries no unused features along.