Run n8n workflows with GitHub Actions

um so for this ac mission uh what me and jan thought of is making something very simple yet very useful for nitin um so after a bit of research uh what we come up is like to automate the process of creating linear tickets whenever a pr is made so uh for this uh what we use is just the google github actions and the engine so the the process how it works is whenever apr is made uh the new nitin instance is triggered using the github actions within the github infrastructure and where we have written a workflow um to create a linear ticket and also uh to intimidate that in the mattermost channel uh i'll i would like jan to continue and give an in-depth presentation along with the demo perfect thank you very much um like one of the important pieces uh there is like that the workflows don't run on a normal ended infrastructure like it runs in github actions and the question why that's important and what makes it quite that special um the great thing is like it literally runs on github so you don't need an own an instance it cannot be down it can there could have been any connection problems there could not be too many requests it's free to run the it also enables that the data lives where it should live so the workflow that runs every time for example you open a pull request that workflow is living on github and the workflow that's there and version gets used so you also have access to all the files on github and we can use them and for example also helpful for the testing workflows omar created we can actually use the github action um to do that so i can try if i have some more luck with sharing because i'm obviously also on linux um so let's see um if that works is everything right or is it actually working yeah it's very good nice cool okay so how that works like we have this um where are we actually um okay we have this is the repository that actually contains the all the github action code that you can run and then and on github actions and also the workflows um to give one part was obviously creating that workflows the other part was making it possible and can work on github actions and the third part was to make it easy for people to do that so how that's done is like you can go in this github action repository you can say run ended n um and then it will start and at n the important part here is that it imports on startup all the credentials we have in this repository and all the workflows so now you can go into n and we have all the workflows available here so you can for example see i have two currently named the same so i go into one of them and call it edit and new so let's get now saved if i now stop edit n it will export the workflows on stopping and you will see that if you actually so get status you see the reflection updated so if you say get stiff you will see that it now updated the name so you can now update commit this one to to github so if you now for example say we do that you get status actually get at the push that one here get push actually i have to do it from somewhere else go ahead and see it and get a nice good push it will now start this github action here you will see it is running actually it should be running get push ah git commit sorry whatever so now it starts at workflow and while we do run it starting we do we also open a pr so they i also have here we open a new pr um we do this one when it restarts open spi it opens another starts another github action both to different things the first one on push we have one github action setup this is the main one that starts workflow number one workflow one simply will push um publish a github message workflow number three which gets executed uh on push will actually uh do exactly what uh what kojic just described before so once it's done you will see it will check out in it and it will get all the information and then run the

workflow and if it's all done it would actually publish that message you see here and then it says the first one that runs through it said push to github and as soon as the second one did run through you will what you will see that it created a message an issue on linear and it will also publish a message to metamorse now you will see it here and you will see that if you look all you see actually it was already there i don't uh sorry you will see here is just this new github issues and it's all that run all on the github infrastructure and yeah that can be reused for many different things in a sense it was important that people that the main reason to do that is like for example we have this test workflow so i have the and release workflow that also runs locally and all of this code is running on a different infrastructure and especially safe somewhere else and like this you really have always the credentials and the workflows where they should be and obviously the credentials are still encrypted and everything works like it should work so hope i'm in time