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 the environments that I'm managing because I I am an independent consultant and I work with a lot of clients, so a lot of

different environments and a lot of different workflows. And over the years, of course, yeah they have a lot of workflows that that you need to manage, and then you can can get questions for, 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 Naden, 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 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 or something like that of course if you have a small set then it's fine um so you can manage that there. 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 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 and N 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 because I changed something in my environment and I broke all my stuff so that's why it's not all filed um and 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 where they are set so you can change something if if if needed um if you 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 the 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 we are receiving an email from Noden because there was the Noden 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 node so I could at least search for the workflows with that node and 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 [Music] 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 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 or whatever or whenever

something changes um so then there is a 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 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 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 Docker Hub 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 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 SaaS or anything like that that's a good question um it's not going to be a SaaS offering uh it's going to be self-hosted because I think that a lot of people

also use n8n because they can self-host and then it makes no sense to offer it as a SaaS 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 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 sync at that point of course cool thank you yes I'm new into uh n8n uh you exploring the metadata 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 in the future when we're starting to do stuff with n8n 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 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're 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 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 as at some point uh there will also be uh just just the extraction with just the APIs and stuff like that for 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 no there's um you can put as many environments in there as 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 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 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 Postgres 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 it's 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 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 one-time 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 mid-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 just reading the database and I will also uh add some

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 easily move between uh stuff uh those kinds of functions are coming at some point um but what it does it 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 [Applause]

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

3년 동안 Naden과 함께 일한 독립 컨설턴트인 Ram은 다양한 고객을 위해 관리하는 환경과 워크플로우에 대한 더 나은 인사이트가 필요했습니다.

수많은 워크플로 내에서 웹훅과 자격 증명을 찾는 것이 어려웠습니다.

Ram은 처음에는 워크플로와 NX 실행에 중점을 두고 Naden의 데이터를 동기화하는 대시보드를 만들었습니다.

알파 버전에는 커뮤니티 지원용 환경과 데모용 환경의 두 가지 환경이 포함되어 있습니다.

대시보드에는 폴더와 프로젝트가 추가되어 더 많은 수의 워크플로우를 체계적으로 관리할 수 있게 되었습니다.

사용자는 경로별로 웹훅을 보고 검색하여 연결된 워크플로로 연결할 수 있습니다.

자격증명 관리를 통해 워크플로에 사용된 자격 증명을 확인하고 해당 자격 증명의 사용에 연결할 수 있습니다.

검색 기능은 워크플로 설정(실행 순서, 표준 시간대), 노드 및 노드 매개변수까지 확장됩니다.

이메일에 대한 고객의 질문으로 인해 매개변수 검색 기능이 추가되어 특정 매개변수를 사용하는 워크플로우를 식별할 수 있게 되었습니다.

실행 분석은 시간 경과에 따른 워크플로 성능을 표시하여 성공적인 실행과 실패한 실행을 강조 표시합니다.

실행 시간별로 필터링하면 실행 시간이 비정상적으로 긴 워크플로를 식별하는 데 도움이 됩니다.

향후 개발에는 인스턴스를 개요하고 주의가 필요한 영역을 식별하기 위한 대시보드가 포함됩니다.

대시보드는 Docker Hub에서 사용할 수 있으며, 문서와 가격은 아직 결정되지 않았습니다.

애플리케이션은 n8n의 자체 호스팅 기능에 맞춰 SaaS가 아닌 자체 호스팅으로 제공됩니다.

동기화용 이미지와 애플리케이션 자체용 이미지 두 가지로 배포되어 유연한 배포 전략이 가능합니다.

현재 데이터는 쓰기 문제를 방지하기 위해 API를 통하지 않고 데이터베이스에서 직접 읽습니다.

향후 API 통합을 통해 복사 및 자격 증명 변경과 같은 워크플로 수정이 가능해질 예정입니다.

초기에는 자체 호스팅 환경에 중점을 두며, 추후 클라우드 지원 가능성도 있습니다.

여러 환경을 독립적으로 추가하고 동기화할 수 있습니다.

애플리케이션용 이미지와 데이터 동기화용 이미지 두 가지를 사용할 수 있습니다.

설정하려면 Postgres 데이터베이스 연결을 위한 환경 변수를 구성해야 합니다.

동기화 이미지는 특정 환경에 액세스하거나 사용 가능한 환경을 반복할 수 있습니다.

대시보드는 현재 워크플로 계측 없이 n8n 데이터베이스에서 데이터를 읽습니다.

향후 계획에는 실행 내에서 특정 흐름 지점을 검색하는 옵션이 포함될 예정입니다.

워크플로 수정 옵션은 향후 릴리스에서 추가될 예정입니다.

동기화 프로세스는 더 나은 사용성을 위해 데이터를 읽을 뿐만 아니라 처리하기도 합니다.