How to Connect and Configure Data for Your AppSheet App

Most people think building a no-code app is the hard part.

It isn’t.

The hard part is getting your data right — connected cleanly, typed correctly, and linked intelligently across tables. Get that wrong, and your app breaks in the field. Get it right, and your team has a tool they’ll actually use every day.

This guide walks you through exactly how to connect and configure data for your AppSheet app — from picking your first data source all the way to creating table relationships that make your app genuinely powerful.

Why Data Configuration Is the Foundation of Every AppSheet App

Here’s a number worth knowing: by 2024, 65% of all application development activity is being performed using no-code or low-code platforms. AppSheet is at the center of that shift.

But no-code doesn’t mean no-structure. AppSheet is, at its core, a data-first platform. Data is the backbone of any AppSheet app — without data, an app is just an empty shell. Every screen, form, and automation you build depends on how well you’ve structured and configured your underlying data.

The good news? businesses can save up to 70% on development costs using no-code platforms compared to traditional coding, and apps built on platforms like AppSheet can be developed in one-third of the time of traditional development.

That speed advantage only materializes when your data is set up correctly from the start. So let’s do it right.

What Data Sources Can You Connect to AppSheet?

AppSheet supports a wide range of data backends. All you need to do is connect AppSheet to your favorite cloud data storage provider — such as Google Drive, Office 365, Dropbox, and Salesforce.

More specifically, the backend data sources for AppSheet include: spreadsheets like Google Sheets, Excel, and CSV files — perfect for simple data structures and quick prototypes; databases like MySQL, PostgreSQL, and Microsoft SQL Server for complex data needs; cloud services like Google Drive, Dropbox, and Google Cloud Storage for secure data access; and APIs to connect to external services and extend functionality.

The full range of data source types includes native AppSheet sources, spreadsheets, databases, other data or provider services, and connections using Integration Connectors.

For most people getting started, Google Sheets is the fastest path. For teams needing enterprise-grade scale, Integration Connectors via Google Cloud unlock connections to systems like Salesforce, SAP, and Oracle.

How to Connect Your First Data Source to AppSheet

Starting from Google Sheets (Recommended for Beginners)

The quickest way to get started: navigate to Tools → AppSheet → Create an App directly from within Google Sheets, and AppSheet will begin connecting your data to your new app immediately.

Alternatively, you can:

1. Go to appsheet.com and sign in with your Google account
2. Click + New App and select Start with your own data
3. Choose Google Sheets as your data source
4. Select your file from the file picker and click Select
5. AppSheet generates an app prototype instantly

Once your app is ready, go to Data, navigate to the Tables column, select the connected data source and pick the table or sheet to use, then configure the table settings including name, display name, and data access. Click Save when done.

Starting from a Database

For SQL databases (MySQL, PostgreSQL, SQL Server), add the data source from your account settings. Open the Sources tab in the account page, click the add data source button, name your new data source, and select your database type.

How to Add a Second Data Source to an Existing App

This is where AppSheet becomes genuinely powerful. Real-world apps rarely run on a single table. The goal of connecting and configuring data from multiple data sources is to enhance a basic application with additional functionality.

Here’s how to add a second data source:

In the AppSheet UI, use the left navigation bar and go to Data. To add a second data source, click Add new Data (+) next to Data. In the Add data form, select Google Sheets (or your preferred source type).

In the Create a new table form, review the default settings — this dialog lets you select a specific worksheet from the spreadsheet or a different data source type, and lets you allow or disallow modifications to the data by users of the app. Leave defaults or adjust as needed, then click Add 1 table.

Important: AppSheet editor only recognizes one table per worksheet. If you have multiple tables in the same worksheet, you’ll need to move them to separate tabs in the workbook or Google Sheet.

The same app can draw from multiple, entirely different data sources — a Google Sheet for one table and a SQL database for another, for example.

How to Configure Data Types in AppSheet

Once your tables are connected, AppSheet reads your column data and attempts to auto-detect types. It’s good at this — but not perfect. Knowing how to set types correctly gives your app capabilities that a generic “Text” column simply can’t unlock.

How AppSheet Reads Your Columns

AppSheet determines the name of your column based on the top cell in the spreadsheet of each column, and deduces the type of data based on the data in the column.

For example, if you have a column named “Birthday” and all your data points use the format 03-20-2000, AppSheet will assume the column is of type Date. The editor often correctly identifies the data type, but when it doesn’t, you can change it using the Type drop-down.

Key Data Types and When to Use Them

Choosing data types in AppSheet goes beyond traditional programming — it’s about unlocking AppSheet’s true potential, since each type enables specific functionalities.

Here are the most important ones:

Text types — Use Name or Email instead of plain Text for those fields. Opting for “Name” or “Email” over “Text” activates built-in validation and formatting, improving data accuracy and user interaction.

Address — Include the word “Address” in the column name to help AppSheet identify it. Enter the complete address including street, city, state, country, and postal code values. You can also store address information in adjacent columns named Street, City, State, Country, and Zip — AppSheet automatically recognizes adjacent columns as a single address and creates a Computed Address column.

Enum — For fields where options are fixed and known, like “Status” or “Category,” use the Enum data type. It simplifies data input, reduces errors, and enhances the app interface by providing clear, easy-to-select options.

Ref (Reference) — This is the column type that creates relationships between tables. The Ref data type creates a link to another table — it’s ideal for fields that require a connection to another table, such as foreign keys or table relationships.

Change Timestamp / Change Counter — In some apps, it’s important to record a timestamp or increment a counter automatically in a row when changes are made through the app. ChangeCounter shows how many times an entry has been edited.

Setting a Key Column

Every table needs a unique identifier. The key may be a single column (such as Employee ID) or two or more columns (such as FirstName and LastName). Each row in the table must have a key value that uniquely identifies it — this is critical, because it allows AppSheet to reliably find the right table row when syncing changes from a user’s device to the server.

If no obvious key exists, AppSheet will auto-generate one. You can also choose your own key column by selecting it in the column editor.

How to Create Relationships Between Tables

Here’s where most people underutilize AppSheet. Connected tables that can reference each other make your app feel like a real database — not just a digital spreadsheet.

Why Table Relationships Matter

AppSheet references allow your apps to support relational data. Once you have an app with multiple tables, it’s often useful to create connections — known as references — between those tables.

For example, an order capture app might contain Orders, Order Details, Products, and Customers tables — where each Orders row references the customer who placed it, each Order Details row references its parent order, and each Order Details row references its corresponding product.

How to Add a Ref Column

AppSheet lets you define references between rows in related tables using a special column type called Ref.

To create a relationship:

1. In your spreadsheet, add a new column header in the table you want to link from (e.g., Company ID in a Contacts sheet)
2. Switch to the AppSheet editor and navigate to Data → your table
3. Click the three-dot menu → Regenerate Schema → Regenerate to confirm
4. AppSheet adds the new column to the table structure
5. In the column editor, set the column type to Ref and select the target table from the dropdown

AppSheet will also automatically infer references when you generate or regenerate a table. For example, if you have a Customers table with a Name column as its key, and the Orders table has a column called “Customer Name,” AppSheet assumes that column is a Ref to the Customers table.

Automatic Related Record Lists

One of the most useful features that comes automatically with Ref columns: AppSheet will automatically create a list of related rows. If you want a record in your Books table to have a list of reviews, you reference the book from each Review record — then when you look at a book in your app, you’ll see a list of related reviews automatically.

Tips for Clean Relationships

• It’s important that each row can be uniquely identified. Names and addresses aren’t always the best choice for keys since multiple people can share a name and addresses can change — that’s why giving every table a dedicated ID column is recommended.
• An EnumList of Ref lets you reference multiple items from a table, enabling one-to-many relationships.
• When you add a reference to a table, read permissions are automatically added to the referenced table to allow access.

How to Verify Your Data Configuration

Once tables and relationships are set, verification is the final step before your app goes live.

Check the live preview — The left-side preview panel in the AppSheet editor reflects your real data in real time. Click through records to confirm references are pulling correct related data.

Verify data writes back to the source — Verify that newly added and modified data is present in the underlying Google Sheet or database by editing a record in the app and confirming the change appears in your source file.

Regenerate schema after source changes — If you ever add, remove, or rename columns in your spreadsheet, go back to AppSheet and regenerate the schema. AppSheet recommends that you change the structure in the data source first, then regenerate the table in the editor — but if that isn’t possible, you can change the data schema directly in the AppSheet app editor.

Watch for sync errors — If column names in your expressions no longer match after a rename, AppSheet will prompt you to update all places in the app where the old column name was used. Always say yes.

Preparing Your Data for Better AppSheet Results

A few quick habits that save hours of debugging later:

Make sure your column headers are bold so AppSheet recognizes them as headers, and ensure that each column has a clear, specific name rather than generic labels like Column1 or Column2. Also make sure the data type format is consistent through each cell in the column.

A record is stored as a single row in your spreadsheet — it is an individual piece of data in your app, and might describe an individual customer, specific job site, or single product. Each table should represent one type of entity.

Keep related data in separate sheets rather than cramming everything into one giant spreadsheet. The one-table-per-worksheet rule means clean sheets make cleaner apps.

The Bigger Picture: What You Can Build Once Your Data Is Right

The global low-code development platform market reached $28.75 billion in 2024 and is projected to reach $264.40 billion by 2032, growing at a 32.2% CAGR.

By 2025, 70% of new business applications are expected to be developed using low-code or no-code technologies.

90% of no-code users believe their company has experienced accelerated growth from using no-code tools.

Apps developed with no-code tools achieve 30% higher user retention rates compared to traditional apps, with 75% of no-code apps meeting or exceeding performance expectations.

In April 2024, Google AppSheet expanded its template marketplace and introduced AI-driven app suggestions to streamline solution building for SMEs and enterprise clients.

The platform is moving fast. Teams that get their data foundations right today will compound that advantage as AppSheet adds more automation, AI, and integration capabilities over time.

Conclusion

Connecting and configuring data in AppSheet isn’t a technical hurdle — it’s a one-time investment that determines everything your app can do.

Start with a clean data source. Connect it through the AppSheet editor. Configure your column types deliberately. Build Ref relationships between tables. Verify that data flows correctly in both directions.

Do those five things, and you’ve laid the foundation for an app your team will rely on — not one they’ll abandon after a week.

The no-code wave is here. By the end of 2025, over 50% of new low-code platform customers will be business buyers outside IT. That means the tools are built for you now — not just for developers.

Your data is already sitting in a spreadsheet or database somewhere. AppSheet is ready to turn it into something your team can actually use in the field. The configuration steps above are your blueprint.

Start building.