npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

n8n-nodes-namegender

v0.7.0

Published

n8n node for NameGender: gender from a name, email or username with the evidence behind each answer, ready salutations in ten languages, a check of whether a name looks real, and the age range of a first name.

Readme

n8n-nodes-namegender

An n8n community node for NameGender. It returns the gender associated with a name, email address or username, together with the evidence behind the answer: probability, sample size, confidence and source. It also returns the first, middle and last name parsed from the input.

Installation · Credentials · Operations · Output · Resources

Installation

In n8n, open Settings → Community Nodes → Install and enter n8n-nodes-namegender. See the n8n community nodes guide for self-hosted setups.

Credentials

  1. Create a free account at namegender.com. No card is needed, and every account gets 100 free credits a day.
  2. In the dashboard, open API keys and create a key. It starts with ng_live_.
  3. In n8n, add a NameGender API credential and paste the key. Testing the credential calls /me, which is not charged.

If the names are personal data you do not want kept in your request history, turn on Don't store the names this key sends for the key.

Operations

The node has four resources: Gender (the four lookups below), Salutation, Name Check and Age. Workflows built before 0.4.0 keep working: Gender is the default resource.

| Operation | Endpoint | Input | |---|---|---| | Gender From Name | POST /api/v1/gender | A first name or a full name | | Gender From Email | POST /api/v1/gender/email | An email address | | Gender From Username | POST /api/v1/gender/username | A username or handle | | Countries For Name | POST /api/v1/gender/countries | A first name | | Name Check | POST /api/v1/name-check | A name as typed into a form | | Salutation | POST /api/v1/salutation | A full name, titles included | | Salutation From Email | POST /api/v1/salutation | An email address, when you have no name | | Age | POST /api/v1/age | A first name or a full name |

The three gender operations accept an optional Country Code (two or three letters, or the country name), which matters for names that change gender across borders, and Best Guess, which returns the most likely gender even below the confidence threshold.

When a form submission has no country, map what it does have: Locale (the browser language, such as it-IT) or IP Address. The API uses Country Code first, then the locale's region, then the IP, and the output's country_source says which one it used (country, locale, ip or null). The IP is not stored. All operations, Name Check and Salutation included, take the same three fields.

Salutation turns a name into a ready letter or email salutation in ten languages: Dr. Anna Müller in German gives Sehr geehrte Frau Dr. Müller,, Ahmet Yılmaz in Turkish Sayın Ahmet Bey,. The output has salutation.formal, salutation.informal and salutation.neutral. The gendered form is used only when the gender is known with at least the Minimum Probability (default 90) and the language has the name part it needs; otherwise form is neutral and reason says why. Set Language, a Country Code for the lookup, or Known Gender when your data already has it.

Name Check says whether a name typed into a form looks like a real person's name, with the reasons: asdf qwerty comes back implausible with keyboard_pattern, Jennifer Null comes back plausible. The output has assessment (plausible, suspicious or implausible), a score from 0 to 100 and the signals behind it. It never calls a name fake: use it to flag a record or route it for review, not to reject people automatically. Surnames are judged by their shape only.

Age returns how old the living people with a first name are: Brittany gives a median age of 36, with age_range 32–38 for the middle half and age_range_80 for the middle 80%. It describes a group, not the person. It covers the United States, France and Norway; without a country the US data is used, and any other country returns no age, reason: country_not_covered, and costs nothing. Gender narrows it to one gender's records, which matters for names such as Leslie.

Each incoming item costs one credit, including items that come back unknown.

Output

{
  "query": "Ayşe Yılmaz",
  "name": "Ayşe",
  "first_name": "Ayşe",
  "middle_name": null,
  "last_name": "Yılmaz",
  "name_type": "personal",
  "gender": "female",
  "probability": 99,
  "sample_size": 655,
  "confidence": "high",
  "source": "db",
  "matched_as": null,
  "country": null,
  "credits_remaining": 4821
}

gender: null is a successful answer that means the data has no confident gender for that name. Route it with an IF node instead of treating it as an error. Read probability together with sample_size before trusting a result.

A name tells you how often people with that name were recorded as male or female. It does not tell you how a person identifies. Do not use it for decisions about employment, credit, insurance, health or eligibility.

Resources

License

MIT