When a form is submitted on Getsitecontrol, add the lead to MailerLite

When a visitor fills in one of your Getsitecontrol forms, FlowMattic creates or updates that person as a MailerLite subscriber, ready for your MailerLite groups, automations and campaigns.

Getsitecontrol

MailerLite

Download this workflow Browse more workflows

2 steps Setup ~5 min Used on 549 sites Free to import

The When a form is submitted on Getsitecontrol, add the lead to MailerLite workflow on the FlowMattic canvas, with 2 steps across Getsitecontrol, MailerLite — The workflow as it appears in the builder after import. Each step opens for editing.

What this workflow does

Getsitecontrol popups and forms collect email addresses from visitors, but those leads only become useful once they sit in the tool you send email from. This workflow passes each submission to MailerLite straight away, so nobody has to export responses and import them by hand.

The Getsitecontrol trigger fires each time a form is submitted and hands the answers to FlowMattic. Every submission starts a run, whichever form on your site it came from, unless you narrow it later.

The MailerLite step then runs Create or Update Subscriber. FlowMattic describes it as creating a new subscriber or updating an existing one, with custom fields. If the email is already in MailerLite, the existing subscriber is updated instead of duplicated. The step ships unmapped: after import you connect your MailerLite account and map the form's email field, plus any name or other answers you want stored on the subscriber.

Submit a test entry through the live form once the mapping is done. Task History lists the fields Getsitecontrol sent and the response MailerLite gave, so you can check the subscriber landed with the details you expected.

Exit-intent popup leads to your newsletter

A blog shows a Getsitecontrol popup offering a free checklist, and every address entered there becomes a MailerLite subscriber who can receive the next issue.

Keeping returning visitors' details current

Someone who signed up last year fills in a new survey form with a different name, and their existing MailerLite subscriber record is updated rather than a second one being made.

Launch waitlist in MailerLite

A product team runs a Getsitecontrol waitlist form before launch and later emails everyone who joined from MailerLite on release day.

How this workflow runs

What happens at each step once the workflow is on, and what you need before you import it.

Step 1Trigger
Getsitecontrol Form is Submitted
Fires each time a visitor submits a Getsitecontrol form on your site. The submitted answers, such as the email address and name, are passed to the MailerLite step.
Step 2Action
MailerLite Create or Update Subscriber
Creates a MailerLite subscriber from the submission, or updates the existing one when the email is already there. The step ships unmapped: connect MailerLite and map the email and any other form fields.

What you need

FlowMatticCore
Getsitecontrol AccountAccount
MailerLite AccountAccount

After importing, map your own data. To keep the template universal, not every step is pre-filled. Open each step in the builder and connect your accounts and fields (channels, lists, sheets, recipients) before you switch the workflow on.

Make it yours

Changes worth making after you import it.

If you run several Getsitecontrol forms and only one should feed MailerLite, put a Filter between the Getsitecontrol trigger and the MailerLite step that checks a field only that form sends.
Map extra answers, such as a company name or interest, into MailerLite custom fields so you can segment those subscribers later.
Make the email field required in your Getsitecontrol form, because MailerLite needs an address to create or update a subscriber.

Questions about this workflow

What happens if the Getsitecontrol lead is already a MailerLite subscriber?

Create or Update Subscriber updates the existing subscriber instead of adding a duplicate, using the values you map. Run a test with an address you already hold and check the response in Task History.

Do all Getsitecontrol forms trigger this workflow?

As imported, yes: the trigger fires on any form submission it receives. To limit it, add a condition on a field that only the chosen form sends, using a Filter placed between the trigger and the MailerLite step.

Which fields does MailerLite receive?

Only what you map. The MailerLite step has no mapping in the template, so after import you pick the email field from the submission and add name or custom fields as you need them.

Can I add the lead to a specific MailerLite group?

FlowMattic's MailerLite integration also has an Add Subscriber to a Group action. Add it after the Create or Update Subscriber step and map the same email, so the subscriber exists before it is grouped.