Predict gender in batch in Genderize for new form responses in Typeform

Each new Typeform response sends the names it contains to Genderize, which returns a predicted gender for each one. Use it as the starting point for tagging or segmenting respondents by name.

Typeform

Genderize

Download this workflow Browse more workflows

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

The Predict gender in batch in Genderize for new form responses in Typeform workflow on the FlowMattic canvas, with 2 steps across Typeform, Genderize — The workflow as it appears in the builder after import. Each step opens for editing.

What this workflow does

Typeform collects names, but it says nothing about how your respondents split by gender unless you ask them directly. Many forms don't, and adding a question can feel intrusive. This workflow takes the names people already typed and asks Genderize for a prediction as each response arrives.

The Typeform trigger fires when someone submits the form you connect. FlowMattic then runs the Predict Gender (Batch) action in Genderize, which handles several first or full names in one request. You map one or more name answers from the response into it, for example a contact name plus the names of guests listed on the same form.

Genderize sends back its prediction, and the run ends there. Nothing stores or uses the result as imported, so you will want to add a step after Genderize that writes it somewhere, such as a spreadsheet row or a CRM field. Task History keeps each run, so you can read what Genderize returned while you decide where it should go.

Group bookings with several attendee names

A Typeform registration form asks for the names of everyone in a party. All of them go to Genderize in one batch request instead of one call per name.

Audience mix for a survey report

A research team runs a Typeform survey without a gender question and adds a later step that logs each prediction, giving a rough split to report alongside the answers.

Choosing a greeting style

A shop that greets new contacts by title can use the prediction in a later step to pick wording, keeping a neutral fallback for names Genderize can't place.

How this workflow runs

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

Step 1Trigger
Typeform New Form Submission
Fires each time someone submits the Typeform form you connect. Every answer, including the name fields, becomes data you can map in the Genderize step.
Step 2Action
Genderize Predict Gender (Batch)
Sends the names you map to Genderize, which predicts a gender for each first or full name in a single request. The response is available to any step you add after it, but nothing uses it as imported.

What you need

FlowMatticCore
Typeform AccountAccount
Genderize 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.

Add a Google Sheets Add New Row step after Genderize and map each name next to its prediction, so the results are kept outside Task History.
If your form only ever holds one name, swap the batch step for Genderize's single Predict Gender action, which takes one first or full name.
Submit a test response with names you know, then open Task History to see how Genderize lays out its reply before you map it into a later step.

Questions about this workflow

Where does the Genderize prediction end up?

Only in the run's Task History, as imported. The template stops after Genderize, so add a step such as a Google Sheets row or a CRM update and map the prediction into it.

Why use the batch action for a single Typeform response?

It lets one response send several names at once, which suits forms that list guests, team members or children. For a form with a single name field, Genderize's one-name action works just as well.

Does this change anything in my Typeform account?

No. The trigger only reads new responses. Your form, its questions and the stored responses stay as they are.

Do I need a Genderize account to use this template?

The Genderize step runs through the connection you set up in FlowMattic when you import it. Check Genderize's own terms for how many predictions your account allows.