Connect your Drupal Webform forms. Send every lead to six email platforms.

ClickSyncr connects Drupal Webform to six email platforms. A consenting submission becomes a subscriber in the group you choose, you map the fields inside Drupal, and every delivery is recorded next to the saved submission.

Six modules, one pattern

Each platform is its own module on Drupal.org, and they all behave the same way. Install the one you need.

• MailerLite: drupal/webform_integration_for_mailerlite
• Mailchimp: drupal/webform_integration_for_mailchimp
• Klaviyo: drupal/webform_integration_for_klaviyo
• GetResponse: drupal/webform_integration_for_getresponse
• Campaign Monitor: drupal/webform_integration_for_campaign_monitor
• Beehiiv: drupal/webform_integration_for_beehiiv

What you need

• Webform on Drupal 11, using a Webform 6 release built for Drupal 11.
• PHP 8.3, 8.4 or 8.5, whichever your Drupal version supports, with OpenSSL and AES-256-GCM.
• An account and API key at whichever platform you are connecting.
• A public HTTPS site, not installed in a URL subdirectory, running Drupal cron every minute on the default database queue.

The Key module is not a dependency. Earlier builds asked you to configure protected key references and have a server administrator place encryption files by hand. That is gone. The module registers your site and encrypts its own credentials.

Connecting a form

1. Install the module you need with Composer and enable it. Enable Webform UI if you want to manage forms in the browser.
2. Open Structure > Webforms, pick a form, and select the tab for your platform.
3. Paste your API key and click Connect. The module verifies the site with ClickSyncr, registers it, and encrypts the credentials for you.
4. Choose a group, map Email plus any other fields, and select your marketing-consent checkbox. Subscriber status defaults to Active.
5. Save, and leave Webform submission storage enabled.

Connecting needs the broker to reach a temporary verification route on your site. A firewall or a login gate in front of Drupal will stop enrollment there.

Checking that it worked

Submit the public form with consent ticked. Under Results > Submissions, refresh and the status moves through Queued, then Processing, then Delivered. Click a status for the detail, or send a submission again from there.

Delivered means the platform accepted the subscriber. It does not mean a campaign email went out, and it does not track what happens to the contact afterwards. Drafts and submissions without consent are never sent, and an ordinary edit does not resend one.

What ClickSyncr receives

Over HTTPS: the values you mapped, their field types, the consent flag, subscriber settings, the submission identifier, and your API key. Values you did not map are not sent. Say so on your public form, and set submission retention to suit you.

Drupal encrypts saved API keys and queued payloads with a key derived from your existing hash_salt. Keep that setting with your database backups, because changing or losing it makes stored credentials and pending payloads unreadable. This protects a database-only disclosure, not a compromised running server, and a cloned database must not send using another site’s registered identity.

Deleting a Drupal submission does not unsubscribe the contact at your platform. Pending deliveries block uninstall, and if deliveries stall, check Reports > Status report and your cron.

How this differs from the other MailerLite module

Webform MailerLite integration also turns submissions into subscribers and supports groups, using MailerLite’s official PHP library with the API key configured in Drupal settings.

These modules send through the ClickSyncr service instead, which is why they need enrollment. In exchange you get the group and field mapping screen on the form itself, mapped consent as a requirement rather than an option, and a delivery outcome recorded against every saved submission. One pattern across six platforms, rather than six different ones.

If you also run WordPress

The WordPress side is wider. ClickSyncr connects more than twenty platforms there, across seven form builders, with the same consent-first approach.

Support

Maintained by ClickSyncr. Report reproducible bugs and request features in each module’s Drupal.org issue queue, with your Drupal, Webform and module versions. Never include API keys or personal submission data in an issue.

Every module ships a README covering installation, connection, mapping, delivery checks and recovery. ClickSyncr service access is separate from the GPL-2.0-or-later license, so confirm terms and any charges before you install. These are independent integrations, not official modules from the platforms they connect to.