Airtable data enrichment guide

Determine Gender in Airtable with the GenderAPI Extension

Analyze names and email addresses from one source field, then write gender and optional supporting values into mapped Airtable fields.

Extension-based enrichment

Map your Airtable fields once

Select the table, source field and output fields in the extension panel, then test a representative set of records before a larger run.

  • Name and email detection
  • Optional country and probability
  • Preserve existing values
Install the Airtable extension
GenderAPI extension interface for Airtable
GenderAPI extension for Airtable.

Official extension

Install GenderAPI from Airtable Marketplace

Add the extension to the relevant Airtable base, authorize it and open the configuration panel from Extensions.

Install the Airtable extension
Names or emailsMapped outputsBulk records

Configuration

Configure the extension in six steps

  1. 01

    Install and run the extension

    Open Airtable Extensions, add GenderAPI.io and choose Run to open the configuration panel.

  2. 02

    Choose the credits key

    Select the GenderAPI key whose credits will be used for the operation.

  3. 03

    Select the table and source field

    Choose the table and the field containing names, email addresses or a mixture of both.

  4. 04

    Map the gender destination

    Select the Airtable field where the returned gender signal should be written.

  5. 05

    Map optional result fields

    Optionally select country and probability fields so supporting values remain available for review.

  6. 06

    Protect existing values and run

    Enable the skip option when the gender field already contains a value, test a small sample and then process the intended records.

Video walkthrough

See the Airtable workflow before configuring it

The original guide includes a walkthrough covering installation, source selection and result mapping. Open it in a new tab while following the steps above.

Video tutorial for the GenderAPI Airtable extensionWatch the Airtable extension tutorial

Data quality

Keep supporting values available for review

Map probability and country fields when useful, preserve existing values and review ambiguous records instead of treating a prediction as verified identity.

Data flow

Map only the Airtable fields the workflow requires

The extension does not upload your Airtable base as a file. It sends the mapped value from each selected record to GenderAPI as an individual name or email query and writes the configured response fields back to Airtable.

Frequently asked questions

Airtable extension FAQ

Can one Airtable field contain both names and emails?

Yes. The extension can inspect a mixed source field and determine whether each supported value should be treated as a name or email address.

Which fields can receive results?

Map a required gender field and optional country and probability fields in the extension panel.

Can existing gender values be preserved?

Yes. Enable the option to skip records whose mapped gender field already contains a value.

Should I test before processing the full table?

Yes. Run the extension on a small representative sample first and review the mapped values before processing a larger dataset.

Does GenderAPI store the Airtable base or query inputs?

The extension does not upload the Airtable base as a file. It sends mapped record values as individual queries. GenderAPI does not store email-query inputs; unresolved name or username queries may be retained to improve coverage.

Published October 17, 2024Last reviewed September 12, 2026

Enrich an Airtable base

Install the extension and test a small sample

Map the source and result fields, preserve existing values and inspect supporting signals before a larger run.

Get the Airtable extension