PHPackages                             xqueue/typo3-plugin - PHPackages - PHPackages  [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register)

1. [Directory](/)
2. /
3. [API Development](/categories/api)
4. /
5. xqueue/typo3-plugin

Abandoned → [xqueue/typo3-maileon-integration](/?search=xqueue%2Ftypo3-maileon-integration)Typo3-cms-extension[API Development](/categories/api)

xqueue/typo3-plugin
===================

The Official TYPO3 Maileon integration Package

v4.1.0(6mo ago)03.9kGPL-3.0-or-laterPHP

Since Aug 17Pushed 2mo agoCompare

[ Source](https://github.com/xqueue/typo3-maileon-integration)[ Packagist](https://packagist.org/packages/xqueue/typo3-plugin)[ RSS](/packages/xqueue-typo3-plugin/feed)WikiDiscussions main Synced today

READMEChangelog (8)Dependencies (3)Versions (10)Used By (0)

Typo3 - Maileon Integration Package
===================================

[](#typo3---maileon-integration-package)

This extension provides seamless integration between TYPO3 Forms and [Maileon](https://www.maileon.com/), a powerful email marketing platform. It enables automatic contact synchronization from frontend forms, including support for custom fields, DOI processes, and subscription/unsubscription workflows.

Features
--------

[](#features)

- ✅ Integrates with TYPO3's `form` extension
- ✅ Map form fields to Maileon standard or custom fields
- ✅ Automatically create missing custom fields in Maileon
- ✅ Handles Single Opt-In, Confirmed Opt-In, and Double Opt-In flows
- ✅ Sends subscription and unsubscription requests via the Maileon API
- ✅ Configurable via Extension Settings (Admin UI)
- ✅ Supports Finisher presets in the form editor

Requirements
------------

[](#requirements)

- TYPO3 v12.4 or higher
- PHP 8.1+
- TYPO3 `form` system extension
- A valid Maileon API key

Minimal Dependencies
--------------------

[](#minimal-dependencies)

- TYPO3 CMS 12.4.x or 13.4.x for Typo3 - Maileon Integration Package 3.2.x
- TYPO3 CMS 11.5.0 or 12.4.99 for Typo3 - Maileon Integration Package 3.1.x
- TYPO3 CMS 10.4 or 11.4.99 for Typo3 - Maileon Integration Package 3.x

Installation
------------

[](#installation)

Install via Composer:

```
composer require xqueue/typo3-maileon-integration
```

Activate the extension in the TYPO3 Extension Manager.

Configuration
-------------

[](#configuration)

1. Go to **Admin Tools → Settings → Extension Configuration**.
2. Locate **TYPO3 Maileon Integration** and set:
    - Your **Maileon API Key**

Usage
-----

[](#usage)

1. Create a form using the **TYPO3 Form Editor**.
2. Add fields and set the `maileonFieldName` in each field’s.
3. Add the **Maileon Finisher** at the end of the form.
4. Configure the finisher options (e.g., permission, DOI settings).
5. Save and include the form on any page.

Standard vs Custom Fields
-------------------------

[](#standard-vs-custom-fields)

The extension automatically categorizes fields based on the `maileonFieldName`:

- **Standard fields**: `firstname`, `lastname`, `locale`, etc.
- **Custom fields**: Any field not in the standard list will be created in Maileon if it doesn’t exist.

Documentation
-------------

[](#documentation)

- [User Documentation](https://xqueue.atlassian.net/wiki/spaces/MSI/pages/482672647/Typo3+Form+version+v4.0)

###  Health Score

41

—

FairBetter than 87% of packages

Maintenance78

Regular maintenance activity

Popularity18

Limited adoption so far

Community9

Small or concentrated contributor base

Maturity50

Maturing project, gaining track record

 Bus Factor1

Top contributor holds 77.8% of commits — single point of failure

How is this calculated?**Maintenance (25%)** — Last commit recency, latest release date, and issue-to-star ratio. Uses a 2-year decay window.

**Popularity (30%)** — Total and monthly downloads, GitHub stars, and forks. Logarithmic scaling prevents top-heavy scores.

**Community (15%)** — Contributors, dependents, forks, watchers, and maintainers. Measures real ecosystem engagement.

**Maturity (30%)** — Project age, version count, PHP version support, and release stability.

###  Release Activity

Cadence

Every ~140 days

Recently: every ~77 days

Total

8

Last Release

65d ago

Major Versions

v3.2.1 → v4.0.02025-06-23

### Community

Maintainers

![](https://avatars.githubusercontent.com/u/37145530?v=4)[Maileon](/maintainers/xqueue)[@xqueue](https://github.com/xqueue)

---

Top Contributors

[![zsmannheim](https://avatars.githubusercontent.com/u/92795252?v=4)](https://github.com/zsmannheim "zsmannheim (7 commits)")[![alange-xqueue](https://avatars.githubusercontent.com/u/55449557?v=4)](https://github.com/alange-xqueue "alange-xqueue (1 commits)")[![itops-xqueue](https://avatars.githubusercontent.com/u/55448834?v=4)](https://github.com/itops-xqueue "itops-xqueue (1 commits)")

### Embed Badge

![Health badge](/badges/xqueue-typo3-plugin/health.svg)

```
[![Health](https://phpackages.com/badges/xqueue-typo3-plugin/health.svg)](https://phpackages.com/packages/xqueue-typo3-plugin)
```

###  Alternatives

[pagemachine/typo3-formlog

Form log for TYPO3

23238.6k8](/packages/pagemachine-typo3-formlog)[typo3/cms-styleguide

TYPO3 extension to showcase TYPO3 Backend capabilities

106760.3k32](/packages/typo3-cms-styleguide)[friendsoftypo3/content-blocks

TYPO3 CMS Content Blocks - Content Types API | Define reusable components via YAML

103519.9k52](/packages/friendsoftypo3-content-blocks)[eliashaeussler/typo3-form-consent

Extension for TYPO3 CMS that adds double opt-in functionality to EXT:form

1595.5k](/packages/eliashaeussler-typo3-form-consent)[hn/typo3-mcp-server

TYPO3 extension that provides a Model Context Protocol (MCP) server for interacting with TYPO3 pages and records

8523.4k1](/packages/hn-typo3-mcp-server)[7elix/styleguide

TYPO3 extension to showcase TYPO3 Backend capabilities

10727.3k](/packages/7elix-styleguide)

PHPackages © 2026

[Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)
