Community Meetup October 8th, 2021: Product updates, Item Lists node, Lightning talks

all right so let's start with our first talk max the head of design at n10 we'll talk about the exciting things we are working on at a time max over to you thanks a lot harshal for the warm introduction as always um so there's been a lot in the pipeline i'm very excited to share um i'll give a few updates on some things that are in progress so you get a bit of a behind the scenes a sneak peek but what i'm going to start with today is the item list note that has come out that harshly referenced so he's going to be doing more of a deep dive i'll just kind of give you the greatest hits on this one um but so this is the latest node that's coming out with an aim to reduce the need for javascript in the function node so generally it's great with n that you can fall back on javascript when you need to but we want to make sure to have all the different types of things that you might need to use javascript for to have a sort of no code option for that so i would say that the item list node is the first node and feature that's coming out to sort of help tackle this but this is something that thematically over the next months we're going to be looking at how to have more nodes and features that let you do things without having to write native code so in a nutshell the item list node is has various helper functions or operations rather for manipulating the data that you have in your workflow and these operations focus on the typical um sort of challenges you might have right now when you're dealing with items and item and sort of channeling the great n8n pattern of being able to iterate over something without really having to do that in a node um so i think the best way to explain this is with a demo so i'm going to share my screen and just kind of get our hands dirty um but so what i have here is a rather simple workbook to just sort of show this out so in this example we're pulling in a checklist from trello so just to contextualize that i have let's say my board here and if i open this ticket in trello a card can have a checklist and then for each checklist we have these checklist items so if i go into my trello note here we're set up to pull in exactly this checklist that i have here if i go ahead and do that what we'll see is if we flip to the json view that by default we have one item of data coming in for this checklist and we have these check items here which is an array with four items on there matching up with these four here and um we can access them in here now um again because nan performs its operation per item we would have to use a function node to sort of promote these items in this check items array to the top level so we can perform per item actions on that so in this case what i'm trying to do is to filter by the checklist items that are completed and not completed so again we would usually have to use a function node to first get these items up to the top level so and it recognizes them as an item what we can do with the item lists node search for it here but you can also find it from the helper's core node section um so well add it to the canvas and we'll connect it here so the way this node works is we have various operations um we can split out items aggregate them sort them limit them partial is going to go into some of these other operations so i'll just sort of highlight the split out items so how this one works is we define a field to split out and then it chops all those into their own top level items so for the field to split out if we take a look in our trailer node here we see that the key where we have this array that we want to split out here is called check items so if i copy that and paste it in here when we execute this node we now have four items with those four checklists in there one thing you can do as well is you can include other items or other fields of data that you'd like included in this item so in this case if i go here we have um in this single item various uh properties like the id of card that we might want to also carry over into these items that we have there so that's possible also with this node but in this case now that i have my four items i can connect it to my if node we go in here the value that we're referencing we're checking if it's either complete or incomplete and so now when we run this workflow we can see that we had one item that was completed that checks out and three items that didn't and so at no point did we have to write out any uh javascript so very excited about that this is maybe one of the most simplest setups here we could of course include other fields um so how that might look like is if we wanted to select other fields to include we can then start adding those as we might in the set mode so in this case what i could do is go in here and let's say i do also want to carry along the id of the card because that might be relevant for us i can copy that i can paste that key in here and then do that and now we see that check items is being carried through and also that top level one thing to keep in mind is in these fields to split out these field names you do want to be writing out the key itself for that json object and not referencing it via expression um when you start working with more complicated data structures you can use documentation so if we had maybe a child element nested within check items we could define it like that if that's the thing that we want to split out to so there's a lot of other modes in this node but i'll leave that to harshal to show you how to use those um so that's uh the demo for uh the item list node please do check it out and use it and as always on our community forums um do reach out with feedback if there's certain cases that you find that aren't possible with the node because again this is the v1 of it and we expect to from your feedback improve the node and sort of add new operations and add more options so we can cover all the world and possibilities of all the sorts of things that you're trying to transform manipulate map et cetera so i'll stop sharing my screen and for the second part of my talk i would love to give you an update on some of the things that we're working on here at nan and i'm very excited about a lot of these things that are in a pipeline so one thing that i think our community's been waiting on for a while now is a google drive trigger and a google sheets trigger so there's been some technical blockers on the hood from us to realize this those are now gone and uh the google drive trigger is currently up for review we're basically doing the polishing final touches on that making sure that it's all working perfectly so that should be coming out real soon so very excited about that and as soon as the google drive triggers out that's going to unblock us to be able to deliver a google sheets trigger as well shortly after that so i don't have a timeline on the google sheets trigger but again the same sort of technical blocker that we had for google drive was the case for google sheets so as soon as the google drive triggers out you can expect that google sheets will be falling soon thereafter i think a lot of our community members would be going to be very excited about that i know a lot of us here on the nan team are as well so you won't have to do that sort of custom polling method that you might have done beforehand with google sheets um so that's um some of the nodes will be coming out of course there's many others that's just one that we're particularly excited about because that's been in the backlog for a while um outside of that um one thing that i've been working on uh with some of my colleagues here at naden is collecting a long list of ux improvements to the workflow canvas or what's also referenced as the editor ui so where you're basically building out the workforce so what we've done is we've collected a lot of these things some small changes some larger changes that we think together will all improve the ux experience for power users and for newcomers as well and so next week we expect to break ground on sort of the first batch of these changes some of the things that we'll be focusing on is making node states a bit clearer so you know when a node's errored out or successfully executed and then also clarifying where your data flows so um what that will likely look like is connectors for example highlighting in green where data has flowed through those so it's a lot easier for you to understand what's happening in your workflow especially as they get more complicated there'll also be a various number of other tweaks that we might demo in a subsequent community meetup here other than that we're working on the record locator component which i'm very excited about so right now in a lot of nodes you just need to define an id let's say in google drive when you're selecting folder you have to go in google drive and figure out that folder with the record locator component you'll be able to traverse tree-like structures like file systems or hierarchies like board and card and checklist like in the trello demo and be able to just drill down point and click and select a record um so that's going to allow you to much more easily find and pick the things like files folders cards without digging around for an id um it's also going to have a buy url mode so you can paste in the url and then we under the hood turn that into an id so that'll be helpful and node's like airtable where right now you have to go around and fiddle around and go find that lastly user management is in progress and we get a lot of inbound requests on this very popular feature request um we're making great progress uh there's a few back-end tickets left and then basically we'll be connecting the front end and back end on that and doing a bunch of testing so i don't have a release date for that but this uh we have a big squad focused on that feature it's uh one of our main priorities and again we're making great progress on that um in closing we're doing a lot more user testing at editing if you're on discord you'll have seen me in there um asking some community members to join it really helps us improve the product it's also a great way to get a sneak peek behind the scenes of what we're working on so if you're interested in helping out with some user testing um make sure to look out for messages from me on discord i'm going to be trying to every week getting some of our community members in there testing some of these new features so we can make sure that they're validated by the time we implement them and lastly as always a massive thanks to everyone on the team and the community who's working to push these features forward and improve naden um i'm truly lucky to have such a great team and community to work with and collaborate with as we build that and roll out these features so thank you everyone thank you so much max for sending this all right perfect thank you max for sharing the updates and this was wonderful and i'm looking forward to using the trigger notes especially because i personally have been waiting for them for a while so it's going to be really exciting again a quick reminder for you all now i am collecting your questions and will be asking them after our next talk so if you have any questions for max don't forget to share them in the chat

moving forward imagine a world where smart devices could be controlled without the internet let's not imagine it let's actually see how jason is building smart devices using inexpensive commonly available hardware that is managed with on-premise n10 thus eliminating the need for an internet connection to run your smart home jason the floor is all yours thanks a lot archon uh so yeah i uh i've been playing around as i tend to with uh various bits of hardware and seeing what we can do with uh any end when we combine them all together um this actually started out in rather an odd way my younger daughter was having difficulty falling asleep and like every good nerd i saw this as an opportunity to build something so i pulled out one of my raspberry pi's and hooked it up to a speaker and had you know in a couple of days built a nice little player for her podcast that didn't didn't require her to actually have to set it all up i could manage it all remotely from my phone but she found that at night if she felt fell asleep she would have missed part of the podcast and wouldn't be able to listen to it and go back so she asked if i could figure out a way to roll it all back and you know i was digging into it and found well sure enough this application has a api built into it so i thought great i can control it with any but i didn't want to give her a whole computer or even a phone to have to work with so i pulled out a wonderful little device and this is called i don't know how well you can see this or not so this is an esp32 microcontroller they're relatively inexpensive you can find them often on places like aliexpress for between five and eight dollars and this is a full-blown computer system it has bluetooth wi-fi um it has uh memory storage you name it it's got all kinds of abilities to build into it i thought that's kind of fun what can we do with that so i actually built a little uh switch into it and threw in a uh a nice little wi-fi connection and got it to send a request out to nan which then would go and it would turn on the her player or depending upon how she touched the button it could roll it back and then it automatically set it to turn off after an hour i thought well if we can do that what else can we do so um i started playing around and looking at this and realized well this is all the stuff that we're talking about with iot the internet of things and i just built out by almost by accident a couple of internet of thing devices that did not require me to have internet connectivity so i took the internet out of the internet of things so when you have devices commonly like this like we all i'm sure have one of these sitting at home plugged that you go and you plug into the side of the wall and you fire up your phone and you often have a qr code on it somewhere or there'll be an id code on the back that you would scan with an app and it asks you to do you know give create an account give out your favorite password that you use for all your other accounts and give them access to basically control hardware within your home um not overly excited about random people from random countries entering my home and doing random things so with some of the devices that i've been playing with now you don't have to do that anymore so i'm going to flip over i'm going to try to flip over to a different camera here we'll see if this works or not it it's got about a 50 success rate and so i may disappear uh but with any luck uh well that's looking good there we go so this is my little device that's set up it looks yeah it looks as scary as it actually is um but this device is now set up to completely run and control um nan um this button here gives me the ability to actually fire off an api call that nan can pick up with the web hook and there is you can see a red light here and beside it there is a blue light that you can't see yet and that is actually can be responded to by any dan so i'm going to share my screen and i'm going to show you a little workflow that i've set up that actually will run i'm actually going to use this one instead and hopefully you can see my see the screen so we've got this workflow set up here's the web hook i promised you and so i'm going to give you guys a bit of a challenge if you can somehow still see my camera where you can see the my device and keep an eye on my on the uh web or workflow that i'm sharing out they kind of have to work together so we'll see if this works or if it doesn't we'll try something else but all i'm going to do is i'm just going to execute the workflow and as you can see it's waiting a typical workflow that's waiting if you can see i'm going to touch the button when i press the button it's going to fire off the workflow and now you see we've got this loop going here i've got an on and off loop so if you take a look back at my camera my camera you will see that there is a blue button that's cycling on and off in time with the workflow it's not that complex it seems like a complicated thing this was about i'd say i put in you know a couple hours a day for about a week to set all this up and it's very relatively simple to work with so this is kind of my proof of concept um and of course i'm never satisfied with just a proof of concept so i've got a roadmap built out of things i want to do so i'm going to actually change uh sharing my screen here and i'm going to flip over to another screen and on that screen there we go so this is the web interface that i'm actually building into that lovely little uh esp32 chip that you were looking at um it's not it's got work that needs to be done on it yet there's still quite a bit to go but so far i've got it set up where it'll pull up the system info so this is again running from a web server built into that chip there's no other web service this isn't on the internet this is completely built into that chip and with that web server it will it'll do api calls out and api calls in so you can send and receive stuff and it's still doing you'll see the chip is still going back and forth um you can also see in the screen i've got so here's your networking info this is all pulled in real time so when i restart the chip and it takes about four seconds for the chip to restart it'll pull all that information in you can then go in and modify your networking information include changing your host name changing your ssid um your nad information so you can change with the address in here you can tell you want to go to your test or your production environment so it will change your web hook url it'll add the test piece onto it automatically um and then the gpios so those are the all the pins on the chip so that you can talk to them uh this is the piece i'm still working on but i'm going to have the ability to build the pick and choose any one of the pins control it and then give it an api endpoint so either it will if it's an input node it will actually create the api endpoint automatically on the chip so that anyone can talk to it or if it's output node it will actually connect to n8n from that api so this is a little bit i have to go yet um i also want to add in a couple more things so for example if the first time you boot it doesn't see um the wi-fi information it'll actually go into a host node so it'll create its own um wi-fi network and you'll be able to connect to it and then do the pre-configuration again without any internet connectivity and it'll be able to fire that up and i've also got and i don't know how well you can it's hard to see even on the camera this little device here so that's actually a screen so it's about a two centimeter screen and on there is a dynamically created qr code that if you take your smartphone and you were to of course i don't have it queued up because why would i have a q-tip that wouldn't make any sense and there we go if you take your favorite barcode scanner and put it over it it'll read the qr code and i don't know if you can see that or not take you straight into the web interface without even having to punch anything in so those are the toys i've been playing around with the things i still have plans to write all this up and i want to make a nice little package for it and when i do get it all done and written up um i'll make it all available on my website and you guys will be able to pull this down and build your own if you want and play around with it and do all kinds of fun things because the wonderful thing about this now is this is kind of the core it's just the base but i can start adding in other things you know like for example i can add in a sonar so that it could detect distance and learn how to follow things i can put in a high voltage relay which will allow it to literally turn on any high voltage device we can start playing around with servos will let us physically control things so we're looking at robotic arms we can start creating and controlling different physical devices that way um you can you know work with it within your home you can turn it in with a temperature sensor turn it into a thermostat that can control different devices control your furnace whichever you like um ir receiver is really good because you can actually could then take this and hijack signals from your remote control and when you go to turn your tv on with the remote control maybe it'll actually catch it and then with any end turn down the lights so there's possibilities with that you know we've got you know a flame control module so you can control your gas fireplace it's really quite endless as to what you can do with some of this stuff now that we've kind of got this interface out into the rest of the physical world and with that i'm going to uh i'm going to stop sharing my screen and i'm going to flip over to my normal camera because everybody needs to be reminded that it is friday and that's why i'm wearing my friday shirt and i'll pass it back over to you herschel

wow okay i'm just still processing all the stuff that i saw and this was amazing jason thank you for sharing it i'm like the possibilities are kind of endless now and i'm sorry folks for asking for recommendations on tv shows and movies i think i know what i'm gonna do this weekend uh but let's move forward and uh move forward because i see a lot of questions coming and a lot of people are now excited about the ideas that you said jason so we have a lot of questions coming in so let me pull up my questions over here all right so the first question is from john and uh it's for you max it's where can he get this light so that is a custom bespoke one-off likes the svg logo is available on our website so i'm sure if you were really uh in the mood you could get your own one made but um noted that they're well liked uh we're currently concepting some rebrands we're likely not going to tackle the logo if we don't maybe harshel you and i have a chat about how we could maybe get a few more of these lights ordered and this could be a sort of uh a treat for certain community members maybe we raffled offers or something if so if you want light up energy and science uh science let us know because maybe we can actually do something about that that's wonderful and talking about the rebranding we have a question on how many colors did you pick um so um likely referencing the brand survey that went out um so we are right now working on potentially rebranding it in um it's something we haven't really invested in a lot since we started out and it's something we're now looking at as we kind of understand who we are collectively and what not um what i can say about that is that we're very much still in concepting phase so nothing's locked in everything's on the table uh the two concepts that you may have seen already were very early stage ones so um we haven't locked in specific colors or concepts or anything so um thank you first off for everyone for your feedback but it's very much still in the brainstorming room bouncing back ideas seeing what's right and likely just like we did now getting some feedback um as those our concepts are shoring up we'll likely also be circulating some surveys and whatnot to get your fantastic opinions as well and makes you said the workflow uh so is it available on the workflows page right now um the workflow that i just showed is not available uh on the workflows page um if someone did want to check it out i could make a note and get it up there by monday if you like um just let me know it is um the most important thing though if you're using the item list node just remember that you need to enter the key name itself and not referenced by expressions wonderful thank you and another question is don't know where to add this but an idea would be to impart previous execution data into the editor so in case the incoming web book or trigger is low and you don't need to do the web who can trigger value by hand yeah so we have a that's a great idea and thankfully what i can say is that's already something that's on our concept board so it won't be one of the immediate things we're tackling next um but we do plan to refactor the no details view so that's the modal view when you're sort of editing a node and as part of that we would like to add basically to all trigger nodes the ability to be able to save to fetch previous execution trigger data and also just arbitrarily paste in um data web hook data for that so it should be a lot easier to sort of simulate and troubleshoot and be testing your workflows and again as that feature is being designed we're going to be really gearing up our user tests and whatnot so you'll have sort of more opportunity to contribute on how that ultimately looks by the time we implement it awesome and can you just repeat again the updates on the google trigger nodes yes sure so um a lot of the google trigger nodes they've kind of been blocked for a while um but we've unblocked basically the technical challenges we had with implementing them and the google tribe trigger node is currently being reviewed so we're polishing it up we're giving it some final tests and hopefully it's going to be going up the ball uh out the door very soon once the google drive trigger node's in place that's going to have unblocked the ability to create the google sheets trigger so is probably the next google trigger that we do just because it is so popular but from there uh it should unblock any of these other google trigger nodes um so on that note if you have a google trigger node that isn't the sheets node um do check the community form and upvote it because now that those are possible we are going to be looking at those and seeing which ones are getting the most up votes to survive to our backlog awesome uh one more question is around the user management uh can we get an update on that um yes so teams hard at work on it um we've got a few back end tickets left the front end for this sort of v1 features is basically done so we'll just have to connect those parts do a lot of testing as you can imagine there's a lot of moving parts in a feature like that and that should be coming out real soon um i think our engineering team would not be very happy if i gave you a hard deadline right now again a lot of moving parts we want to make sure that v1 is high quality when we roll it out but again it's a big priority for us and we're making great progress on it so i hope it's going to be out soon wonderful thank you so much jason i have a question for you since what you showed today does not use internet what do we call it no iot um maybe it's just the um uh jason's network of things j naught i like that awesome uh moving forward let's take a look

at the item list node and learn a few tricks around that so i am gonna start with setting my screen see wonderful i am assuming that you all can see my screen now so with the item list node as uh max already showed you how it works i'm gonna go through uh a deeper example and gonna show you each and every operations in there so the first example is similar to what mac showed so in here i love pokemon so i'm just making a api call to the 4k api if i execute this i am going to get some information okay let's see in the meantime let me take a quick look at the chat right let's stop this reload it again try it once again all right so as you can see now we have we are getting a lot of information like the count the next endpoint that i should call if i want to get the further information the previous end point for this and then the result now i am only interested in the result for this so earlier it was using the function node but with the item list node i can specify that i want the results and if i execute this it just gives me the result so the result now contains the name and the url and it splits them into individual items so now over here we have hundred items and now if i want to process this hundred items i can add another node refer to these values and that particular node is gonna iterate through all these items so this was a small example around the item list node the next is what if we want more information from this so for example if i execute this particular node which gives me some information over here so we have the json information sorry in the json object we get the id and we have the fields which contains the actual information but over here what i am interested in is get the category of all these particular json objects so the first thing i do is i specify which field i want to split so it's gonna be the categories because that's an array so if i execute this i get the all the categories for each of these individual items but i have the categories but i don't know which category belongs to which particular id or which particular object and that's where the selected or the fields or the all other field is helpful let's just take a look at what happens when i select all other fields now if i execute this it includes all the other fields from the previous node as well as it gets us this particular value over here that we have extracted in this node but as mentioned i am just interested in getting the id because i want to map that information in the next part of my workflow so i'm going to select selected other fields and over here i have to specify which field i want maybe let's just do id for now it's gonna be a quicker if i do id now you can see that i have got the json id as well as this so now i have an object that i want and then i can use it later on in my workflow so this was this split with a split out items operation now often times you may want to aggregate all this information that is coming in right we earlier saw that we can split out all this information but what if we want to aggregate and bundle all this information into a single array that's where the aggregate without merge option is really useful so if i now execute this node we see that we have a category array which contains again all the categories now because these were all individual arrays it's now just creating an array of arrays all right uh just taking a look over here at this again now if you have made api calls and if you have taken a look at you know how api sends the response back it's generally not arrays of arrays it's simply a single array of maybe a string or an object so to do that what we can do now over here i have enabled the merge list option so what this will do is this will create a single array of all these options so now if you're making a call to an api if you want to pass on a single array to a particular node this is how you can do it without writing code the next one is kind of really interesting because we also have seen a lot of people doing this you know they want to sort the information coming in maybe in an ascending order descending order and they are not sure how they can do it using the function uh function node and that's where again the item list node is really helpful now over here what i am doing is i am again making a call to the book api extracting the results and now i am selecting the short operation i am sorting this based on the field name and i want to do an ascending order so i selected the odd ascending if i want to do descending i'm going to select descending execute the node and now it does sorting for you so again it's just trying to help you out with you know not getting into the complexity of writing codes and giving you more of a visual cue of how you can do all these operations without code and the last one is around limiting these outputs so you get thousands of outputs from a particular node but in your response you won't only want to send maybe 10 of this incoming information so how can you do that so again the earlier word must you know write some functions and then limit those incoming values but now with the item list node you can limit the number of outputs that you want so over here i just want 10 items from the last right i just want the last 10 items that's why i selected keep if you want the first 10 items we can select first items we can even change this so let's just say we want only five items we execute this it returns only just five items and you can then pass on this information to the next node now over here you can combine all this together so let's just say we sorted shorted this into ascending order and then we want to send the first five so you can have the sort operation and then you can connect the item list node with the limit operation and that's how you can move forward with this so i hope this kind of helps you understand how item list node can be useful now if you have again any feedback or if you want to you know uh let us know uh what kind of operations you think should be added in this you can always uh share it on the community forum and we would be happy to take a look at it and you know try to add more operations to the item list node wonderful so that was me talking about the item list node now moving forward it's time for our

next stop we are we have daniel who is the co-founder and ceo of nirvana technologies and he's going to share with us how they use ntn to unite a user-friendly notion kanban board experience for the team now at the same time how the metrics are generated and represented automatically for the upper management in a bi tool before uh handing it over to daniel a small reminder i am collecting your questions and will be asking them after this talk so if you have any questions don't forget to put them in the chat daniel giving you the permission take it away thank you hershell uh i'm trusting everyone is hearing me well uh it's really a pleasure to be here thank you very much for the n-8 team um i'm gonna share my screen just a second yeah so i have five really quick slides just give context and we'll go right into the workflows um so my name is daniel barrow i'm the ceo and co-founder of navarro tech we're a small startup based in brazil developing financial solutions for the electricity market and basically my life goes around three main things that uh are my main objectives which is nevarra my company i'm also a digital nomad i'm currently living in costa rica until sunday when i'm moving to colombia and i also work a lot on fitness also uh i am a person that has two um strange attributes to be together i am a very ambitious person and i'm also very lazy person and the outcome of those two things the only way they can work together is if you have really good time management optimization um so that's why i built my system for time management also i am not a developer uh i'm kind of excel savvy from working in finance but i am not a full-time developer so basically i built my time management optimization system around four tools which are notion google sheets google calendar and nan and i'm going to show a bit of the workflows that i use to do that but first uh what is a task for me so in notion you can set a lot of different um properties inside of an item this is what a task is for me so as you can see there are a lot of things you can have the day of the week oh my workflows are in portuguese so i'm sorry about that but i think it will be clear for everyone so i have the day of the week i have the date and time that it's actually scheduled if it's professional or personal i have a tag so it could be deep work it could be a personal task it could be all types of things personal or professional if it's recurring and how long does it take in hours because i really like to matrify everything that i do and i'm going to show how i do that in a second uh okay so where did tasks come from and where does any end come into this to this process so i have three main sources of tasks one of them are recurring tasks which are things that i do every week which is like gym meditation aerobics journaling my daily sprint with the team um answering email all types of things that we do regularly that i do every week so i'm gonna have tasks for that every week the second source is google calendar meetings it can be either myself scheduling with someone else or someone else scheduling with me um that could be clients service providers or all types of things and non-recurring tasks which are tested basically i'm talking here to you at a meeting you i have a follow up with you i'll just write them down and allocate them to a specific time um maybe later or maybe on the spot so that could be book my ticket to columbia that could be review marketing's new article or all sorts of things so let's get into it uh my notion dashboard is basically uh allocated between to do monday tuesday wednesday thursday and until sunday uh i've configured it so that i only see what is in my current week i can also see change to see other weeks but it's configured so that i only use the task from the current week and basically i have among those properties they done or discarded so for example i've done my training session today i'll just come here and finalize it i've done journaling i've done my robes i'm currently in the n88 meeting meaning so basically in a month i'll have around 400 cards like these so creating them from zero with all those properties is a lot of work and that's where nadine comes in so i spoke a bit about recurring tasks so i'm going to show that first and for that i use google sheets as my backend i use a lot of that since i don't know how to code and i'm going to show you the workflow that i use for that so basically i have a spreadsheet oh sorry wrong one with all the tasks and they have google sheets formulas where i just change the date of the beginning of the week it will update all of the dates that i can have it correctly for that specific week once i have done that process which really doesn't change a lot from week to week i might add one thing or reduce one thing i will use a very simple workflow just to read the information on google sheets and insert it into my notion database since i have the time as well and i sort it by time it already comes in the order that i'm gonna do them uh so that helps me a lot and the second part is uh the google calendar meetings that show up so for that i have a different workflow which is a bit more complex maybe more complex than it needed to be but basically what i'm doing is i'm kind of doing a polling here i'm every minute checking and getting all of my events in my calendar checking if there's anything new from the last time that we ran it then i'm going to calculate the beginning and the end how long it takes and all sorts of things uh most of these dating times are just date conversions i will check on this function node which day of the week it is and then depending on which day it is i'll use the if statements to place it on the correct uh place so i'm gonna do a quick example here yeah just to show you like test one and while we iterate uh i hit the one minute cron uh i'm going to show you something else so at the end of the day what i do is i have a workflow that every minute or so it's going to take some of my databases from notion and it's going to place it into a google sheets uh that is this dashboard here just a second i need to change this uh so basically it is just gonna throw everyone every data from those databases here so this is my database that i was showing like which is my time management system like my cambium board is going to throw it here i'm going to do a few calculations in my back end and it's going to show up here so basically i can without any work like the only work i have is finalizing the task when it's done or discarding it in case i know i'm not gonna do it at all so like maybe i had to like drink enough water for it today and i didn't do it so i have to it's not something that i can reallocate so i'm just going to discard it and it's going to calculate for me for each tag that i have how much was my target and how much i actually did how much i did in total i can change this to be just recurring or just professional or just one tag and i kind of calculate a few metrics for myself based on that i do pretty much the same thing for fitness this for sure could be done with a postgres database or an sql database that could be on a bi tool that's what we do for like company things but since this was personal i just prefer to have it in a easier in an easier solution so let's go back here and the test that we have is here it was allocated for 4 45 local time in costa rica it has already put it to friday because it detected that was on a friday since it's a meeting in my business calendar it's going to throw it to professional it's going to have the tag meeting and since i only booked half an hour it's going to put here 0. 5 so that's pretty much an overall of my time management system i wanted to make it into a way that it had almost no work but that at the same time it would generate automated metrics so that's pretty much how i follow my schedule and that i can seek to reach my ambitious goals without working too hard i hope you guys liked it um and i'll pass it back to her show

oh daniel thank you so much for sharing that uh we have some questions coming in but once again thank you for sharing that and i have a question before i jump into all the other questions what how are you managing this you know without any tan and what was your process before that so before nadan i actually did this on trello and it was a crazy process so i actually did it i would take like what i did in the day and every end of day i would put it on a spreadsheet with a kpi spreadsheet that i would manually input it so of course it was terrible data and it was a lot of work um and yeah i mostly moved it on i did it on a trello board i didn't like complete a task i just for example meditation i would have it on monday once i did it on monday i would put it on tuesday so it wasn't very efficient it uh and it took and it gave me a lot of work for way worse results than i have right now wonderful thank you for saying that and uh people are asking you know if there are any resources or template about this setup so if someone wants to you know uh try it out for their own use case where can they find it yeah i'm working right now to try to get it uh to be set up for anyone to use uh right now the way i did it in notion is kind of like you have to have made it to understand it um but i'm i'm working on restructuring it so we might have it soon as i have it i'll share it with you and you can feel free to share it awesome thank you so much and there are a couple of questions i think for me but let me check uh uh right okay so thank you daniel once again uh there are a lot of questions for me so i'm gonna address them now uh so there's a question around how hard would it be to structure data flows between nodes based on a specific schema that's a really interesting question and like you can create your own schema but it needs to still follow the unit and structure so you know it should be an array which should contain json objects basically should have the json keyword so if you can do that that's how you can you know then specify your own schema if that answers your question uh because currently it's not gonna it's not possible uh without specifying that and i see another question it says uh for the item list that i showed that some categories are duplicated and maybe add an option to remove them and make them unique yeah so i didn't show the remove duplicate functionality but we do have that so there is an operation that you remove duplicate so if you select that and if you execute it it's gonna remove all the duplicate entries from that item all right uh i'm gonna wait for two more minutes so that other people can ask questions but while we do that i'm gonna talk a bit about the uh breakout the icebreaker that we are gonna have today so now zoom has this amazing feature that's called breakout rooms so we will use these breakout rooms to meet fellow community members and network with them so these rooms are gonna be generated automatically and you will be assigned randomly so this i am not gonna do you know do any kind of shooting trust me on this and once the rooms are created uh zoom will ask you to join that breakout room so there will be a pop-up window on your screen so make sure that you click on join this room and we will have two rounds which will be each of five minutes so uh after for every round i'm gonna share some questions so that you know if you are a bit shy like me you can get started with you know talking around those questions and get to know the community members