flowmailer / m2connector
flowmailer/m2connector
Flowmailer Connector for Magento 2
Magento 2 Connector for Flowmailer
This extension allows you to configure Magento 2 to send all emails using Flowmailer including raw data.
See flowmailer.com for more information.
Compatibility
| Module version | Magento / Adobe Commerce | PHP |
|---|---|---|
^2.2 |
2.4.7, 2.4.8 (+ patches) | 8.1, 8.2, 8.3, 8.4 |
^2.1 |
2.4.4 – 2.4.8 | 7.4, 8.0, 8.1, 8.2 |
^1.0 |
2.3, 2.4 (< 2.4.4) | 7.3, 7.4, 8.0 |
Magento 2.4.8 removed the laminas/laminas-mail dependency. Module versions < 2.2 therefore
fail at runtime on 2.4.8 with Class "Laminas\Mail\Message" not found. Upgrade to ^2.2.
Installation
A normal installation would be something equal to:
composer require flowmailer/flowmailer-php-sdk flowmailer/m2connector symfony/http-client nyholm/psr7
Choose your preferred flowmailer-php-sdk implementations on packagist, based on your minimum requirement for PHP.
Choose your preferred client implementations on packagist.
See docs.php-http.org for details on the HttpClient discovery.
Enable the module:
bin/magento module:enable Flowmailer_M2Connector --clear-static-content
bin/magento setup:upgrade
bin/magento setup:di:compile
bin/magento module:status Flowmailer_M2Connector
bin/magento cache:clean
Configuration
Obtain credentials from Flowmailer credentials wizard
Go to http://your-magento-store/admin and login with your admin credentials.
Navigate to Stores > Configuration > Flowmailer > Connector and add API Credentials.
Upgrading to 2.2.x
The 2.2 release removes the hard dependency on laminas/laminas-mail, which was
removed from Magento core in 2.4.8. The plugin now consumes Magento's own
Magento\Framework\Mail\MessageInterface directly. Existing template-variable
handling and admin configuration are unchanged.
After upgrade run:
composer update flowmailer/m2connector flowmailer/flowmailer-php-sdk
bin/magento setup:upgrade
bin/magento setup:di:compile
bin/magento cache:flush
Development
Static analysis uses the official PHPStan bridge for Magento.
composer install
composer analyse
See phpstan.neon for the configured rule level.
No changelog yet
The vendor hasn't published a changelog. Tagged releases appear in the Versions tab.
| Version | Stability | QA Status | Compatibility | Released |
|---|---|---|---|---|
| 2.2.0 | stable | Fail | Not yet tested Details | 2026-06-30 13:29:12 |
| 2.1.1 | stable | Fail | Not yet tested Details | 2026-06-29 08:10:36 |
| 2.1.0 | stable | Fail | Not yet tested Details | 2024-12-16 10:49:15 |
| 2.0.0 | stable | Not tested | Not yet tested Details | 2022-06-01 09:51:08 |
| 1.0.15 | stable | Not tested | Not yet tested Details | 2021-09-08 12:02:48 |
| 1.0.13 | stable | Not tested | Not yet tested Details | 2020-10-19 13:31:11 |
| 1.0.11 | stable | Not tested | Not yet tested Details | 2020-07-30 07:24:10 |
| 1.0.10 | stable | Not tested | Not yet tested Details | 2019-12-20 12:22:01 |
| 1.0.8 | stable | Not tested | Not yet tested Details | 2019-05-06 09:18:26 |
| 1.0.7 | stable | Not tested | Not yet tested Details | 2019-04-24 13:26:58 |
| 1.0.4 | stable | Not tested | Not yet tested Details | 2019-04-17 08:26:01 |
| 1.0.3 | stable | Not tested | Not yet tested Details | 2019-01-02 15:52:45 |
| 1.0.2 | stable | Not tested | Not yet tested Details | 2018-12-21 15:27:32 |
| 1.0.1 | stable | Not tested | Not yet tested Details | 2018-11-30 09:59:17 |
| 1.0.0 | stable | Not tested | Not yet tested Details | 2018-11-29 14:23:18 |
Requires 5
| Package | Constraint |
|---|---|
| flowmailer/flowmailer-php-sdk-implementation | ^1.0 || ^2.0 |
| magento/framework | ^103.0 |
| magento/module-sales | ^103 |
| php | ^8.1 |
| psr/log | ^1.0 || ^2.0 || ^3.0 |
Requires-dev 12
| Package | Constraint |
|---|---|
| bitexpert/phpstan-magento | ^0.30 || ^0.31 |
| ergebnis/composer-normalize | ^2.23 |
| flowmailer/flowmailer-php-sdk | ^2.3 |
| friendsofphp/php-cs-fixer | ^3.50 |
| icanhazstring/composer-unused | ^0.8 |
| maglnet/composer-require-checker | ^4.0 |
| nyholm/psr7 | ^1.8 |
| phpstan/extension-installer | ^1.4 |
| phpstan/phpstan | ^1.10 || ^2.0 |
| phpunit/phpunit | ^9.6 || ^10.0 |
| rector/rector | ^1.0 |
| symfony/http-client | ^6.4 || ^7.0 |
Compatibility
Each Magento release line is installed on its supported PHP versions, then the module is built (DI compilation + static-content deploy) and its unit and integration suites are run. The matrix shows the lines and PHP versions the module is confirmed to install and run on. Code-quality results further down (phpstan, phpcs, …) are reported separately and never affect compatibility.
| Magento | PHP 8.2 | PHP 8.3 | PHP 8.4 | PHP 8.5 |
|---|---|---|---|---|
| 2.4.7 | not tested | not tested | ||
| 2.4.8 | not tested | not tested | ||
| 2.4.9 | not tested | not tested |
Code Quality
Advisory checks against the module's source. Static analysis runs once across the whole module; PHPStan re-runs per Magento + PHP version because resolvable symbols differ between releases. These NEVER affect the Compatibility badge. A phpcs finding can't make a module incompatible.
Static analysis
Coding standards (phpcs), mess detection (phpmd), copy-pasted code (cpd), PHP cross-version compatibility, composer.json validity. Each runs once for the whole module.
PHPStan
Type-checks the module's PHP against a real Magento install at the configured gate level. Re-runs per Magento and PHP version because resolvable symbols differ between releases.
Tests
Unit and integration suites, run for each applicable Magento and PHP version. A test failure speaks to the module's behaviour, not its compatibility with a Magento line, so it is reported here separately and never reddens the compatibility matrix.
Unit tests
| Magento | PHP 8.2 | PHP 8.3 | PHP 8.4 | PHP 8.5 |
|---|---|---|---|---|
| 2.4.7 | N/A | N/A | ||
| 2.4.8 | N/A | N/A | ||
| 2.4.9 | N/A | N/A |
Integration tests
| Magento | PHP 8.2 | PHP 8.3 | PHP 8.4 | PHP 8.5 |
|---|---|---|---|---|
| 2.4.7 | N/A | N/A | ||
| 2.4.8 | N/A | N/A | ||
| 2.4.9 | N/A | N/A |
Security
Security checks run directly against the module: an audit of its declared dependencies for known vulnerabilities (composer audit) and a scan of its source for malware and web-shell signatures. Each runs once. A malware detection fails the version outright.
Turn an existing module into recurring revenue.
If you already maintain a Magento 2 module on GitHub or GitLab, listing it on Packagento takes about five minutes. We mirror your tags, handle distribution signing, and route paid licenses through Stripe Connect, so you can keep shipping the way you already do.