Hey @Jon
I finally managed to do what I wanted, your tips helped me a lot, I’ll share below how my flow turned out. Basically what I did was:
1 - I created two nodes in the first I got all the appointments from my Google Calendar, and in the second I got the appointments that are in the Notion calendar;
2 - I created two nodes to define which data from each Calendar would be used;
3 - I created a Merge node with “Remove Key Matches” because it keeps the data from entry 1 (Google Calendar) if it does NOT find a match with the data from entry 2 (Calendar Notion), this way the flow does not duplicate existing appointments in Notion;
4 - I created a Notion node to create new appointments in my Notion calendar, and I made the correspondence in the data so that when creating a new event it puts the data in the right field.
5 - I created one more merge node with “Keep Key Matches” as it keeps the data from input 1 (Google Calendar) if it finds a match with the data from input 2 (Calendar Notion), however when I run the flow the data didn’t update in Notion, that’s when I searched and found that to update Notion’s data I would need Notion’s item id, that’s when I created 3 more nodes, one to create another Google Calendar data definition where I inserted some fields with empty data these fields correspond to the fields contained in Notion so that when you merge the data they are filled with the information coming from Notion, another node I created was to merge with “Merge By Key” because it merges the data from both inputs and as a result the output will contain items from input 1 (Google Calendar) merged with the data from input 2 (Calendar Notion), and as a reference the merge happens depending on a key defined in the case the id of the appointment of goo gle and the same id as contained in Notion’s commitment as I inserted it into the creation flow, these two nodes were placed before the “Keep Key Matches” mentioned above, so the data output now contains all the information that is needed to update appointments in Notion;
6 - Before the Notion update node I placed a definition node to select the data I would need to update;
7 - I created a node to update the notion and made the correspondence between the data so that when updated it can update the data in the correct fields.
This was the way I found to sync my google calendar with the notion, another job I have now is to duplicate this flow for all the calendars I have in google calendar, as I have an agenda for each appointment category.
My final workflow: