Add the fields
Use the native builder workflow and save the ClickSyncr configuration.
Drupal Webform integration layer
Connect Webform to your subscriber list ClickSyncr adds email-platform handlers to forms built with Drupal Webform. A handler connects one form to an account destination, maps submitted values,…
Inside the form workflow
Prepare the form first, then configure ClickSyncr beside the settings you already use.
Use the native builder workflow and save the ClickSyncr configuration.
Use the native builder workflow and save the ClickSyncr configuration.
Use the native builder workflow and save the ClickSyncr configuration.
Use the native builder workflow and save the ClickSyncr configuration.
Use the native builder workflow and save the ClickSyncr configuration.
ClickSyncr adds email-platform handlers to forms built with Drupal Webform. A handler connects one form to an account destination, maps submitted values, and records delivery results alongside saved submissions.
Start with the account where you want subscribers to arrive. The Kit integration targets a Kit form. The MailerLite integration targets a group, while Mailchimp uses an audience. Brevo and Klaviyo use lists.
Install the matching Drupal integration module. For example, the MailerLite module listing provides its releases and requirements. Check the chosen release before installing it, especially when working across different Drupal versions.
Use the Webform module and keep submission storage enabled. Create the fields you want visitors to complete, including an email field. Add a checkbox if the form needs to record a marketing choice. MailerLite requires this checkbox; the other four handlers let you choose whether to use one.
Have the destination account’s API key ready. The integration also needs Drupal cron to process saved delivery requests. Check that cron runs before treating a successful form submission as a successful subscriber transfer.
Go to Structure > Webforms, choose the form, and select the email platform’s tab. The tab opens its handler configuration. If no matching handler exists, it opens the add-handler form. If several exist, choose which one to edit.
Paste the API key and select Connect. Choose the form, group, list, or audience shown for that account. The integration then loads the field choices for your destination. Save the handler after mapping and reviewing consent.
Email mapping is required. Map optional fields only when you collect a corresponding value. Kit includes First name and custom fields; MailerLite loads its account fields; Brevo loads normal contact attributes. Mailchimp uses the chosen audience’s merge fields. Klaviyo offers profile fields and an option to add further profile properties.
Use the displayed field names and types to check each match. A label alone can be misleading when a form has several similar elements. After changing an account or destination, reload the fields and review the saved mappings.
For MailerLite, select Marketing consent checkbox. For Kit, Brevo, Klaviyo, or Mailchimp, selecting Consent checkbox limits delivery to checked submissions. MailerLite and Mailchimp offer Active and Unconfirmed subscriber status choices. Confirmation email behavior depends on the destination account’s settings.
Complete a test submission, let cron run, and open the submission’s platform tab. Review the result and compare the subscriber’s stored fields with your test values. Test an unchecked consent box too when consent is configured.
“Could not connect” calls for checking the API key and connecting again. “Could not load this group” in MailerLite calls for reconnecting and choosing the group again. When saving asks you to refresh fields, reload the destination and check the required mappings. Read the delivery result before deciding whether to send a submission again.
Your next subscriber is one connection away
Install ClickSyncr, connect your platform, and publish your first tested sync in about two minutes.
Built by Renzo Johnson