What is your goal?
Send new subscribers to Mailerlite groups (and into that specific Mailerlite workflow) based on answers in Tally quiz.
I’m building a Tally → Make → MailerLite automation. The flow is: Tally quiz submission triggers Make, which creates/updates a subscriber in MailerLite, then a Router splits into 3 paths based on the answer to Question 5, with each path using an “Add Subscriber to a Group” module to assign the subscriber to one of three MailerLite groups.
The subscriber is being created in MailerLite successfully, but they are not being added to any group. The “Add Subscriber to a Group” module requires a Subscriber ID. I’ve tried mapping this using both the Tally email variable ({{1.fields.Enter your email}}) and the MailerLite Create/Update variables, but neither successfully adds the subscriber to the group — they remain as a subscriber with no group assigned.
What is the correct variable to use in the Subscriber ID field of the “Add Subscriber to a Group” module when the subscriber has just been created in the same scenario? Is there a better way to structure this flow so the subscriber is both created and added to the correct group in one clean path?
What is the problem & what have you tried?
Subscribers are being added as subscribers in mailerlite but not entering the group as I’ve instructed in Make and therefore not that workslow. I think there is a problem with the variables - possibly the Subscriber ID field.
Screenshots (scenario flow, module settings, errors)
Hey @Sheryl_Hickey !
You should usually use the Subscriber ID returned by the MailerLite Create/Update Subscriber module, not the email from Tally.
The Add Subscriber to a Group step expects MailerLite’s internal subscriber ID, so if you map the email instead, it often won’t add them to the group.
I’d check the output of the Create/Update Subscriber module and map its subscriber ID directly into the Add Subscriber to a Group module.
If that still doesn’t work, a cleaner setup is to skip the separate group step if your MailerLite module supports assigning groups during subscriber creation/update. If not, keep your current structure but make sure each router path uses the subscriber ID coming from the MailerLite step, not from Tally.
Dr. Tanvi Sachar
Monday Certified Partner, Tuesday Wizard
Hi thanks for this. But I’m not even sure what to look for or how to set this up. I.E what do I click on for this?
I just don’t know how to assign groups to make sure subscribers go into the correct group. Essentially I want it to be - they do the quiz in Tally > last question differentiates what group they go into > they get sent into their answer’s corresponding group > they enter the Mailerlite workflow that triggers my automation (withing Mailerlite).
I hope I am explaining it clearly enough. I’ve contacted support and they sent me a loom about nothing to do with what I’m asked and I’m more confused than ever. I’ve spent an entire day and evening trying to figure this out, so I really appreciate your help!
I’ve now set it up differently to before as this seemed more intuitive but only one of the automations fired for one of the answers. Whereas when I filled in the quiz again with the other answers nothing happened.
Please see most recent screenshot. Thanks so much again!
Hey @Sheryl_Hickey !
Your structure is close. The part that usually causes confusion is the Subscriber ID field.
In the “Add Subscriber to a Group” module, you should not use the email from Tally. Instead, map the Subscriber ID that comes from the “Create / Update a Subscriber” module.
What to do step by step:
-
Open the “Add Subscriber to a Group” module.
-
In the Subscriber ID field, click inside the field so the mapping panel appears.
-
From the previous MailerLite module (Create / Update a Subscriber), select the Subscriber ID value from its output.
-
Do this for each of the three group modules.
This works because when the subscriber is created or updated, MailerLite returns its internal ID. That is the value the next modules expect.
For the router part, each path should have a filter based on the answer to the last Tally question. For example:
If Question 5 equals “The Hype Roma…” then send to Group A.
If Question 5 equals “Prompt Spiraler” then send to Group B.
If Question 5 equals “Voice on Vacation” then send to Group C.
If only one path ran in your tests, it usually means the filter condition only matched that one answer. It helps to open the Tally module output from a test run and copy the exact value of the answer so the filter matches it exactly.
Your flow itself is fine:
Tally submission triggers the scenario, MailerLite creates or updates the subscriber, the router checks the quiz answer, and the matching path adds the subscriber to the correct group which then triggers the MailerLite automation.
Dr. Tanvi Sachar
Monday Certified Partner, Tuesday Wizard
Use the Subscriber ID from the MailerLite Create/Update Subscriber module, not the Tally email.
The email is fine for creating/updating the subscriber, but the Add Subscriber to a Group step wants the actual MailerLite subscriber ID from the previous MailerLite step. MailerLite treats group membership separately from just creating the contact.
So the clean setup is:
Tally → MailerLite Create/Update Subscriber → Router → Add Subscriber to Group
Then in each Add Subscriber to Group module, map the ID/output from Create/Update Subscriber. Not the Tally email. If you map the email there, it usually won’t work the way you expect.
If you want, I can also write you a super short reply version you can paste directly into the Make thread.
