Predict age in Agify for new course enrollments in Tutor LMS to segment learners by age category
When a learner enrolls in a Tutor LMS course, Agify estimates an age from their first name, FlowMattic saves them in FluentCRM and a Router tags them as under 18, 18 to 39, or 40 and over.
Tutor LMS
Agify
FluentCRM
Router7 steps Setup ~12 min Used on 1.0k sites Free to import
What this workflow does
Course sites often serve very different learners, and the emails that suit a teenager rarely suit a retiree. Tutor LMS doesn't ask for age by default, but you usually have a first name. This workflow uses Agify to estimate an age from it and files each learner into an age group in FluentCRM.
The Tutor LMS trigger starts a run each time someone is enrolled in one of your courses. Agify's Predict Age step is already mapped to the learner's first name. Next, FluentCRM creates the contact, or updates it if that email already exists, with the email and first name from the enrollment.
A Router then sends the learner down one of three routes by predicted age: under 18, 18 to 39, and 40 and over. The routes compare whole numbers and can't overlap, so each learner follows exactly one. Every route ends with Add Tags to Contact, mapped to the learner's email. The tags themselves aren't chosen yet: after import, pick a tag for each route.
Treat the result as an estimate. If Agify returns no age, for example for an unusual name, the empty value counts as 0 and the learner lands on the Under 18 route. Each new enrollment runs the flow again, so a learner who joins a second course is checked and tagged again.
Age-appropriate follow-up emails
A language school sends younger learners study-game tips and older learners career-focused content, using the age tags in FluentCRM sequences.
Course recommendations by age group
An online academy promotes its exam-prep courses to the under 18 segment and its professional courses to the 18 to 39 segment.
Understanding who enrolls
A course creator checks FluentCRM to see how the three age tags are spread across learners when planning new courses.
How this workflow runs
What happens at each step once the workflow is on, and what you need before you import it.
Tutor LMS User Enrolls in CourseStarts the workflow on each new Tutor LMS course enrollment. The learner's email and first name are passed on to Agify and FluentCRM.
- Agify Predict Age
Predicts an age from the learner's first name, which the template already maps from Tutor LMS. Agify's answer is an estimate, and it may be empty for names Agify doesn't know.
- FluentCRM Create or Update Contact
Creates the learner as a FluentCRM contact, or updates the contact with that email, using the email and first name from the enrollment. This makes sure the contact exists before tagging.
- Router 3 paths
Sends the learner down one route by predicted age: Under 18 (less than 18), 18 to 39 (greater than 17 and less than 40), or 40 and over (greater than 39). An empty age counts as 0, so it takes the Under 18 route.
- FluentCRM Add Tags to Contact
Under 18 route: adds tags to the FluentCRM contact found by the learner's email. Pick the tag for this age group after import, as the template leaves it unset.
- FluentCRM Add Tags to Contact
18 to 39 route: tags the same FluentCRM contact, matched by email, with the tag you choose for this group. Choose that tag when you set the step up.
- FluentCRM Add Tags to Contact
40 and over route: adds the tag you choose for older learners to the FluentCRM contact matched by email. The tag is left for you to select after import.
What you need
- FlowMatticCore
- Tutor LMS PluginPlugin
- Agify AccountAccount
- FluentCRM PluginPlugin
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.
- To keep learners with no predicted age out of the Under 18 group, add a condition to that route that the age is greater than 0, so empty results take no route at all.
- Create the three tags in FluentCRM before import, such as age-under-18, age-18-39 and age-40-plus, so they are ready to pick in each route.
- Start a FluentCRM automation on each tag, so learners in each age group get their own welcome sequence.
- Change the route conditions if you want other bands, and keep them so they can't both match, because every route whose condition matches runs.
Questions about this workflow
How does Agify know a Tutor LMS learner's age?
It doesn't know it. Agify predicts a likely age from the first name, so two learners with the same name get the same estimate. Use the tags as a rough guide.
What happens if Agify returns no age for a learner?
The Router treats the empty value as 0, so the learner goes down the Under 18 route. Add a greater than 0 condition to that route if you want those learners left untagged.
Will a Tutor LMS learner already in FluentCRM be duplicated?
Create or Update Contact matches by email, so the existing contact is updated rather than duplicated, and the age tag is added to it.
Can a learner end up with two age tags in FluentCRM?
Not from one run, as the three routes don't overlap. If a later enrollment gets a different prediction, for example after the learner changes their first name, they could receive a second tag.
More AI Automation workflows
Other ready-to-import templates from the same category.
Import this workflow into your WordPress site
Download the JSON, import it from the Workflows screen and connect your accounts. Every run stays on your server, with no per-task fees.
30-day money-back guarantee Unlimited workflows and runs Self-hosted