# n8n Advanced Course (8/8) - Enterprise features

## Метаданные

- **Канал:** n8n
- **YouTube:** https://www.youtube.com/watch?v=fXEubzmVJ_E
- **Дата:** 20.06.2024
- **Длительность:** 12:07
- **Просмотры:** 22,953
- **Источник:** https://ekstraktznaniy.ru/video/15639

## Описание

⌨ Sign up to n8n Cloud for a free trial: https://app.n8n.cloud/register

Or:

npm install -g n8n
n8n start

*Resources:*

❔ Need help or want to discuss the course? Join the conversation on our forum: https://community.n8n.io/t/advanced-course-8-8-enterprise-features/48617

🛠 Workflow templates: https://n8n.io/workflows/

📚 Documentation: https://docs.n8n.io/

## Транскрипт

### Introduction []

hey and welcome to video number eight of the advanced course for NN in this video we'll be covering some Enterprise features that'll really help you with more advanced workflow

### User management [0:12]

building the first very useful feature um we're going to talk about in the Enterprise set is having different kinds of access that are available to users and starting in this case with user management there are three typ types of levels of users owner admin and member these users will have different access levels when it comes to workflows or credentials to ensure that no one has unwanted access to any of the workflows in your anend instance um but also to API Keys credentials or any other tools there's only one owner for every nend in they have all of the rights listed below adding removing users seeing and sharing workflows credentials but also setting up and using Source control what's important to note is you cannot transfer ownership of an ENT instance it is also important to note that even though they have access to all the credential information they can't actually read the sensitive information itself so they will be able to use and share credentials but not access the underlying API key or other information admins are like owners except that they can't access the dashboard or manage the owner role whereas members are just your run-ofthe-mill normal nidn users and can manage their own accounts and

### Execution data [1:56]

workflows the second feature we will cover is saving execution data making it a lot easier to find executions that deal with certain information this avoids you having to search through hundreds or thousands of executions one by one to find a specific execution the execution data node lets you save fields or values that you want to use later to easily find an execution for example an order ID or a user ID you will be able to search data by this key and value in your executions tab we'll see in a second for example here the input data of the execution data node includes an order ID I can save this ID to make it easily searchable later from the execution history tab you can filter by key and value here for example we search for executions where the order ID was equal to the one from the previous example when working with orders transactions products or any other type of object that has an ID consider saving them to make them more easily

### Git Source Control [3:23]

searchable Nidan uses git based Source control to support environments linking your NN instance to a git repository lets you create multiple NN environments backed by git branches kit is a virsion Control software and NN environments let you control Version Control your nent instance using git there are different advantages to having more than one environment a common pattern is to have different environments for both development work and production development is where we do work and make changes or test updates to workflows and production is going to be our live environment that the business depends on a setup like this helps you make changes to workflows without breaking workflows that are already in use this will come in very handy especially if you have business critical workflows you can find a full guide on how to Version Control your niden instance in the niden documentation under Source control environments This is highly recommended for any NN instance that runs workflows that the business depends on for example customer facing automations or anything that might have to uh deal with inventory or stock that would directly impact the business should they start failing due to an update

### Custom Variables [5:01]

custom variables are readon and can be used to store and reuse values across workflows they can be used to store commonly used information such as IP addresses URLs Etc on a per environment basis for the whole team to reference more easily variables can be configured by environment and this is important to note let's say you have a variable with name database in both production and development environments the value is set to the dev database path in the dev environment and the production production environment then you can run the identical workflow referencing the variable name database and it will read SLR to a different database as defined in each instance this means no more pushing to production and then realizing you forgot to change the name of your variable you can create a new variable from the variables Page by signing it a key value pair keys are under 50 characters and values under 220 you can then access the value of the variable using dollars VAR in the expressions or in the code node as we see below here I wrote dollars vs. company Tax ID and I was able to read the uh environment

### External Secrets [6:40]

variable you can also use an external Secrets store to manage credentials for aniden stores all of your credentials encrypted in its database and restricts access to them by default but with the external Secrets feature you can store sensitive credential information in an external Vault and have in then loaded only when required this provides an extra layer of security and allows you to manage credentials used across multiple NN environments in one central place you can use external secrets with any environments to create different environments backed by git the feature doesn't support using different credentials in different instances but you can use an external Secrets Vault to provide different credentials for different environments by connecting each inent instance to a different Vault or project environment for example you can have two Inn instances one for development and one for production as mentioned earlier and use Hashi Corp vault in Hashi Corp create a project with two environments one for development and one for production by generating a to token for each hashy Corp environment you can use the token for the development environment to connect your development and instance and the token for your production environment to connect with your production inent

### Log Streaming [8:12]

instance another very useful uh Enterprise feature is log streaming allows you to send events from Inn to your own logging tools this allows you to manage your nen monitoring in your own alerting and logging processes from the settings you can access the log streaming tab when you create a new event destination you start by selecting the type of destination is it web hook or Sentry or CIS log for example then you can set up all the information necessary for the given destination in the case of web hooks we would have the method URL and we also have options to add query parameters headers and additional options for redirects proxy timeouts Etc from here we can select the types of events that we want to stream to the destination there are events related to AI workflows audit node executions um audit events can also be anonymized and these can all be found from here we can select the type of event that we want to stream to that destination there are events related to audits they can be anonymized AI workflows node executions Etc audit events are going to be useful for compliance regulations you can find a lot more information about log streaming in the nland documentation linked below so to illustrate um execution data saving uh here I have a pretty simple workflow that listens for web hooks on a URL and returns information such as the order ID the order name customer ID customer email Etc from here the workflow sends a slack message for reporting purposes and depending on the state of the workflow is going to add it to Google Sheets or insert a line into the SQL database if we have hundreds or thousands of executions coming in per day it can be difficult to find a specific execution so what we can do here is add the execution data node and drag in a new saved field so here this could be for example the order ID and I can drag this in so when I execute this node it will save the order ID and associate to this execution which means that if I then want to go into the execution log I can now filter by order ID and match it up with I think it was 5 4 32 no and match it up with uh the order ID which was 53452 and here we can see this was executed today meaning it's very easy for me to go back and find this uh execution for the other Enterprise features most of them can be found in the uh settings panel so here you're going to find information about users or um log streaming environments external secrets and here in the tab to the left you can find variables if you want to add new variables uh and use them uh per environment in your instance thanks for listening to the eth video of the niden advanced course where we covered the niden Enterprise features