Productivity

Notion and Google Sheets: Embed, Import, or Sync (2026)

Notion has no built-in Sheets sync. Pick by how closely the two must agree, and know where each method breaks

M
Murali
Nov 19, 202617 min read
TL;DR

Notion has no built-in sync with Google Sheets. In Notion's help center the only Sheets-specific feature is the Google Drive embed, which shows a sheet on a page and does not turn it into Notion data. So pick by how closely the two need to agree: embed for a view only, CSV import for a one-time move, a Zapier or Make automation for new and changed rows flowing one way, or a two-way add-on when edits must travel both directions. Each method breaks in a specific, predictable place, and this guide lists them.

Check your own data before trusting any method

Everything below is documented behavior and common failure patterns, not a promise about your sheet. Before you rely on a method, test it on five rows: add one, edit one, delete one, reorder two, and see what arrives in Notion. That ten-minute test is worth more than any feature list.

A reader asked me last month why her Notion project table kept showing last week's numbers. The numbers lived in a Google Sheet that her finance contact updated every morning. She had pasted the sheet link into Notion, saw a live-looking grid, and assumed the two were connected. They were not, at least not in the way she needed. The grid was a window, and the Notion database next to it, the one her filters and rollups ran on, had never seen a single number from the sheet.

That gap is the whole subject of this guide. "Notion and Google Sheets" sounds like one task, but it is at least four different jobs: look at a sheet from inside Notion, move a sheet into Notion once, keep new rows arriving, or keep both sides identical. Each job has a method, each method has a failure mode, and most of the bad advice online comes from using a method built for one job to do another.

I build Mursa, a task app, so I spend a lot of time watching people keep tasks in spreadsheets and databases they outgrew. I will mention Mursa once, near the end, where it genuinely fits. Everything before that is about Notion and Sheets only.

Does Notion Connect to Google Sheets Natively?

Not as a sync. Notion's help center documents a Google Drive embed that accepts a Google Sheet, either by pasting its URL or by choosing Browse Google Drive. It also documents a CSV import, and neither feature keeps a sheet and a Notion database in step. I could not find a native two-way or one-way Sheets sync in Notion's documentation as of November 2026, and the vendors that sell sync tools say the same thing about their own category.

That matters because the search results for this topic are mostly written by those vendors. Their guides are accurate about their own product, but each one starts from the assumption that you need a sync tool. Often you do not. The cheapest method that meets your real requirement is almost always the right one, so start from the requirement.

Which Method Matches What You Actually Need?

Answer one question first: if someone edits a cell in the sheet, what must happen in Notion, and how fast? The answer sorts you into one of four methods.

01

Embed: you only need to see the sheet inside a Notion page

Setup is a minute. Nothing is copied, so nothing can drift, but Notion cannot filter, sort, relate, or roll up the data because it is not Notion data. It breaks on permissions and on mobile.

02

CSV import: you need the data in Notion once

Best for a finished list: a contact export, a reading list, an archive. It breaks the moment the sheet changes, because Notion's import adds rows and does not update existing ones.

03

Automation (Zapier or Make): new or changed sheet rows should create or update Notion items

Best for a form-style intake sheet. It breaks on edits you did not plan for, on deletions, and on rows that get re-sorted.

04

Two-way add-on: people edit on both sides and both must match

The only method that attempts true agreement. It breaks by overwriting, by looping, and by asking for broad access to your Google account.

If you cannot decide between 03 and 04, you probably need 03 with a rule that one side is the source of truth. I come back to that rule in the section on two-way sync, because it is the most useful single idea in this guide.

How Do You Embed a Google Sheet in Notion?

In Notion's help center, the steps are short. On a page, add an embed block and paste the Google Sheet's URL, or use Browse Google Drive and pick the file. Notion says you can connect more than one Google account if your files sit in different Drives. The same page states a general rule for all embeds: if the source changes, the change appears in Notion too.

Here is what Notion's own page does not say, and what you should therefore test instead of assume. It does not state which Google sharing setting a sheet needs, whether a viewer can edit the sheet from inside Notion, or how the embed behaves for someone who lacks access to the file. Third-party guides commonly say the sheet must be shared so that viewers can open it, and that matches how Google's own permissions work: an embed shows what the viewer is allowed to see, nothing more.

Notion's help center does carry one warning that bites here: embeds that require a login to an external site will not work in Notion's desktop or mobile apps. A sheet that opens fine in your browser, where you are signed in to Google, can show an empty or failed block on a phone. If your team reads Notion on mobile, open the page on a phone before you tell anyone it works.

The Embed Privacy Test

Before you embed, ask who will open this Notion page. If the answer includes anyone outside the people already invited to the sheet, you have two choices: widen the sheet's sharing, or do not embed. Widening sharing to anyone with the link is the quick path that most tutorials show, and it is wrong for client data, salaries, invoices, or anything under a contract. A link that opens without a login is a link that can be forwarded.

A safer pattern for sensitive sheets is to keep sharing restricted to named people, embed it, and accept that viewers outside that list see an access error. The embed then follows your Google permissions instead of replacing them. It is less convenient and much harder to leak.

A good use for the embed

Charts. If your sheet feeds a chart or a summary block that people only need to glance at, an embed of that one range keeps the numbers current without any automation. The moment someone asks to filter or link those numbers to a Notion task, switch methods.

How Do You Import a Google Sheet Into Notion?

Export the tab you want from Google Sheets as a CSV, which downloads one tab at a time, then import it. Notion's help center gives three entry points: Settings, then Import, then CSV; typing /csv on a page; or, from a full-page database, the Merge with CSV option on the menu. A fresh CSV import creates a new database where each row becomes a page and each column becomes a property.

Notion's import article spells out the traps, and they are worth knowing before you click:

  • Numbers with symbols can fail. Values with a dollar sign, a percent sign, or a negative sign may not map to a Number property. Notion's advice is to map those columns to Text, then convert after checking the result.
  • Mixed columns become text. If one column mixes numbers, words, and dates, Notion may import the whole column as text to avoid losing data. Clean the column in Sheets first.
  • Dates arrive as MM/DD/YYYY. A sheet that uses day-first dates will misread any date where the day is 12 or lower, so check the first few rows against the original.
  • Commas break Select. A cell containing commas may not show when mapped to a Select property. Map it to Text instead.
  • No formulas, rollups, or relations. A new import cannot create them. You rebuild formulas and rollups in Notion afterward, and a CSV column can only fill a relation that already exists.
  • Size and file limits. The article lists 5 MB per file on the Free plan and 50 MB on paid plans, and one CSV at a time.
  • Headers must match. When you merge into an existing database, the CSV headers need to match the property names exactly, and the first row must be the header row.

What Does Merge With CSV Do to Rows You Already Have?

This is the trap that turns a one-time import into a slow mess. Notion's article says CSV merges add rows and do not update existing rows, and it warns you to watch for duplicates. If you export the same sheet every Friday and merge it, every item that did not change arrives again as a copy, and every item that did change is now in your database twice with different values.

The fix is a rule, not a feature: use import for a snapshot, not for a living list. If you find yourself importing the same sheet a second time, you want an automation or you want to stop moving the data, and the sections below cover both.

Can Zapier or Make Send Sheet Rows to Notion?

Yes, and for an intake sheet it is often the best method. The pattern is a trigger on the sheet and an action that creates or updates a Notion database item. Both tools offer it, and both have trigger choices that decide whether it works for you. I compare the two platforms in general in the Zapier vs Make breakdown, so this section covers only the Sheets-to-Notion details.

On Zapier, the Google Sheets app offers a trigger for new rows and one for new or updated rows. Zapier's help center lists a 15-minute polling interval on the Free plan, with shorter intervals on paid plans, and community discussion describes the non-Team-Drive Sheets triggers as hybrid, meaning Google can notify Zapier instantly with polling as a backup. Users report delays well beyond the stated interval when Google does not send its notification, so treat "near real time" as "usually soon" and measure it on your own sheet.

On Make, the choice matters more. Make staff describe the Watch New Rows module as a polling trigger that watches only new rows. The instant option, Watch Changes, is described in Make's help text, as quoted in its community forum, as watching only changes made by a person in the Google Sheets app. It does not fire for edits made by scripts or API calls, and it does not watch newly added rows. A sheet that another automation writes into will therefore not wake that module. This is the kind of detail that makes a flow look fine in testing and fail in week three.

Why Do Automations Miss Edits and Deletes?

Because most of them are watching for an event, not comparing two tables. A new-row trigger fires once per row. If you then fix a typo in that row, nothing is listening for the fix unless you chose an updated-row trigger. Even with one, a deleted row is a different problem: a row that no longer exists cannot produce a change event, so I would not assume either tool announces it. Check the trigger list of the tool you use, and prove the behavior by deleting a test row.

Row numbers cause a quieter failure. Sorting a sheet or deleting a row shifts every row below it, and an automation that tracks rows by position can misfire or skip. Make's own forum has threads from users whose new-row watcher stopped tracking correctly after a row was removed.

The Stable ID and Last-Synced Columns

Two helper columns fix most of this, and they cost almost nothing. The first is a stable ID: a value in each row that never changes when the row moves, such as a short code you type once or a unique string a script writes when the row is created. Do not use the row number. Store the same ID in a Notion property so the automation can find the existing item and update it instead of creating a duplicate.

The second is a last-synced column. Have the automation write the current time back into the sheet after it updates Notion. Now you can see at a glance which rows have never synced (the cell is empty) and which have gone quiet (the time is old). A blank is a visible failure. Without this column, a broken flow looks identical to a quiet week.

Add one weekly check on top: count the rows in the sheet and the items in the Notion database. If the numbers differ, something drifted, and you found out in five minutes instead of at the next client meeting.

Are Two-Way Sync Add-Ons Worth It?

Several add-ons in the Google Workspace Marketplace advertise two-way sync between Sheets and Notion, including Addsync, SyncSheetsPro, and Sync2Sheets. I am not ranking them, because I have not stress-tested them, and a vendor's own listing is marketing. What the listings do show is the shape of the trade-off. One listing mentions refreshing as often as every five minutes, and the same listing states it can see, edit, create, and delete all your Google Sheets, which is the access level any tool needs to write back to your files.

Read that permission line before you click Install. A tool that can edit every spreadsheet in your Google account is a larger trust decision than an embed, and it belongs in the same mental category as giving an app access to your whole Drive. If the sheet holds client data, consider whether a copy of that sheet, limited to the columns you need, is a safer thing to connect.

Why Two-Way Sync Creates Loops and Overwrites

Two systems that each treat the other's change as news will pass the same edit back and forth. You change a status in Notion, the add-on writes it to the sheet, the sheet counts that as a change, and the add-on may write it back to Notion. Good tools guard against this, but guards fail at the edges, and the edge is usually two people editing the same row within one sync interval. One of the edits loses, silently.

There is a second, structural problem. A Notion database is relational: it has select options, multiple values, relations, and rollups. A sheet is flat: a cell holds text or a number. Anything that does not fit in a cell is either flattened on the way to the sheet or lost. Two-way sync between a rich database and a flat grid therefore always involves a translation, and translations leak.

If two people can edit the same fact in two places, you do not have a sync problem. You have a source-of-truth problem.

The One-Direction Rule

The most reliable setup I know is boring: pick one side as the source of truth and sync one way only. If the numbers originate in Sheets because that is where formulas and finance live, push rows into Notion and treat the Notion copy as read-only. If tasks and statuses originate in Notion, push to Sheets for reporting and never edit the copy. Write the rule at the top of both: "Edit here. The other side is a mirror." Mirrors do not loop.

This also answers the permissions question. A one-way flow needs a connection that writes to only one side, so you can give the tool read access to the sheet and write access to a single Notion database.

If you write your own script

Google Apps Script can call the Notion API, and Notion's API only reaches a database after you share that database with your integration. Notion's API documentation also sets an average request rate of about three per second, so a script that pushes hundreds of rows needs a short pause between batches rather than one fast loop.

A Decision Guide for Notion and Google Sheets

Use these in order and stop at the first one that fits.

  • Just need to look at it? Embed the sheet, check it on your phone, and keep sharing restricted if the data is sensitive.
  • Need it inside Notion once? Clean the sheet, export the tab as CSV, import, and map symbol-heavy columns to Text. Do not import a second time.
  • Need new rows to arrive over time? Use an automation with a stable ID and a last-synced column. Test with an edit and a delete before you trust it.
  • Need both sides editable? Reconsider. If you still need it, pick a source of truth first, then check what permissions the add-on requests.
  • Is the sheet really a task list? Stop syncing. Keep tasks in one place, which is the next section.

When Should You Stop Syncing Sheets and Notion?

Count the tools your tasks live in. If a task starts as a row in a sheet, is copied to a Notion board, and then someone asks about it in chat, you are not syncing data, you are maintaining three copies of one commitment, and the sync is the work. I made the broader case in Notion is not a task manager, and the same logic applies to a sheet that was never meant to hold tasks. The honest comparison of the two as task tools is in Google Sheets vs Notion.

A sheet is wonderful for numbers, lists, and the occasional script, and the ideas in Google Sheets automation scripts show how far it goes on its own. If most columns in your sheet are task, owner, due date, and status, the sheet is doing a job that a task app does better, and no sync method will make it less awkward.

This is the one place Mursa fits. It can import tasks from a Google Sheet you choose, shows a preview of the sheet's headers and rows first, and then the tasks live in one place with times attached. That is a one-time move into a task tool, not a sync, and I would use it exactly like the CSV import above: bring the list across, then stop maintaining the sheet.

Common Mistakes When Connecting Notion and Google Sheets

  • Treating an embed as a connection. It is a window. Notion filters, relations, and rollups will not see the numbers inside it.
  • Merging the same CSV repeatedly. Notion's merge adds rows and does not update them, so repeated merges multiply your data.
  • Tracking rows by position. Sorting the sheet moves every row. Use a stable ID.
  • Trusting an automation because it ran once. Test an edit, a delete, and a re-sort, and keep a last-synced column so silence is visible.
  • Granting broad access to save five minutes. An add-on that can edit every sheet in your account is a bigger decision than the sync it provides.
  • Syncing both ways by default. Choose a source of truth first.

None of these is exotic. They are the ordinary results of choosing a method for the wrong job, which is why the first step is always the same question: what must happen in Notion when a cell changes in the sheet, and how soon?

What Should You Do This Week?

Open the sheet and the Notion page you are trying to connect, and write down the single sentence your setup must satisfy, for example "new rows from the intake sheet appear as Notion items within an hour, and edits in Sheets update them." Match that sentence to a method above. Add a stable ID column and a last-synced column before you build anything. Test on five rows. Then add the weekly count check. The whole routine takes an afternoon, and it replaces the version where someone discovers in a meeting that the numbers are a week old.

Common questions

Frequently Asked Questions

Does Notion have a built-in Google Sheets integration?

Not a sync. Notion's help center documents embedding a Google Sheet through the Google Drive embed and importing a CSV, but neither keeps a sheet and a Notion database in step. For ongoing syncing you need Zapier, Make, a Marketplace add-on, or your own script.

How do I embed a Google Sheet in Notion?

On a Notion page, add an embed block and paste the sheet's URL, or use Browse Google Drive to pick the file. The embed shows the sheet but does not turn it into Notion data. Check it on a phone, because Notion warns that embeds needing a login to an external site will not work in its desktop or mobile apps.

How do I import Google Sheets data into Notion?

Download the tab as a CSV from Google Sheets, then in Notion go to Settings, Import, CSV, or type /csv on a page. Each row becomes a page and each column becomes a property. Map columns with dollar signs, percent signs, or negative numbers to Text, because Notion may fail to map them as Numbers.

Does Notion's Merge with CSV update existing rows?

No. According to Notion's import article, CSV merges add rows and do not update existing rows, so importing the same sheet repeatedly creates duplicates. Use a snapshot import once, or switch to an automation that matches rows by a stable ID.

Can Notion sync with Google Sheets automatically?

Only through a third-party tool. Zapier and Make can create or update Notion items from sheet rows, and Marketplace add-ons such as Addsync, SyncSheetsPro, and Sync2Sheets advertise two-way sync. Test edits and deletions before trusting any of them, because many triggers only fire on new or changed rows.

Why does my Make scenario not trigger when a script edits the sheet?

Make's help text for the Google Sheets Watch Changes module, as quoted by users in Make's community forum, says it watches only changes made by a person in the Google Sheets app, and script or API edits do not trigger it. Use the polling Watch New Rows module for new rows, or trigger the scenario from the script itself.

Is it safe to share a Google Sheet publicly so Notion can embed it?

Not for sensitive data. A link that opens without a login can be forwarded to anyone. For client, financial, or personal data, keep sharing restricted to named people, accept that others see an access error, or use a limited copy of the sheet.