Hi everyone. As you saw in my last video,
I'm really excited about the possibilities that have been opened up by the Notion API,
even for non-coders using Zapier and Automate.io. And in this video, I'm going to dive right
in, get my hands dirty share with you how you can put this to use immediately, with
one of the most high-demand, highly requested automations. And the one that I listed in
my last video as my number one priority of integrating our comprehensive Notion life
operating system. With Google Calendar, we want to have automated updates of the events
in our Google Calendar. And in our notion, Master task database. Some people may have
an events database just for events, but in Pillars, Pipelines & Vaults, the system that
we've been covering in this entire series, or really any comprehensive life system, typically
you'll have a master task database that will have events in it ideally, in the past, we
may not have always updated it because it was too much work. Now we can automate a great
deal of it, I'm going to look at every combination of automation. So it'd be creating events,
updating and changing events, deleting events. And I'm going to look at both the movement
from creating an event in Google Calendar, automatically updating a notion. And I'm going
to look at updating originating an event and notion. And automatically having that update
in Google Calendar, a lot more of these combinations are possible than had realized not all of
them, but a lot of them. And it's to the point now, where right out of the gate, this is
an extremely usable set of automations. It's more than one case, you need to set up different
triggers and actions for each of these different scenarios. But the majority of the ones that
I think are most important, are ready to go and totally working. And that's what I'm going
to show you how to do today. And I'm going to show you how to do it in a real active,
fully operational master tasks database. So we're not just going to look at small simple
test databases, the notion, we're going to dive into the full complexity of our fully
operational master task database, which in our PPV system, we call action items. But
it will work with any fully functional, fully built out master task database. And in some
ways, it's more exciting to see it working with the full complexity of the fully operational
master task database than a simple test database, because you can see all the variables that
are capable of transferring information across and in our case with the pillars pipelines
and vault system that we've been covering in the series, we want to make sure any synchronization
between Google Calendar and our action items database is going to be tagged specifically
to be a scheduled item because only the scheduled items in our action items database have specific
times those are the ones we want to sync with Google Calendar, and not touch any of the
others that have a priority other than scheduled. We'll see this in action when we dive into
the notion system. But just as important as the technology level automations, we also
have to think of the workflow that we want. And in many cases, you might have multiple
workflows that are equally valid or equally appealing. But some leverage the tech automations
that are viable now more than others, we happen to be very lucky in this case, because the
workflow that I most want the one that I would ideally choose regardless happens to be the
one that best leverages the automation technology that's currently available. So in addition
to sharing the tech implementation, I'm also going to talk about the workflow and the human
practices that I will be conducting to maximize the capability of the current viable automations.
A quick note before we dive in my free template pack is available to anyone who signs up to
my free newsletter link to that below. And information on my upcoming notion life OS
course which will be shared at notion life OS comm is also available at the link below.
And with that, let's dive in, we always start with the command center, and we'll go straight
into our action zone. So this is my actual personal action zone that we'll be working
with, I want to show you how to bring these automations into a real life operational full
master task database, which again, we call the action items database. Now a couple setup
notes. If you're familiar with the PPV life OS that we implement here, this will all be
familiar. If not, I have a whole video on the action items, Master task database that's
previously in this series and another whole video on this action items dashboard that
shows you how to put this into good use. Now the automation with Google calendar will be
working directly with the database for the action items, and will be interacting with
it primarily in the actions own dashboard. So those are both relevant videos. If you
want to catch up on those, we have to do a little bit of modification to the action items
database to be ready for this, you will need to add at least one maybe two
properties, we need to add the G Cal link this is a link to the Google Calendar entry.
So when it creates the entry, we'll be able to click here and go straight to the Google
Calendar link, which will be a really nice connection between the two systems. It will
only be the scheduled entries that we want to sync and our scheduled entries will have
a specific time. So we'll set that time to whatever we choose, but it's going to be one
of the scheduled priorities. other priorities are not going to have specific times only
the scheduled entries have specific times, if you're just creating a general events database,
then everything may have a specific time, that would be all events, but we combine our
events with our action items. So it's all together in one view, in the way we do that
is you have a priority for all of them. And then those that are scheduled have a scheduled
designation. That way, they're all stacked together, each with the time and you'll see
everything together in order because they're sorting it by date. And the date sort, even
if they're on the same date like they are in this today. Toggle will sort by time as
well. So they'll be in sequence. And that way, we don't miss anything, as we're looking
at our priorities through the day. And we don't have to go over to the Google calendar
to check our events. We can be here with all of our prioritize tasks, and our scheduled
events together. That's why sinking them is so valuable. But when we open this, we need
to make sure we have that Google Calendar link added and that it is a URL type property,
or due date will serve as our starting time and the date for the event. So it's important
to have a time and as we create them, they will be created with times. The additional
thing is I have always had a completion date. This was renamed from the due date, d u e
date since our D o date is the date we plan to do it. In this case, we're going to use
this not as a date in the future, it must be finished by which we occasionally need
to have that date. So this will still be here for non scheduled tasks that we do want to
have a fixed completion date. But for the sake of scheduled tasks, it will be an end
time because the sync with Google Calendar, we need both the start time and the end time
and notion we don't need an end time. But in Google Calendar, you do so we need that.
So if you don't already have an end completion date, then your notion test database, you
need to add that as well. And that's obviously a date property. With those two additions,
you're ready to go. And I have set these two to hide the property when empty. Both of them
are hide when empty. This is really useful, because that way they won't clutter the screen
here. And typically they'll just be invisible because most of the tasks in here are not
scheduled events. So you don't want that cluttering but when they are populated, the information
will be here. So you'll have that link without having to open the other properties to click
straight over into Google Calendar. And with that you're all set. Now you're going to have
to connect your notion workspace to Zapier. I'm going to be doing this in Zapier. A lot
of this can be done on automate IO. Having experimented with both a bit, I do get the
sense, Zapier can do more of the things that I'm trying to do here. Although automated
IO is very close, and I imagine that gap will be completely closed very soon. Also, I already
use Zapier a lot for my business, Zapier tends to have more connections. But once you get
to the paid plans, it tends to be a little more expensive. So that's the trade off. But
both have free plans that let you do a lot of this. If you're not doing super high volume
of automated triggers. And just for updating your calendar, most people probably won't
be hitting that limit too quickly. I'm not going to explain how to connect your notion
API to Zapier. I'm going to link below to notions explanation on how to do that if you
don't already know how to go into integrations here. And you're going to click develop your
own integrations. If you don't know how to do this, all you have to do is click this
link here learn about managing integrations and it will open the integration instruction
on how to create a code and notion that you can then enter in Zapier or automate IO, and
then that will connect notion to those services. So with that all set up, go to Zapier. Now,
I've already created these, but I've turned them off so that we can create them from scratch.
So we're going to create a zap, you start by the trigger. The way Zapier and automate
both work is you have a trigger, and you have an action. That's the cause and effect. So
the trigger is the cause that initiates the action is the effect that results from that
trigger occurring. So you start by typing Google Calendar, and you choose Google Calendar, we're going
to focus most on initiating with Google and having that update in each of the scenarios
to notion because in Google Calendar, you have a lot of automations already coming in,
you have calendly invites, you have zoom calls, automatically adding calendar invites, you
have lots of different software that trigger the automatic adding of calendar invites that
we're not even doing and you want all of those to automatically populate into notion in your
master task action item database. So the most important thing is we capture all those. And
then if we commit to the workflow of initiating our creations in Google Calendar, as well,
then we have a consistent pattern. And we're not going to trip ourselves up, we are able
to create a new scheduled event in notion and have it automatically added to Google
Calendar. But as I'll show you later, that creates problems. Whereas if you're always
creating initially in Google Calendar, and doing your updates in Google Calendar, then
you have a workflow that's really solid, but it's also going to be the better have two
workflows. I would prefer to have them initiated in Google. If I have to pick one over the
other. Ultimately, we'll be able to do both. I think right now if you commit to initiating
any changes or creations or deletion During a Google Calendar, you're then going to have
all your events perfectly synced with notion. If you're initiating a notion, there are going
to be situations in which things don't update. And I'll explain that toward the end. When
I talk about triggering events in notion and adding them to Google, which is possible,
it's just a lot more limited. So we're going to create a series of actions in Google calendar
that will sync with your events in notion, and we have to have at least three scenarios
covered creating an event, updating or changing an event. And deleting or canceling an event.
The simplest way to do this is to have each of these as a separate zap a separate trigger
an action is possible if you're on a paid plan to have a series of these actions stacked
on each other. But let's just keep it simple. And if you did want to stack them on a paid
plan, then the instructions here are exactly the same. You just do it as multiple actions
from the same trigger. But these three independent actions can be done on the free plan. First,
we want to set it up. So when you create a new event in Google Calendar, or one is automatically
created will automatically be added also to your notion action items database, or any
master test database. And the way you do that is you choose Google Calendar as we did here,
then you choose a trigger event, we're going to choose new event, hit Continue. Now we
need to choose the account, I have one of my accounts set up already. If you want to
add any new Google Calendar account, all you do is click new account. Here, I've set one
up, this is a test one an email that I'm going to be retiring here very soon. So I thought
it'd be a good test one to do here, that YouTube video. So I've already set this up, but you
just click here to set up a new one. And of course, you can set multiple ones up, click
Continue. Now we choose the calendar within that account. So if you have multiple calendars,
you'll have the option to choose any of them. Let's use the main one and continue. Now in
order to test it, you need some data in it. So we're going to jump over to the calendar
itself. And right now it's empty because this is a test calendar. So we need to add a few
events, we want to have those created before we test when we hit test, it's going to pull
one of those, you can choose the one if you want to switch to a different one it chose
today test. That's good, it shows us all the data from in there, that'll be helpful going
forward. So we continue it runs the test, and it moves forward. And now we choose notion.
We choose an event, we want to create a database item creating an item in the action items
database, we're gonna choose an account, we've already linked this, if you haven't already
linked this, you'd hit connect a new account, it'll ask you for the code that that link
I showed you in notion, you would then enter that code here. I've already connected it.
So I'm going to continue. Now we choose our database. In this case, we want the action
items database, which is the name of my master task database. Now we want to define the action
item, which is the title. This is the title of the text field in the action items database,
this one singular, that one is plural, because that's the name of the whole database. This
is the name of the text Title field for each entry in the database. So we want that to
be the title of the calendar event entry in Google Calendar. And by running that test
event, we see a sample data today test was the name of the event we entered for today.
So we'll click that. And we're mapping the title from Google calendar to the title in
the action items entry AB status. In most cases, those of you using PPV, this will be
active AB status is my personal status status would be what it's typically called when you're
running the system by yourself it active, you want every item that come in to be active
because remember our action items today toggle is filtered only to show active tasks. Same
thing with all of the views on our action zone. Our calendar only shows the active tasks.
So we want to automatically check the active status and not do waiting pause next up or
future. So that'll be a fixed attribute assigned to every event entered from Google Calendar owner. If you want to assign yourself as the
owner, if you have multiple people using your system, you could assign yourself as the owner
here or whoever you want assign it to priority. This is where we choose schedule. This is
important in the PPV system. If you're just doing a general events database, and they're
all scheduled events, then you would need this. But this is how we are certain that
every event created in Google Calendar that's added to notion will be prioritized as a scheduled
event. That will be that's a great feature. So here we're seeing all the properties in
our notion database. And we can choose what information comes from Google calendar to
be passed over, in which we want to be automatically assigned the same thing every time in that
property field. Others we may skip there's a note field, I'll skip that due date. This
is important. This is the starting time and the date of the event. So now we want to click
on all these properties in Google Calendar. Now we want to bring over dynamic information
from Google Calendar and you want to show all you have an option for a prettier version
but you want the original one I think both would work. Zapier is really good at interpreting
dates event begins, which is a date and a time you want added to the due date. And it
will automatically assign the time that you've scheduled it. Done. This is the checkbox you
don't want anything checked is done to leave it blank privates blank Now Google Calendar
link, we've created that additional field. This is going to be important. So we have
a direct link from our entry to the Google Calendar entry. And since we're going to be
doing our changes and maintenance of events in Google count Having a direct link to that
Google Calendar entry from notion is super valuable. So you want to click here, show
all options and find the HTML link. And then any completion date, this is going to be the
event ends entry. That's going to bring the end time from Google calendar where the event
is created to notion content is the body. So here we want what Google Calendar calls
the description. This case, we left it blank, so it doesn't have any sample data is better
for your sample test ones to fill in all the fields you want to transfer over, I just happen
to know which description so we'll click that if we had entered content in the body of today's
entry, then that would have some sample data. And we would be easier to match that up. But
I just noticed description. So be sure to add description to content. Now hit Continue.
And now it pulls the same sample test run from the first trigger. That information is
here. Now we test the writing of that information to notion it said it was successful. Now we
want to jump over to notion and see if it was the today entry has been added. And we
see today test is right there. We scroll down to the calendar. Today test is there, it has
the start time that we entered the end time that we entered, and it has the Google Calendar
link. Now if we click this, it'll take us right to that entry in the calendar and pop
it open. And if we want to modify it or change it, that's where we do it. That's where workflow
comes in. By doing all of our entries, modifications and deletions in the Google Calendar side,
we have the ability to do a lot more than if we initiate on the notion side. But by
having that link here and notion, it makes it very easy to do it added the scheduled
tag and added active it added the title. If we had had a description it would have entered
down here. So now that we're done and it's successful, you turn on zap here or you turn
it on up there. Either way you have to turn it on, or it won't start working. All right,
it's time. Now we're going to go back and test it with a real live one. Okay, so now
let's add a new one in the future. You could add it in the past, it doesn't matter, you
can edit anywhere, let's choose the 25th test that 25th. We'll give it a time 730. And at
and really late, let's say 1130. So that's all 730 to 1130. Let's enter some text here,
testing the script here. So just showing that the rows of data, say that we entered one
for the 25th. And there it is popping in about a minute later on the 25th. Now I'm on a paid
plan with Zapier and I believe it comes through a little faster, it could take up to 10 minutes
on the paid plans zaps happen faster on the non paid plans, they still happen reasonably
fast, within say 10 minutes or so. But this came through really quickly for me, I'm on
a paid plan, but it would have come through within 10 minutes. If you're testing them
on your own, give it a good 10 minutes. So entered here, entered active, enter the start
time, enter the end time that we entered, give us the direct link back entered scheduled
and gave us the description down here. How awesome is that like that is fantastic. And
that'll happen with ones automatically entered with zoom with calendly with anything or the
ones you enter yourself. Now we want to be able to update and change them. So we need
to create a new zap Google Calendar. Now we want to do new or updated event. Google Calendar
again, choose the calendar that relevant to you. Within that calendar account, choose
the calendars you want to test the trigger. Same as before, we've
got a sample coming through here continue. Now this time, we have to do an intermediary
step because we're initiating a change or edit in Google Calendar. But we're going to
need to update something that already has been entered as an entry in notion. So we
need to identify the one a notion that we're going to be modifying. So before we can actually
apply the change, we have to find the entry we want in notion and we do that by clicking
notion here. And the event we're going to choose is search find database item. And now
we choose our account just like we did previously continue. And now we need to pick the database
again. Again, each action is specific to a particular database. You then work with any
database in your notion workspace. And we need to find a way to identify it. If we use
action item, that's the name, you could have multiple ones with the same name. So that's
not a reliable way to reference them. We're not entering notes very often anyway. So that's
in we're not transferring that data from Google Calendar. So that's not a way that we can
match them. The only option we're given of the properties we currently have in our notion
database is the Google Calendar link, but that's perfect because that's going to be
unique to each entry. So we enter this, we go down here we find among the Google Calendar
properties, HTML link, which is the same link we used when we created the event. And so
it's serving double purposes. Both As a quick and easy way to jump back to Google calendar
for any changes we want to make, and a way to identify that and pull up that notion record
to match it with the entry that we're modifying in Google Calendar. Leave this one false,
because we only want changes to affect notion entries that are already there. We don't want
to be creating any new entries in notion, because this remember was new or updated event,
but new will be ignored, because it won't find any that already have that gkl link in
it. Now we test and review it found one and matched it, we move on close. Now we need
to apply the change. So we choose notion again, we choose Update database item in notion continue.
We choose the notion account, we have linked, we continue, we choose the database. Now by
default, Under Item, these are specific entries, you don't want a specific entry, we want it
to be custom for each iteration that's running each zap each automation that's being applied.
And we need to find the notion ID right here notion ID, we pulled that up by the search
function here. The reason we needed to do this was to identify the right entry in notion.
And that pulls up all the data from notion. And now we have the notion ID which we didn't
have from the Google Calendar side. So we now have a notion ID, if that doesn't make
sense, just enter notion ID and it'll work. Don't click it twice, or it'll enter twice,
just once. And then we're there. Now, these are the properties that will be written over
what's already a notion with the edits we make in Google Calendar. So if the name of
the event changes in Google Calendar, we want that to be updated. So the title here, test
is AP trying fifth is the title in the Google Calendar, we're choosing that to update if
it changed in action items in the action item title, or name of the action item in our notion
database. If nothing changed, it'll just write the same name on top of it, which will be
fine. If it changes, it'll write the new name on top of it. So a title or name change of
the event will come through to notion we don't need to update this because that's not going
to change. None of these are going to change priorities already set, it's not going to
change, the due date could change. That's the start date and time of the event. So we
need to choose from the Google Calendar list. The event begins property, don't use these
because these are not changing the calendar links not going to change the end date, which
in this scenario is the end time could change. So that we need to add here as well to map
that over for this change automation. And we'll scroll down to event ends. Now the body
of the event could change. And I would love to have that ability to change the content
in the notion page, if the description changes in the Google calendar event. However, in
my testing, this doesn't work. As of today. This simply doesn't work. When I choose description here, which is what you
would do, when I choose description here is even got the sample data this time, enter
that here. This should map over any changes to the description in the Google calendar
event. I have tested this over and over and over again. And it simply doesn't work. So
my preference would be to have that updated. And then again, remember make all changes
on the Google Calendar side, not the notion side. But since it doesn't work, I'm just
going to leave that empty. So that I at least have the option to add notes on the notion
side. And if that starts working one day, I will add that and so now I've got the data
here, we're going to hit test and review. It said that successful. So whichever one
this was, so this one was already entered, and we didn't actually have a change. So there's
nothing for us to go check a notion. But now after we activate the zap, we turned it on
either here or in the upper right corner. We have it going now. I forgot to in the other
one, you need to name the zaps here. We're going to call this G cow update. Edit. I use
double arrows to notion action. items. Name it's very clear because you'll have a long
list of these eventually, we've turned it on. And then we go back. And now realize I
forgot to title the other ones. So we'll do that now. Name your zap here. That's the calendar
to notion setup. We'll name that the previous one we did g cow new event to create notion,
action item event. Alright, and that one's on. Now we're going to test this and let's
move them around. Let's take the one on the 16th and move it to yesterday and the one
on next Tuesday and move it to tomorrow. Now back here, watching this one. And we're watching
this one from the 25th and we'll see them move in It should be done within probably
five minutes at the most 15. But I'm finding that they take about a minute or two, there
they go, that popped over here and this one down here popped over here, everything else
is the same. Let's do a name change. new title, save, let's get a new title here. We're watching
the test zap here. And now we have the new title, new title is here, that took about
four minutes I cut out. So you didn't have to wait with me for that. But took about four
minutes for that title change, and then for this title to change. So it comes through
if you make the change. And once you've done enough testing, you're just going to trust
it and let it go. And it'll be ready for you next time you come back to your action zone.
I've got two more options. And one of them I think is important. But the other one I've
decided not to do, I'll explain that we add Google Calendar as a trigger. So we have event
cancelled, we want to make it so that if we delete an event in Google Calendar, they will
remove the event from our notion action item. So now we're going to do event cancelled and
then I'll talk a little bit about event ended to automatically check it as done. But first
event cancel if we actually delete the event. We go to Google Calendar, choose the calendar
you want. Choose the calendar within the calendar account, hit Continue. You want to have deleted
one already. So you'll want to go over to your calendar of one of the ones you are testing
already delete one of them, so it has something to pull in here. When you do the test. I've
already deleted some but so I have some in there for to pull up, it pulls up a deleted
event status canceled, so I already picked one, we hit Continue. Now we have to identify
the one in notion that matches the one that we're deleting. So again, we have to have
this intermediary step, we choose an event which is find item and database. This will
be exactly like the intermediary step in the previous one, we choose notion user database
action items in the PPV case. Now here, we're not going to do it by title of the entry,
we're not going to do it by note, we're going to do it by the GL link, which is the HTML
like that's a unique identifier that we have already written from the Google Calendar entry
to the notion entry when we created it, this is false. Next, now I was having trouble testing
it, I think because the calendar link has already been deleted, so we can skip this
step. And close. Now we go to notion, update database item. Continue. She's our notion
account. hit Continue. Choose our database. The item again is going to be the notion ID
custom notion ad that was pulled when we did the search here. Now we don't need to change
the action item here. We're not changing the title. We're not changing any of these properties.
The one thing we're going to do is check it done. And done. A checkbox and notion is a
true setting in Zapier. Now, we cannot actually delete because you'll see here, we don't have a delete database item, we have
a CREATE DATABASE item and update database item in find search, we're missing an important
one, which is delete database item. Eventually, we're certainly going to have this there's
no question we're going to get that but right now we don't. So the way we do this is we
check it done, and it will disappear from all of our filtered views. So you're done
is true true means check the checkbox in our action items database. Now, you could of course
set up a whole new property that's labeled delete or canceled or removed. And you could
check that but the problem is then you'd have a whole new property in the action items database,
where the done checkbox works just as well. And you'd have to in every instance that you're
filtering, for a view of your action items, you'd have to add an additional filter that
the checkbox is not checked. And so it just adds a lot of extra baggage to maintain. By
checking it done, it disappears from all of our active views. The only downside of this
approach is it will now appear as a completed event in your weekly or monthly reviews or
anytime you go back to look at historically completed actions. To me that's not a big
deal. I'll know if an event didn't happen. I'll just disregard it. And it's simpler just
to have the one property and the one filter in all the filtered views from action items
than to have that additional property. Of course it's up to you. But this is a simpler
solution. And it totally works. Don't need to add anything here because we're not changing
any of that all we're doing is changing the done checkbox, hit complete. Test and review
that. And now since we deleted that one and ran the test here, it was removed also from
the notion calendar so it's gone. We had an event here, our test removed it. So now we
know it's working. So now we turn on the zap. We make sure it's named g cow cancelled event.
notion x action item done and it's turned on here we go back to our main menu. Now we
go back here. And we can delete this one and delete this one. And let's see what happens.
Yeah, this one here. And we got this one here waiting to see what happens to them. And they're
already disappeared. I waited about two or three minutes for that to happen. Okay, so
now we have addition from Google Calendar modification, and deletion will remove them
from our notion, action items calendar, The only caveat so far is that the description
modification isn't transferring over to notion, but everything else is updating properly.
Now, there's also a trigger for event ended looks like you could set one up for that as
well have it automatically check it as done when you have past the time that an event
was scheduled for. But I actually don't want to do that, again, I'm thinking about an optimal
workflow. And I have such a routine of checking things done, including scheduled events. And
sometimes seeing the event that I'm going to check as done will trigger thoughts on
follow up I need to do or actions I want to take before that reminder disappears. So I
don't want to automatically disappear after an event. I may have notes attached to it.
And I want to actually process any notes or any actions, or any follow up before I check
it as done. So I'm not going to add that one. But just so you're aware, there is an event
ended trigger available here for Google Calendar. And you should be able to add that done checkbox
with as an update, just as we saw in the canceled item. Now I have tested going the other way, creating
an event in notion and having an added to Google Calendar. And it is working. But there's
a big problem. When you create the event in notion, it will add it to Google Calendar.
But the notion entry does not have the Google Calendar link. Not only does that not let
you link directly over Google calendar for any modification. And again, our workflow
is emphasizing entry and management of events in Google Calendar. But it doesn't have that
ID to pull from. So if you then go and make any modifications or cancel the event in Google
Calendar, it can't update in notion because that ID, which is the URL link to the Google
Calendar entry isn't there. So there's no way to look it up and identify it and pull
up that notion ID number. So even though you can create an entry a notion and have it added
to Google Calendar, it's a bit of an orphaned entry in that you cannot have any modifications
to it from Google Calendar anymore. So I have found that doing all of your entries, modifications
and cancellations to events to scheduled events with a specific time to do all of those in
Google calendar will create a great synchronization across the two by creating an entry and notion
that adds it to Google Calendar, even though you can do that then prevents you from doing
any modifications to that in Google Calendar. And suddenly, you have to update each of them
separately, and you no longer have synchronization. So by simply committing to the workflow of
doing all of your event management in Google Calendar, it creates a synchronized combination
of entries across the two platforms. And I just find that as the optimal way. Anyway,
I like the idea of having one place to manage that type of entry. And Google calendar is
clearly the better place to do it. Because you have automatic entries coming in with
zoom links. And with calendly, and calendar invites, it's just already automatically coming
in there to begin with. So I'm going to make all of my manual entries on that one side,
and then we'll have two that are consistently updated together. And I am extremely happy
about that. It's taken a long time to get to the point where we had this capability.
And it is now here across entry updates and deletion. So I'm very happy with this workflow,
I have put this into effect, this is the way I work. Now. This is not something that's
necessary for everybody. It's an option. As with all of these API additions, they don't
change the foundation of our systems. They give us options on top of our systems, options
for automation. Obviously, automation is appealing, it makes things easier, it also increases
accuracy. Because if you're maintaining two systems manually, you're going to have some
discrepancy. So the accuracy is as important as the ease and convenience of it. So for
all these reasons, this is a new way that I'm managing my Google Calendar and notion
integration together, I'm going to do a series of additional videos on the API and ways that
we can optimize the pillars pipelines involved system, or really any comprehensive life management
system. So I'm gonna have a series that's going to explore additional options that are
very practical, and work with the fully built out system. So a number of videos to come,
I'm going to share how to take automations that are hugely valuable to the things that
we do in our notion life OS to integrate with the system we've already built in are already
using day to day, so the There's going to be real world implementations at full scale.
That's what I'll be focusing on in the next few videos. If that's of interest to you,
be sure to hit the subscribe button and the bell icon to get notifications of future videos.
And if you found this valuable hit, like very excited about exploring more ways we can leverage
this automation to make our systems work better, faster, more effective, and with greater accuracy.
So lots more to come. Transcribed by https://otter.ai
