‘MyMaco n8n Dashboard’ - from the Amsterdam Meetup (November 2024)

so I'm Ram uh I've been working with naden for three years now um and for almost as long I've wanted more insight into uh the the environments that I'm managing because I am an independent consultant and I work with a lot of clients so a lot of different environments and workflows and over the years of course yeah they have a lot of workflows that you need to manage and then you can get questions for example um we see this web Hook is listed somewhere which and inflow is doing something with that good luck finding that with 200 workflows or if you have credentials where are they used um so I created a dashboard We sync all the data from nadn um so the workflow is NX executions this is the first Alpha version so not all the features are actually in there I actually broke a couple of features while I was reworking some stuff if you're a developer you know how that goes um so this is what there is now um this thing has two environments in it already at this moment so it's uh my own environment that I use for all kinds of things mostly um Community uh support where I just created a workflow and do something so I can help someone that's why they are all called my workflow um and one that I created speci specifically for uh this demo so there's two uh environments uh doing different things I added um folders because we all want folders um this also includes the projects which is an Enterprise feature so for example this cats and dogs and super project um those are projects uh but within those um we have folders as well so you can have all kinds of uh folder structures and whatever you want which is quite nice if you have over 50 workflows or or something like that of course if you have a small set then it's fine um so you can manage that there dog yeah uh so for example for the web hooks uh you can just uh look at all the web hooks that are here um there's a little bit of a performance thing that I still need to fix but sure uh you can of course link towards the workflow that has the stuff inside and you can search for the web hook path so for example if some kind of system has web hook listed you can just put in a path and you know exactly um which workflows are actually using that path or at least workflow because of course you can only have one per path if you have it active um same for credentials so you see all the credentials that are listed within my um application or my n andn instance so for example a money bird which is my uh Financial thing you can see all the workflows that I use my money bird node in um there's a bit of funky stuff going on as well because I changed something in my environment and I broke all my stuff so that's why it's not all filed um and you can of course link towards whatever you want and there's also a search where you can search for certain settings so if you have those are workflow settings so for example the execution order or the time zone so you can search where they are set so you can change something if if needed um if you search for a node you can also do that so for example if there's a breaking change with a certain node and a certain node version you can also just do that so for example MySQL so you know there's a breaking change in 2. 1 and you need to update or whatever then you can just search them and find them of course I don't have any of version 2. 1 there we go so there's a couple of flows with that and problem you search it searches across all your instances yes um here you have the option to include all folders uh which is also the instances so a folder is actually also an instance or an instance is also a folder so you could uh all folders or not this thing doesn't actually work at the moment but it needs to be implemented and also include filters that are on the bottom left here there's more to come of course this is something I broke and yeah there's only one filter

left uh so those kinds of things you can all put together and of course you can also just search for all versions um and then you see all the workflows with that node which can be quite handy also if you are searching for a certain node parameter you can just search for that I had a question of a client of mine where they asked like we are receiving an email from naden because there was the naden line under the email but they had no idea which workflow of the 230 workflows was sending that good luck finding that uh at that point I did have the node function to search for a note so I could at least search for the workflows with that Noe and find like 20 workflows where I could just search um but that also gave me the idea to just search for all the parameters so all the parameters are in here uh and you can search them all um you will also get a list of the parameters uh that are actually used and then of course the value which is quite handy of course um and also a nice thing is the executions um this is not fully fledged yet uh because I broke some stuff of course because I do uh but this does help you with finding out uh what's going on U so this is over time so each day what is going on so also if you are successful then you see that there's a lot of uh things of course the successful ones aren't that very useful uh so you go for the field and then you see how many there are failing and also per workflow of course we're also going to add the time and duration of a workflow one of the things I also have from experience is that there is a web hook or a trigger node running which is fired every what is it minute or whatever or whenever something changes um so then there is a long list of executions but there is a filter within that workflow that if something is the case then the workflow is actually executed uh so then you are searching in the list of executions where they are all like 0. 1 second but there's one that's 10 seconds and you want that you can also search for that so you can just search for the duration limit in this case there's only one workflow that actually has any in it of course this data is just demo data and stuff so there's not actually anything uh useful going on so um big bar of 187 that's uh quite a lot but that's because of the demo um but it's easy just to find which workflows those are and you can then just link to the workflow that uh that you're looking for uh also with the date range and stuff like that and of course a lot more to come like the dashboards uh it's great out now because I've not started working on it yet but then you get one overview of all your instances um to know uh where you have to take action for example if stuff is failing or uh something takes more time than on average uh I can put all that stuff in the dashboard and then you can act on that and you have one place to look at that and especially for me as an consultant for a lot of different clients it's nice to have all that in One dashboard and then yeah you only need one place to look which is uh quite handy of course I made it for myself and of course you can also use it um it is actually already live on dockerhub uh so you can install it the documentation is uh not really there um there's a little uh description on how to do it uh it will run for uh the rest of the year uh there is going to be some kind of pricing on it uh not sure yet but the rest of the year you can just use it uh whatever you want um and then uh yeah are there any questions oh there yeah all right yeah so one of the things I was uh wondering about is like and sort of get that from your last sentence like are you planning to offer it as a SAU or anything like that that's a good question um it's not going to be a SAS offering uh it's going to be self-hosted because I think that a lot of people also use naden because they can self-host and then it makes no sense to offer it as a SAS uh so it's all self-hosted it's in two Docker images one for the sync and one for the actual uh application so you could actually uh

for my case and for yours as well have one Central instance and then have a sync uh container on every server of the the clients for example and those push it to your central instance so security wise flexibility wise that's all uh a lot easier to manage that's also why I split them out of course and then you can select which one to syn at that point of course cool thank you yes I'm new into uh n8n uh you exploring the metad data apis is there any limitation when you uh um I'm not exploring any apis at the moment okay uh what I'm doing is I'm reading the database okay um so there will be some apis involved in the future when we're starting to do stuff with naden uh but at this point I'm just reading so I can just read the data and I'm not going to write to the database or at least I'm not planning to cuz that's yeah can cause issues um so the API will be added later uh and then yeah it depends on what the API is able to do uh for the plans I have now the API is fine to do uh what I want to do which is for example copying a workflow changing the credentials stuff like that so basic stuff uh that's already possible so for the private environment but in case your customers are on the hosted environment you also still able yeah so for now it's just for the self-hosted environments because I had to make a choice um I will probably also add something to get Cloud involved in there because of course there are people on the cloud which can use it what I see with my clients is that they are all self-hosted also because I manage their self-hosted service bit of my own fault um but yeah as at some point uh there will also be uh just the extraction with just the apis and stuff like that for also able to um make an interface between different private class of n or is it just one instance one environment where you're are retrieving all the data no no there's um you can put as many environments in there as you want uh I did not show it but here you have it so there's two environments in there right now this of course is not the prettiest screen like all the other stuff uh but there's two environments you can just add the environment as you want and the sync image can be put on the server uh that you're extracting the data from so you can yeah make that uh separate as well any other questions where can people find it yeah here that was a bit slow um so there's two images the base image so without the sync is the most important one this will also do the database migrations database setup for my macro itself the only thing uh that you need to do is uh put in these variables which is basically just a postgress database where you connect to because of course this application also needs a database it's not directly reading from anaden when you are browsing the site so it's all synced um so these are the only environment variables you need uh and you can just run it um and then for the think uh yeah it of course needs to be able to access the server is extracting data for and you can actually uh set a specific environment um so if you have this thing inside a environment uh server cluster or whatever where you have then you can uh sync it from there to a central location if you want and otherwise it will just Loop through all the environments that are available but the documentation will come uh soon is nothing else we have time for another question that's a question for what yeah we can do one more yeah I think you answered a bunch of them here but it's it sounds like and I'm new to nadm so I don't understand the architecture how it's set up it sounds like nadm uses a database to store the workflow designs and running instances and all the onetime data everything and you're just reading that yeah is there anything that you need to do to instrument the workflow design itself like um if you want to do something midf flow raise a flag set a kind of Milestone you have any kind of instrumentation inside the workflow or it's only just reading the database at this point it's and I will also uh add some

database and I will also uh add some options to read specific parts of a database that you can search for a certain uh flow for example if uh if the workflow actually passed a certain point or whatever um but that's also that's just the analysis of the execution then so I'm not injecting anything into the workflow uh there will be some workflow modification options in the future at some point but that's mostly to uh go from Dev to Pro or something like that so you can EAS move between uh stuff uh those kinds of functions are coming at some point um but what it does it syncs the data and it also processes it because the database that nen has um it has all the data but for viewing something like this it's not really that usable directly because it's mostly Big Blocks of text because it's all Json based and of course and then it works very well and very fast and very smooth but if you want to get insight into it then it gets tricky because then you have to analyze data and that part of analyzing it that's what the synchronization is doing and then you have a database that you can actually read and do something with any other all right we other one for more questions let's do it afterwards so we can move on now