Resources · Make integration

Genderize Make integrationAutomate Genderize with Make.

Need a gender reading for the names flowing through your tools? The Genderize Make integration gives you 2 action modules and no trigger. This page shows how to link your account, where Genderize fits in a flow, and how to test it before you switch it on.

Try the Genderize integration on MakeSee the 2 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Genderize Make integration do for you?

The Genderize Make integration lets a Make scenario, the automation you build in Make, send a name to Genderize and use the answer in the next steps. It has 2 modules, both actions: Read a Gender by Name and Make an API Call. Genderize never starts a scenario by itself, another app or a schedule does.

Enrich a signup list. A form tool or a CRM hands over a new contact, Read a Gender by Name reads the name, and the result lands in a column of your sheet. The whole chain runs without code.

Reach an endpoint the module skips. Make an API Call sends a request to the Genderize API with the connection you already set up, handy when the listed module does not return what you need.

Clean an older base. Run a batch of existing contacts through the same module and write the answer back next to each record, then check a few rows by hand.

Know the limits before you build. The Make documentation for Genderize is flagged as limited: it lists no fields, no formats and no quotas, so plan to read the output of your first test carefully. Many teams start with the Make training, and the Make troubleshooting guide helps when a run fails. Genderize often has an n8n node as well; the n8n vs Make comparison sets out the criteria.

Connect

How do you connect Genderize to Make?

  1. 01

    Add a Genderize module

    In your scenario, click the + and search for Genderize, then pick Read a Gender by Name. Make asks for a connection, which is your Genderize account linked to Make once and reused by both modules. Click Create a connection.

  2. 02

    Name the connection

    Giving the connection a name is optional, yet it pays off as soon as you run a test account next to a live one. A label such as "Genderize main" tells you at a glance which account a module talks to.

  3. 03

    Authorize and save

    Depending on what Genderize asks, either approve Make on the Genderize page or paste the key Genderize gives you into the field Make shows. Then click Save. The connection now appears in the module, ready for your first test.

First scenario

Build your first scenario with Genderize

GoalWhen a new contact reaches another app, Make reads a gender for the name with Genderize and passes it on.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the + to add the first module. Genderize has no trigger, so this first module belongs to the app where your contacts arrive.

  2. 02

    Set the starting module

    Pick the module of that other app that returns new contacts, then link its account. Each contact it finds becomes a bundle, one item that flows from one module to the next.

  3. 03

    Add Read a Gender by Name

    Click the + on the right of the first module, search for Genderize and choose Read a Gender by Name. Map the name from the previous module into it, using your saved connection.

  4. 04

    Test with Run once

    Click Run once to execute the scenario a single time. Read the bundles each module received and check what Genderize sent back for your sample name.

  5. 05

    Schedule and switch on

    Set the schedule on the first module; a new scenario runs every 15 minutes by default, which is also the shortest gap on the Free plan. Then switch the scenario on.

Modules

What the Genderize modules do

Genderize gives you 2 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Genderize1

Make an API Call

ActionIn the docs only

Opens the whole Genderize API to your scenario: you write the request yourself and reuse the connection already saved, so no second login is needed.

When to use it
the Read a Gender by Name module does not cover the request you have in mind, and the Genderize API does.
Watch out
the Make documentation for Genderize is limited, so check the endpoint and the answer in the Genderize reference and read the output after Run once.
Genderize2

Read a Gender by Name

ActionIn the docs only

Gives your scenario a gender reading for a name you pass in, so the next module can file, tag or route the contact with that result.

When to use it
a new signup, lead or customer record arrives from another app with a name, and you want the answer stored next to it.
Watch out
Make does not document its fields or output, so run one test on a known name and inspect the bundle before you map anything further.
Need help

Need help automating Genderize with Make?

A person reads every message.

FAQ

Genderize and Make: common questions

01Is the Genderize Make integration free?
Yes, on the Make side. Genderize is a standard app, so it works on the Free plan. That plan allows 2 active scenarios, a minimum gap of 15 minutes between scheduled runs, runs of 5 minutes at most, files up to 5 MB and 512 MB of data transfer. Every module execution counts as one operation, the unit Make counts on your plan. Paid plans lower the gap to 1 minute and lift the active scenario cap. This page gives no price for Genderize itself, so check your own Genderize account for that side.
02What do you need to connect Genderize to Make?
A Genderize account and a Make account are enough to start. The Make documentation lists no prerequisite and no dedicated steps for this app, so the generic flow applies. Add a Genderize module, click Create a connection, name it if you like, then either authorize Make on the Genderize page or paste the key Genderize provides, and click Save. Both Genderize modules then reuse that one connection. If saving fails, confirm in your Genderize account which credential it expects.
03Does the Genderize Make integration react in real time?
No. Genderize has no trigger module, so it never starts a scenario on its own. The scenario starts from another app's trigger, for example the tool where new contacts arrive, or from the schedule set on the first module. A new scenario runs every 15 minutes by default, and 15 minutes is the shortest gap on the Free plan; paid plans go down to 1 minute. Genderize then acts on each bundle that reaches Read a Gender by Name.
04What if a Genderize module is missing in Make?
Use Make an API Call. It calls any endpoint of the Genderize API from your scenario, with the connection you already saved, so you are not limited to Read a Gender by Name. Keep in mind that the Make documentation for Genderize is flagged as limited: it gives no fields, formats or quotas. Test each request with Run once and read the bundle Make returns before you connect the next module, so a surprise shows up in the test rather than in live data.
05Should you use Make or n8n for Genderize?
It depends on what your flow needs from Genderize. On Make, Genderize offers 2 action modules, including Make an API Call for any other endpoint, and it is available from the Free plan. Genderize often has an n8n node too, so check its coverage there before you decide. The comparison page linked in the section above lays out the criteria side by side, so you can weigh them against your own flow.
Same platform

Other docs you might need on this stack.

Browse all integrations