Connect Drupal Webform. Send every lead to MailerLite.

Connect Drupal Webform to MailerLite

ClickSyncr sends Drupal Webform submissions to a MailerLite group. Connect your account inside the webform, match its fields, and save the handler to prepare new submissions for delivery.

What you need

Use Drupal 11.1 or later, Webform 6, and PHP 8.3 or later with OpenSSL. You also need a MailerLite account, an API key, and a group to receive subscribers. Keep Webform submission storage enabled and Drupal cron running: the module sends saved delivery requests when cron runs.

Install and open the handler

Install and enable Webform Integration for MailerLite from Drupal.org. Open Structure > Webforms, choose your form, and select its MailerLite tab. The tab opens the handler configuration. If more than one matching handler exists, choose the handler you want to edit.

Connect your API key

Paste your key into MailerLite API key and select Connect. Then choose the MailerLite group. The field mapping options load for that destination. To replace a saved key, paste the replacement and connect it before saving the configuration.

Map the fields you collect

Email is required. Other field names come from your MailerLite account, including its custom fields. The integration loads each field’s label and its text, number, or date type. Use those displayed names as your mapping list; a field created in one account may not exist in another.

For each destination field, select the matching element from your webform. Start with Email, then review the optional mappings. Check the displayed field types as well as their names so that a date or number is connected to the intended value.

Set consent and subscriber status

Choose the Marketing consent checkbox that records the visitor’s choice. Only completed submissions with that checkbox checked are sent to MailerLite. Save the handler after selecting it. Subscriber status offers Active and Unconfirmed. Confirmation email behavior depends on your MailerLite settings, so test the selected status before accepting signups.

Test a completed submission

Submit the public form using a test contact you control, with the configured consent checkbox checked. After cron runs, open the saved submission’s MailerLite tab and inspect its delivery result. Check the contact in your selected group, including each mapped value. If you configured consent, submit another test with it unchecked and confirm that it is not sent.

Resolve connection and mapping errors

“Could not connect to MailerLite.” Check the API key and reconnect; the error message confirms that the saved mapping has not changed. “Could not load this group.” Reconnect and select the destination again. If the account has no groups, create one in MailerLite, then reconnect.

If saving asks you to refresh fields and groups, reload them and review the selected sources. A saved submission is not proof of delivery. Read its result before trying again, then correct the reported value or setting. An authorized administrator can use Send again from the submission’s delivery screen.

See the MailerLite integration overview for the destination’s ClickSyncr page.

Frequently asked questions

What happens to the saved MailerLite API key if Drupal’s hash salt changes?

The module encrypts the saved MailerLite credential with a key derived from Drupal’s hash salt. Changing that salt means the old encrypted value cannot be opened with the new key. Reconnect the MailerLite API key after the change, then test the handler again. A copied database alone does not recreate the encryption context needed to read the saved credential.

Does Send again use the original MailerLite mapping or the current one?

Send again rebuilds the delivery from the submission’s current saved values and the current handler mapping. The consent rule and handler conditions must still pass. It does not replay the original request unchanged. Review the earlier MailerLite result before confirming: an unresolved earlier delivery may still complete, and the retry form rejects deliveries already marked accepted or still pending.

How can I tell which mapped fields MailerLite accepted or dropped?

Open the saved submission’s MailerLite tab and read the Fields column alongside Delivery state and Reason. When the service returns field details, the module shows how many fields were kept and names dropped fields with their reported reasons. An empty Fields cell means no field summary is available; it does not establish that every mapped value was accepted.