1. Home
  2. Automation
  3. automate.io
  4. Google Drive to Notion Database

Google Drive to Notion Database


I’m completely in love with Notion, Google Workspaces, and Automate.io – independently.

As an intermingled offering, these platforms offer everything I could ever ask for!

Automate.io has enabled me to create behind-the-scenes automation to auto-populate a Notion.so database with all files that are added to my Google Drive.

Let me show you what I configured.

When you set up a free (YES!) account with automate.io, you are given 300 actions per month for free. That’s more than enough for me to get started!

“Create a bot”, use one of their pre-selected options if you want, or start from scratch. Either way, it’s self-explanatory.

You first need to select your “TRIGGER”, which is the action that’s going to trigger the actual actions that you’ll build in – later.

  1. For me, it’s the Google Drive app > When File is added trigger.
New File Added in Folder

Then, you’ll want to add your first action, after that initial trigger supercharges the bot that you’re creating.

2. Select the Notion App > Add Database Item

Backtracking, we need to identify the folder in the Trigger category that will be monitored for new files – mine is called “Notion”. Once you identify that folder in your Drive, you can move on to Action 1.

In action 1, you’ll select the database that you pre-built – mine is called “Google Drive database”.

You’ll also want to select the Heading and Paragraph parameters.

You’re not done!

3. Create a new action (Action 2), select Notion App > Search Database item

Database > “Google Drive database” > ID > Item ID

One final step!

4. Create another action (Action 3), Notion App > Add Content to Page

And build it out however you want, or select what I have below:

  • Custom Value for Page/Item
  • Item ID
  • Heading 1,2, and Text Fields

That’s it! The notion is being populated with a Google Drive database of all files added to a repository folder.

Play around with the data types you want to be ported over, but in general, it works perfectly for me to know when someone makes a change to a document or added new documentation to a folder. Mix this with a few sorting/filtering options and you have a dynamically updated database with no code!

Tags , ,