Nationalize in n8n
n8n is a workflow-automation platform — self-hosted or n8n Cloud — that connects apps and services into automated pipelines. The Nationalize node is a verified community node maintained by Demografix.
- Listing: n8n.io/integrations/nationalize
- Source: github.com/DemografixNationalize/n8n-nodes-nationalize
- Action: Get Nationality — input a name, output an array of up to five country candidates with probabilities and a count.
Add the node
Nationalize ships as a verified community node, so it appears in the standard node picker on n8n Cloud and recent self-hosted versions — no install step.
In the workflow editor, click +, search for Nationalize, and drop the node onto the canvas.
Add your API key
Open the node, click Credentials → Create New Credential, paste your API key from your dashboard, and save.
Credentials are stored encrypted in your n8n instance and reused across workflows.
Example workflow: enrich incoming form submissions
A common pattern: a form submission arrives, you extract the last name, predict nationality, and write the result to a database or downstream tool.
- Trigger node — webhook, Typeform, Airtable Watch, or whatever produces the name.
-
Nationalize node
— set Name
to
{{ $json.last_name }}(or the field that holds the name). - Downstream node — write the result anywhere. Examples: append a row to a Google Sheet, update an Airtable record, post to Slack, store in Postgres.
Screenshot · n8n-workflow-form-to-sheets-nationalize
The Nationalize node returns a JSON object the next step can read with <.property>{{ $json.country[0].country_id }}, <.property>{{ $json.country[0].probability }}, and <.property>{{ $json.count }}.
Example workflow: branch on top-candidate confidence
Nationalize returns up to five country candidates ordered by descending probability. The top candidate's probability is a useful confidence signal.
- Trigger node.
- Nationalize node — predicts nationality.
-
IF node
— condition
{{ $json.country[0].probability }}≥0.5. - True branch — write the top candidate to your primary destination.
- False branch — send the row to a review queue, or write the full candidate array for human inspection.
This keeps low-confidence rows visible rather than silently picking a top guess.
Quota and rate limits
Each node execution consumes one name from your monthly Nationalize quota. Batched workflows that process many names through the node deduct one per name. The node respects the same
X-Rate-Limit-*
headers as the API; n8n's retry-on-fail behavior handles transient throttling automatically.
See pricing for tier limits.
Troubleshooting
| Symptom | Cause | Fix |
|---|---|---|
| 401 Invalid API key | The credential holds an outdated key. | Open the credential, paste a fresh key from your dashboard, save. |
| 429 Request limit reached | Monthly quota exhausted. | Upgrade or wait for the window to reset. |
| Node returns country: null | The name has no prediction in the underlying dataset. | Expected for very rare names. Treat null as "unknown" downstream. |