When a new question is answered in Survicate, update the corresponding contact in MailerLite

Each answer given to a Survicate survey question is sent to MailerLite, where the respondent’s subscriber record is updated with it, or created if that email isn’t on your list yet.

Survicate

MailerLite

Download this workflow Browse more workflows

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

The When a new question is answered in Survicate, update the corresponding contact in MailerLite workflow on the FlowMattic canvas, with 2 steps across Survicate, MailerLite — The workflow as it appears in the builder after import. Each step opens for editing.

What this workflow does

Survey answers tell you what a subscriber wants, but they sit in Survicate while your emails go out from MailerLite. Getting an answer onto the subscriber record usually means an export and an import. This workflow writes answers to MailerLite as they arrive, so you can segment on them.

The Survicate trigger fires each time a respondent answers a question. FlowMattic passes that answer to MailerLite with the Create or Update Subscriber action, which matches the subscriber and writes the values you map, including custom fields. If MailerLite has no subscriber with that email, the action creates one.

The trigger works per question, not per survey. A survey with four questions answered by one person starts four runs, each carrying one answer. MailerLite needs an email address to match on, so the Survicate response must include the respondent's email. Answer a test survey yourself and check Task History to confirm the email arrives with each answer before you map the fields.

Store a topic preference for email segments

A one-question Survicate survey asks which topics a reader wants, and the answer is written to a MailerLite custom field you can build a segment on.

Record satisfaction scores on subscribers

A score question in a post-purchase survey updates a MailerLite field, so you can later email customers who gave a particular score.

Capture role or company size

A B2B newsletter asks readers about their role, and the reply is saved on their MailerLite subscriber for more relevant content.

How this workflow runs

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

Step 1Trigger
Survicate New Question Answer
Fires whenever a respondent answers a question in your Survicate survey. Each answer starts its own run and carries the question and response data for mapping.
Step 2Action
MailerLite Create or Update Subscriber
Updates the matching MailerLite subscriber with the answer, or creates the subscriber if the email isn't there yet. Map the respondent's email and put the answer into the custom field you want.

What you need

FlowMatticCore
Survicate 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.

Create the MailerLite custom field for the answer before you map the step, so it appears as a field you can choose.
If your survey has several questions, add a Filter after the trigger that continues only for the question you care about, so other answers don't overwrite the same field.
Prefer one update per finished survey? Swap the trigger for Survicate's New Survey Completion trigger and remap the MailerLite fields from its data.

Questions about this workflow

Does Survicate send every answer to MailerLite?

Yes, as imported. Every answered question starts a run, so each answer reaches the MailerLite step. Add a Filter on the question if you only want some of them.

What if the Survicate respondent isn't a MailerLite subscriber yet?

The action is Create or Update Subscriber, so MailerLite adds them as a new subscriber when no record matches the email. If you only want existing subscribers updated, this template isn't set up for that as imported.

What if the survey is anonymous and has no email?

MailerLite has nothing to match the answer to, so the step can't update anyone and Task History shows the response for that run. Collect or pass the respondent's email in Survicate first.

Will a later answer replace an earlier one in MailerLite?

If two answers are mapped to the same custom field, the later run writes over the earlier value. Map different questions to different fields, or filter by question, to keep each answer.