I would like to know whether the use of an n8n workflow with the free license in self-hosting is possible, or whether it is prohibited under the SUL:
We host n8n ourselves.
We have a workflow that receives data from our self-developed application (user data) via an API, processes this data in the workflow, and then returns the result to the application via the API.
The user does not see the API. It is integrated into the application.
The workflow processes user data via API from the application in the background.
Because the user does not directly log into or interact with n8n, and you treat n8n as a backend engine within your system, this leans strongly toward “internal tool / internal business use” of the free license. That is permitted.
You are not offering n8n as a platform to your users (i.e., you’re not charging them for access to configure workflows themselves via the n8n UI). That aligns with permitted use.
You are processing user data for your own service (your application) rather than providing n8n as the service itself. This also appears to fit the “allowed” case
So in sum: yes, I believe your described setup should be permitted under the free/SUL licence of n8n - because you are using it as part of your service’s backend for your own users, not as a workflow-platform you sell access to.
Thank you for this information.
It is correct that the user never sees n8n—they don’t even know that n8n is working behind the API of our application.