Resources · Make integration

Namsor Onomastics AI Make integrationAutomate Namsor Onomastics AI with Make.

Got a list of names and need to know more about them? The Namsor Onomastics AI Make integration gives you 12 action modules that read a name and return what Namsor infers from it. This page is for ops and marketing people who want to add that step to an automation without writing code.

Try the Namsor Onomastics AI integration on MakeSee the 12 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Namsor Onomastics AI Make integration do for you?

The Namsor Onomastics AI Make integration lets a Make scenario (the automation you build in Make, a chain of steps) send a name to Namsor and get an answer back: a likely gender, an origin, a country of residence, or the name split into parts. Namsor offers no trigger in Make, so the names always come from another app.

Clean up a signup list. A form tool collects a single "Name" field. Add Split full names right after it, and the next steps of your automation can work with a first name and a last name instead of one long string.

Segment an audience by region. A sales team imports leads with a first and last name only. Get country of residence from first/last names adds a likely country you can use to route each lead to the right rep, before anyone opens the file.

Tidy mixed text. When a column holds a mix of people, companies and places, Get the types of proper nouns helps you tell them apart before they land in your CRM.

Know the limits before you build. Make's own documentation for this app is thin: it says there is not enough public information to describe it fully. It lists the modules but no fields, no connection steps and no quotas, so test every module with real names first. There is also no generic API call module for Namsor in Make. If you are still choosing a tool, the n8n vs Make comparison and the Make review give you the wider picture, and the Make training covers the editor from scratch.

Connect

How do you connect Namsor Onomastics AI to Make?

  1. 01

    Add a Namsor module

    In your scenario, click the +, search for Namsor Onomastics AI and pick any of its modules. A connection (your Namsor account linked to Make once, then reused by every Namsor module) is created from this first module.

  2. 02

    Create the connection

    Click Create a connection. You can give it a name, which helps if you later run a test account and a production account side by side. Make then asks you to authorize on Namsor's page or to paste the key Namsor gives you.

  3. 03

    Save and check

    Click Save. The connection now shows up in the module, and every other Namsor module in your scenarios can pick it from the list without asking for credentials again.

First scenario

Build your first scenario with Namsor Onomastics AI

GoalWhen a new contact arrives in another app, Make asks Namsor for a likely gender and origin, then passes both answers along.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the +. The first module has to come from another app, since Namsor has no trigger: your form tool, your CRM or a spreadsheet.

  2. 02

    Add Get gender from full name

    Click the + on the right of the first module, search for Namsor Onomastics AI and choose Get gender from full name. Connect your account, then map the name coming from the first module.

  3. 03

    Add Get origin from full name

    Add a second Namsor module, Get origin from full name, and map the same name again. Each module handles one bundle (one item passing through, here one contact) at a time.

  4. 04

    Test with Run once

    Click Run once. Make runs the scenario a single time; click the bubble above each module to read what it received and returned. This is where you learn what Namsor actually sends back.

  5. 05

    Schedule and switch on

    Open the clock on the first module to set the schedule (every 15 minutes by default for a new scenario), then switch the scenario on. Each module run counts as one operation on your Make plan.

Modules

The 12 Namsor Onomastics AI modules in Make

Namsor Onomastics AI gives you 12 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Namsor Onomastics AI1

Get Indian caste group from first/last names

ActionIn the docs only

Sends a first name and a last name, kept apart, to Namsor and returns the Indian caste group it associates with them. The result is an inference, not a declared fact about the person.

When to use it
research or survey data where names already sit in two columns and the question is specific to India.
Watch out
this is sensitive data, so check what your local rules allow before storing it next to a contact.
Namsor Onomastics AI2

Get Indian caste group from full names

ActionIn the docs only

Same question as the previous module, asked with a single full-name string instead of two separate parts. Handy when your source only ever gave you one field.

When to use it
a form or an export that stores "Name" as one value and you do not want an extra splitting step.
Watch out
Make's docs describe no fields for this app, so run it once on a few known names to see how it reads them.
Namsor Onomastics AI3

Get country of residence from first/last names

ActionIn the docs only

Returns the country where Namsor thinks a person with this first and last name most likely lives. It gives you a region to work with when an address is missing.

When to use it
routing new leads to the right regional sales rep when the CRM already stores first and last names separately.
Watch out
treat the answer as a hint for routing, and let a real address overwrite it later.
Namsor Onomastics AI4

Get country of residence from full names

ActionIn the docs only

Takes one full-name string and comes back with a likely country of residence. It spares you a split step when names arrive in one piece from a form or a chat tool.

When to use it
filling a missing country column in an event signup list before you sort attendees by region.
Watch out
if you already have split names, the first/last version of this module is the more natural fit.
Namsor Onomastics AI5

Get ethnicity from first/last names

ActionIn the docs only

Returns the ethnicity Namsor associates with a given first and last name. Researchers and analysts use this kind of output to describe a population in aggregate when no self-declared data exists.

When to use it
an anonymized dataset with split name columns that feeds a diversity or audience analysis.
Watch out
an inferred ethnicity attached to a named person is sensitive, so aggregate it rather than keep it per contact.
Namsor Onomastics AI6

Get ethnicity from full names

ActionIn the docs only

The full-name counterpart of the module above: one text field in, one inferred ethnicity out. Choose it by the shape of your data, not by the answer you expect.

When to use it
a spreadsheet of authors or speakers where each row has one name cell and you want a statistical overview.
Watch out
each name you send is one operation, so a large sheet uses up your plan's credits quickly.
Namsor Onomastics AI7

Get gender from first/last name

ActionIn the docs only

Guesses whether a first name, read together with the last name, is more likely male or female. That is often enough to pick the right greeting in an automated message.

When to use it
choosing the right greeting in a follow-up email when your CRM holds both name parts but no gender field.
Watch out
add a neutral fallback greeting in your email tool for the names where the guess is weak.
Namsor Onomastics AI8

Get gender from full name

ActionIn the docs only

Reads a whole name as written and returns a likely gender. It is the quickest entry point to Namsor in Make, since almost every tool stores at least a full name.

When to use it
a newsletter list built from a signup form with one "Name" field.
Watch out
names written in reverse order, last name first, may not read the way you expect, so test a handful with Run once before switching the scenario on.
Namsor Onomastics AI9

Get origin from first/last names

ActionIn the docs only

Returns the country or culture a name most likely comes from, which is different from where the person lives today. That makes it useful for language or cultural context rather than for geography.

When to use it
picking the language of a welcome message for contacts stored with separate name fields.
Watch out
do not use it as a stand-in for location; the country of residence modules answer that question.
Namsor Onomastics AI10

Get origin from full name

ActionIn the docs only

Asks Namsor where a full name comes from and passes the answer to the next step of your scenario. Pair it with a gender module when you want two answers from the same contact.

When to use it
enriching a list of webinar registrants that arrives with one name field before it goes into your CRM.
Watch out
nicknames and initials give the model little to work with, so filter them out upstream if you can.
Namsor Onomastics AI11

Get the types of proper nouns

ActionIn the docs only

Tells you what kind of proper noun a value is, for instance a person rather than a company or a place. It is the module to reach for when a column mixes all three.

When to use it
cleaning a contact export where the "Name" column holds both people and business names before you run the gender or origin modules.
Watch out
add a filter after it so only person names reach the next Namsor module and you do not spend operations for nothing.
Namsor Onomastics AI12

Split full names

ActionIn the docs only

Cuts a full name into its first-name and last-name parts. That gives you clean columns for personalization and opens the door to the first/last versions of the other modules.

When to use it
a lead form that only asks for "Your name" while your CRM expects two separate fields.
Watch out
compound surnames are exactly the case to check with Run once, since the docs say nothing about how the split is done.
Need help

Need help automating Namsor Onomastics AI with Make?

A person reads every message.

FAQ

Questions about Namsor Onomastics AI in Make

01Is the Namsor Onomastics AI Make integration free?
Yes, on the Make side: Namsor Onomastics AI is a standard app, available from the Free plan. That plan allows 2 active scenarios, a scheduled run every 15 minutes at the shortest, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) go down to a 1 minute interval and allow 40 minutes of execution. Every module run counts as one operation, so enriching a long name list uses credits fast. Whatever Namsor charges for its own service is a separate question to check on Namsor's side.
02What do you need to connect Namsor Onomastics AI to Make?
A Namsor account and a Make account. Make's documentation for this app lists no prerequisites and no official connection steps, so the generic flow applies: add a Namsor module, click Create a connection, optionally name it, then either authorize Make on Namsor's page or paste the key Namsor gives you, and click Save. Once saved, the connection is reused by all 12 Namsor modules in every scenario you build. If the screen asks for something the docs do not mention, keep your Namsor account open in another tab to find it.
03Does Namsor Onomastics AI trigger a Make scenario in real time?
No, Namsor has no trigger in Make, so it never starts a scenario on its own. The first module always comes from another app: a form tool, a CRM, a spreadsheet. If that app offers an instant trigger, the scenario starts as soon as the app calls Make through a webhook. If it offers a scheduled trigger, Make checks it on the scenario's schedule, every 15 minutes by default. Namsor then runs as an action step in the middle of the flow, once per contact that comes through.
04What if the Namsor module you need is missing in Make?
It depends on what is missing. Make offers no generic API call module for Namsor, so you cannot reach an endpoint that the 12 modules do not cover. Make's own documentation also says it cannot describe this app fully for lack of public information, which is why testing with Run once matters more here than usual. If a module does not answer your question, check whether another app in Make covers the need, or ask a Make agency to look at your case.
05Should you use Make or n8n for Namsor Onomastics AI?
It depends on your criteria, not on a winner. Make gives you the 12 Namsor modules listed on this page, a visual editor and a Free plan to test them. Many apps also have an n8n node, so check whether one exists for Namsor and which name questions it covers before you compare. Pick the tool your team already uses for the rest of the flow, since the names come from another app anyway. Keeping the source app and Namsor in the same tool is simpler to maintain.
Same platform

Other docs you might need on this stack.

Browse all integrations