Agify in n8n

Add the node

Agify 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 Agify, 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 first name, predict age, and write the result to a database or downstream tool.

1. Trigger node — webhook, Typeform, Airtable Watch, or whatever produces the name.
2. Agify node — set Name to {{ $json.first_name }} (or the field that holds the name). Optionally set Country to a two-letter ISO 3166-1 alpha-2 code.
3. Downstream node — write the result anywhere. Examples: append a row to a Google Sheet, update an Airtable record, post to Slack, store in Postgres.

The Agify node returns a JSON object the next step can read with <.property>{{ $json.age }} and <.property>{{ $json.count }}.

Example workflow: filter by data quality

Agify returns a count — the number of data points behind the prediction. Low counts mean the prediction is based on a small sample. Use that as a quality gate.

1. Trigger node.
2. Agify node — predicts age.
3. IF node — condition {{ $json.count }} ≥ 1000 .
4. True branch — write the prediction to your primary destination.
5. False branch — send the row to a review queue (a Slack channel, an Airtable view, a separate Google Sheet).

This pattern keeps thinly-supported predictions out of your main dataset.

Quota and rate limits

Each node execution consumes one name from your monthly Agify 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