Overview
The "Gender API" node integrates with an external Gender API service to predict or determine the gender of a person based on input data such as first name, full name, or email address. This node is useful in scenarios where you want to enrich datasets with gender information for marketing segmentation, personalization, demographic analysis, or user profiling.
For example:
- You have a list of customer first names and want to append likely gender information.
- You want to analyze full names from a contact list to infer gender distribution.
- You want to guess gender based on email addresses for targeted campaigns.
The node supports querying by different criteria (first name, full name, or email) and allows additional optional parameters like country code, locale, IP address, and internal request ID to improve accuracy or track requests.
Properties
| Name | Meaning |
|---|---|
| Query by... | Criterion to query gender by. Options: First Name, Full Name, E-Mail Address. |
| First Names | Collection of one or more first names to query. Each entry includes: - First Name: The person's first name. - Additional Fields: - Country Code: ISO 3166 ALPHA-2 country code to specify nationality context. - Locale: Browser locale to influence results. - IP Address: Optional IPv4 or IPv6 address. - Internal ID: Unique identifier for the request. |
| Full Names | Collection of one or more full names to query. Each entry includes: - Full Name: The person's full name. - Additional Fields: Same as for First Names. |
| E-Mails | Collection of one or more email addresses to query. Each entry includes: - E-Mail: The person's email address. - Additional Fields: Same as for First Names. |
These properties allow flexible input of multiple entries per execution, each optionally enriched with geographic or locale data to improve prediction accuracy.
Output
The node outputs a JSON array where each element corresponds to a gender prediction result for an input entry. Each result typically contains fields such as:
- The queried name or email.
- Predicted gender.
- Probability or confidence score.
- Possibly other metadata returned by the Gender API.
No binary data output is indicated.
Dependencies
- Requires access to the external Gender API service.
- Requires configuration of an API authentication credential (an API key or token) within n8n credentials.
- Network connectivity to the Gender API endpoint.
Troubleshooting
Common issues:
- Invalid or missing API credentials will cause authentication errors.
- Incorrectly formatted input data (e.g., empty names or invalid emails) may lead to no results or errors.
- Exceeding API rate limits can cause request failures.
- Providing unsupported country codes or locales might reduce accuracy or cause warnings.
Error messages:
- Authentication errors: Check that the API key credential is correctly configured and valid.
- Validation errors: Ensure all required fields (like first name, full name, or email) are provided and properly formatted.
- Network errors: Verify internet connectivity and that the Gender API service is reachable.
- Rate limit exceeded: Implement retry logic or reduce request frequency.