Creating new options for multi-select dropdown in Airtable database

Other Questions Airtable
1

I’m trying to figure out how to create new choices for a multi-select dropdown field when working with Airtable. Every time I try to insert a record that contains a new option that doesn’t already exist in the dropdown, I keep getting an error message.

The error looks something like this:

{
  error: 'INVALID_MULTIPLE_CHOICE_OPTIONS',
  message: 'Unknown choice values: Premium',
  statusCode: 422
}

Here’s the code I’m using to create the record:

airTable('Companies').create({
    CompanyName: 'Sample Corp',
    Category: ['Premium']
  }

Is there a simple method to automatically add new dropdown options when they don’t exist yet?

2

yeah, airtable’s api can be a hassle. gotta add those dropdown options first through the ui, no shortcuts! i usually add all the options i think i’ll need upfront.

3

Nope, Airtable’s API can’t create new multi-select options on the fly. You’ve got to manually add them in the field settings first before you can use them in records. I hit this exact problem building an integration that pulled categories from external sources. My solution? I built a validation step that checks existing field options against new data, then flags me to add missing options through the web UI. It’s annoying but unavoidable - go into your base settings, edit the field, and add ‘Premium’ as an option. Then your API call will work fine. Pro tip: batch these updates. Collect all the unique values you need first, then do one manual update session to add multiple options at once.

4

There’s no direct API way to auto-create dropdown options. You’ve got to update the schema separately before using new values. Here’s what works for me: I built a preprocessing step that handles this smoothly. First, I grab all existing dropdown values, compare them to what I’m inserting, then batch up the missing options that need manual addition. Instead of silent failures or crashes, I log everything to a tracking table with timestamps. The trick is seeing this as data governance, not just a tech limitation. Most “new” categories are actually variations of existing ones or need approval anyway. Adding a review process actually cleaned up our data quality big time. For now though, just add Premium manually through field configuration and your code will work fine.

5

Had this exact issue last year building a client onboarding system. The API limitation is frustrating as hell.

I ended up with a two-step workaround. First, I query the field metadata to grab current dropdown options:

const fieldInfo = await base('Companies').fields();
const categoryField = fieldInfo.find(f => f.name === 'Category');
const existingOptions = categoryField.options.choices.map(c => c.name);

Then I check if my new value exists. If it doesn’t, I log it to a “pending options” table that I review weekly and bulk add through the UI.

Not elegant, but it stops the crashes and lets me control data quality. Half those “new” categories are just typos or duplicates anyway.

For high-volume stuff, you could maintain a master list of approved categories in a config file and validate against that before hitting Airtable.

6

Ugh, this limitation drives me crazy! Been dealing with it for months. My workaround: create a separate “new options” field as single line text. Then I check it periodically and move the approved ones to the actual dropdown. Not pretty, but it works and keeps everything flowing without crashes.

7

The Airtable API won’t let you create dropdown options on the fly. You’ve got to update the field schema first, then add your records.

I’ve hit this exact problem building data pipelines with dynamic dropdown values. It’s perfect for automation.

You need a system that:

  1. Checks if your dropdown option exists
  2. Creates it if it doesn’t
  3. Adds your record

Sure, you could code this yourself, but it gets messy quick. Error handling, rate limits, schema updates, proper sequencing - it’s a pain.

Latenode handles this scenario really well. Set up a workflow that automatically manages your Airtable schema and keeps dropdown options synced. The built-in Airtable connectors handle field updates and record creation in the right order.

The workflow detects new values, updates your field schema, then creates the record. All automated, zero manual work.

Check it out at https://latenode.com

8

Hit this exact problem with a CRM sync. Airtable’s manual field schema updates break any real automation.

Here’s the fix - skip the workarounds and manual reviews. Just automate the whole thing.

I use automation that watches incoming data, catches new dropdown values, updates the Airtable schema via API, then creates the record. No manual work.

The trick is automating the field updates instead of fighting Airtable’s limits.

Latenode handles this perfectly. Set up a workflow that watches for new values, updates dropdowns, and creates records in order. Kills the error handling and batch processing mess.

Check it: https://latenode.com