Automate Gender API With Make: 3 Modules, No Code Required

What you can automate

What can the Gender API Make integration do for you?

The Gender API Make integration lets a Make scenario, the automation you build as a chain of bricks, ask Gender API for the likely gender behind a name or an email address. Each brick is called a module. You pick the module, point it at the contact data coming from another app, and Make writes the answer wherever you need it next, without a line of code.

Cleaner lead records. When a signup form or a CRM hands a new lead to Make, Get Gender from a Name reads the first name and passes the result on, so the record gets a gender value the sales team can filter on.

Emails with only an address. Plenty of newsletter lists hold nothing but an email. Get Gender from an E-Mail works from that address alone, which saves you from asking subscribers for more information.

Segmented campaigns. Once the gender sits in your spreadsheet or email tool, Make can route each contact to the right audience. If you want a request the two ready-made modules do not cover, Make an API Call reaches the Gender API endpoints through the same connection.

Know the limits before you build: Gender API has no trigger in Make, so something else has to start the scenario, and the official Make documentation for this app is thin. The Make troubleshooting guide helps when a run fails, and the Make training covers the editor from scratch. The same app often has an n8n node too; n8n vs Make lays out the differences between the two tools.

Connect

How do you connect Gender API to Make?

01
Add a Gender API module
Inside your scenario, add any Gender API module, then click Create a connection. A connection is your Gender API account linked to Make once and reused by every module of the app afterward.
02
Name it and authorize
Give the connection a name if you like, something that tells you which account it uses. Then either approve Make on the Gender API page that opens, or paste the key that Gender API gives you, depending on what the window asks for.
03
Save and check
Click Save. The connection now appears in the module's dropdown, and the other Gender API modules in your scenarios can pick it without asking you to log in again.

First scenario

Your first scenario with Gender API

GoalWhen a new contact reaches Make from another app, Gender API reads the first name and Make passes the gender on to the next step.

01
Create the scenario
Open the Scenarios page, create a new scenario and click the + to add the first module. Since Gender API has no trigger, start with the app where your contacts live, such as your form tool or CRM.
02
Connect the contact source
Search that app by name, pick the module that brings in new contacts, and click Create a connection. Once it is linked, Make lists the forms, sheets or objects it can read.
03
Add Get Gender from a Name
Click the + on the right of the first module, search Gender API and choose Get Gender from a Name. Map the first name coming from the previous module into it.
04
Test with Run once
Click Run once. Make runs the scenario a single time, and each module shows the bundles it received, one bundle per contact. Check that the answer matches the name you sent.
05
Schedule and switch on
Open the clock on the first module to set the schedule, every 15 minutes by default, then switch the scenario on. Each module run on one bundle counts as one operation on your plan.

Modules

What each Gender API module does

Gender API gives you 3 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Gender API1

Get Gender from a Name

Action

In Make“GetS Gender from a Name.”

Hand this module a first name and it returns the gender Gender API associates with it, ready to map into your CRM, spreadsheet or email tool. It is the module to reach for first, because most forms ask for a name.

When to use it

a lead form collects first names and your sales team wants to filter or address contacts by gender.

Watch out

map the first name field specifically; a company name or a full address line in its place gives the module the wrong input.

Gender API2

Get Gender from an E-Mail

Action

In Make“Gets Gender from an E-Mail.”

This one works from an email address alone, so contacts that arrive with nothing else still get a gender value you can use downstream. Prefer it over the name module whenever the address is the only field your source provides.

When to use it

a newsletter signup captures just the email and you still want to segment the list.

Watch out

a shared inbox such as a team address holds no personal name, so review those answers before you rely on them.

Gender API3

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

With this module, any Gender API endpoint becomes reachable from your scenario, using the connection you already created. It fills the gap when the two ready-made modules do not offer the request you need.

When to use it

you need a Gender API feature that neither Get Gender from a Name nor Get Gender from an E-Mail exposes.

Watch out

you have to know the endpoint and its parameters yourself, since Make builds no form for them.

Need help

Need help automating Gender API with Make?

A person reads every message.

FAQ

Gender API and Make: common questions

01Is the Gender API Make integration free?

Yes, on the Make side. Gender API is a standard app, so it is available from the Free plan. That plan allows 2 active scenarios, at least 15 minutes between two scheduled runs, 5 minutes of execution at most and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) lower the interval to 1 minute and remove the cap on active scenarios. Usage is counted in operations per month, one per module run on one bundle. Your Gender API account itself is a separate matter.

02What do you need to connect Gender API to Make?

A Gender API account and a Make account. The Make documentation lists no other prerequisite. You add a Gender API module, click Create a connection, optionally name it, then either authorize Make on the Gender API page or paste the key the app provides, and click Save. Because the official documentation for this app is limited, keep your Gender API account settings open in case the connection window asks for something specific.

03Does the Gender API trigger work in real time?

No, because Gender API has no trigger in Make at all. All 3 of its modules are actions, so another app has to start the scenario. You can open the flow with a trigger from your form tool, CRM or spreadsheet, or let Make run the scenario on its own schedule, which is every 15 minutes by default on a new scenario. Whether the start is instant then depends on that other app's trigger, not on Gender API.

04What if the Gender API module you need is missing in Make?

Use Make an API Call. It can call any endpoint of the Gender API with the same connection your other modules use, so a request outside Get Gender from a Name and Get Gender from an E-Mail stays within reach. You will need to know the endpoint and its parameters. Note that Make currently provides only limited documentation for this app, so the Gender API reference is where you check what each endpoint expects.

05Should you use Make or n8n for Gender API?

It depends on the tool your team already runs. Make offers Gender API as a standard app with 3 modules, including Make an API Call for anything the ready-made modules skip, and it is available from the Free plan. The same app often has an n8n node as well. The sensible choice is the platform where your other automations already live, so your contacts, connections and scenarios stay in one place.

Add a Gender API module

Name it and authorize

Save and check

Create the scenario

Connect the contact source

Add Get Gender from a Name

Test with Run once

Schedule and switch on

Need help automating Gender API with Make?