Send Drupal Webform submissions to your email platform
ClickSyncr connects forms built with Drupal’s Webform module to email platforms through separate integration modules. Choose the module for your destination, connect an API key, and map the form values you want to send.
Choose from 15 Drupal modules
Each integration has its own Drupal.org project listing. Start with the platform that holds your subscribers, then check that project’s release requirements against your Drupal installation.
- beehiiv
- Benchmark Email
- Brevo
- Campaign Monitor
- Drip
- Elastic Email
- EmailOctopus
- GetResponse
- Kit
- Klaviyo
- Loops
- Mailchimp
- MailerLite
- Moosend
- SendPulse
The destination depends on the platform. Kit uses a form, Mailchimp an audience, and MailerLite a group. Brevo and Klaviyo use lists. Choose the actual destination during setup, rather than assuming the same label applies to every integration.
Prepare Webform and the site
You need the Webform module, an account at the destination platform, and its API key. Review the integration’s README before installation. The current MailerLite source requires Drupal 11.1 or later; the Kit, Brevo, Klaviyo, and Mailchimp sources support Drupal 10.3 and Drupal 11. These modules require PHP 8.3 or later with OpenSSL.
Keep submission storage enabled. Drupal cron processes the saved delivery requests, so include cron in your setup checks. An accepted form submission and a completed email-platform delivery are separate events; inspect both when testing.
Configure the integration on your form
After installing and enabling the chosen module, open Structure > Webforms. Select your form and its destination tab, such as Kit or MailerLite. Paste the API key, select Connect, and choose the destination.
Map Email first. The other choices depend on your account and the selected destination. Kit offers First name and account custom fields. Mailchimp loads audience merge fields. Avoid copying a mapping from another account without checking which fields are available.
Review consent for each form
MailerLite requires a marketing-consent checkbox. Kit, Brevo, Klaviyo, and Mailchimp let you select a consent checkbox; when selected, only submissions with it checked are sent. Review the handler’s saved selection before testing. Subscriber status choices also vary, so follow the settings shown by the module you installed.
Check the delivery result
Submit a completed test using a contact you control. Once cron runs, inspect the submission’s destination tab and check the subscriber at the email platform. Compare the mapped values with what you entered. Repeat with consent unchecked when the handler has a consent condition.
If the module reports that it could not connect, check the API key and try again. If it cannot load the destination, reconnect and select it again. Refresh the available fields after changing the destination, then review required mappings before saving.
Use the official project listing for the module’s releases and issue queue. Include the module and Drupal versions when describing a reproducible problem, and leave credentials and personal submission data out of the report.