> ## Knowledge Base Index
> Fetch the complete knowledge base index at: https://help.syncbase.app/sitemap.xml
> Use this file to discover available pages before exploring further.
> Pure-Markdown content can be obtained by appending a '.md' suffix to the content URLs listed in the sitemap (without the trailing slash).

# ✚ How to create a new metaobject entry from Airtable with SyncBase?

You can create new Shopify Metaobject entries directly from Airtable using SyncBase.

This allows you to manage structured content (Suppliers, FAQs, Ingredients, etc.) without going back to Shopify.
There are two ways to create a new entry, depending on whether your Metaobject definition contains required fields and how you prefer to work.


${youtube}[](pAcljPjgx_E)

# Before you start

__Make sure that__:

* SyncBase is installed on your Shopify store.
* You have generated an Airtable synced base that includes your Metaobjects.
* You are working inside the correct synced `Metaobject` table (for example: `MO – Suppliers`).

Each table corresponds to one Metaobject definition in Shopify.


# Method 1: Create a blank record

| This method is ideal if you want to manually create a single entry and your Metaobject definition has no required fields.

### How it works

1. Go to the synced `Metaobject` table (example: `MO – Suppliers`).
2. Add a new record (create a new row).
3. Wait a few seconds.

__SyncBase will__:

* Create the entry in Shopify.
* Automatically populate the **Entry ID** field in Airtable.

Once the **Entry ID** appears, your Metaobject entry has been successfully created in Shopify. 
You can now safely edit the other fields.

### Important

* **Do not edit fields before the Entry ID is populated.**
* This method does **not work** if your Metaobject definition contains required fields. If required fields exist, Shopify will reject the blank creation and a sync error will appear in your Status page. 
* If that happens, simply delete the failed record and use Method 2 instead.

![](https://storage.crisp.chat/users/helpdesk/website/-/3/5/e/8/35e84c43b53ca800/syncbase-help-center-video_1joilkx.gif =809xauto)

# Method 2: Create a record with data (recommended)

| This method works in all cases — including when required fields are defined. It is also perfect for creating multiple entries at once.

### How it works

1. Go to the synced `Metaobject` table.
2. Create a new record **and fill in the necessary fields immediately**. (You can do this via an Airtable Form, an Automation or Script)
3. Leave the **Entry ID** field empty.

__SyncBase will__:

* Send the data to Shopify.
* Create the Metaobject entry.
* Return the **Entry ID** (and Handle, if not set).
* Update the record automatically.

Because the required values are sent at creation time, Shopify accepts the entry without errors.

# Special: Creating records with required fields and relations to other objects

For advanced Shopify setups, metaobject entries can reference other objects — such as products or other metaobject entries — to create highly custom configurations.
These entries can be created in Shopify and managed from Airtable.

To create metaobject entries with relations directly from Airtable, a highly individual, custom Airtable setup is required. The references are connected via Shopify GID values, and this logic must be properly reflected in your Airtable record creation process (see [Metafield reference values](https://help.syncbase.app/en/article/metafields-synchronization-how-does-it-work-i26yl8/#1-metafields-with-reference-types) for more info on GID values).

Our experienced in-house Airtable experts can assist you or build it for you in a paid Studio mission. Please reach out in the live chat for a custom proposal.


# Metaobject status and behavior

### Default status

* Entries created from SyncBase are set to **DRAFT** by default.
* You can change the status to **ACTIVE** directly from Airtable.

### Required fields

__If a field is marked as required in your Shopify Metaobject definition__:

* It must be filled in Airtable.
* It cannot be left empty.
* Otherwise, the sync will fail.

# Best practices

* Use **Method 1** only for quick manual creation and when no required fields exist.
* Use **Method 2** for scalable workflows (Forms, bulk creation, automations).
* Always wait for the **Entry ID** before modifying a newly created blank record.
* Monitor the **Status page** if something does not sync as expected.

# Need help with advanced automation?

If you’d like to build a custom workflow (bulk creation, approval pipeline, automation setup…), our team can help.
Simply reach out via the in-app live chat and explain your use case — we’ll guide you or prepare a custom setup proposal.