n8n
Create automations — and how this relates to real n8n behind the scenes.
The page “n8n Automation Guide - Create Your Automations” covers the function identified by this URL. The existing summary is expanded with the actual workflow, prerequisites and known limitations. The tenant interface is a simplified proprietary rule engine with four trigger types. It is not the full n8n editor. The actual n8n editor is accessible only in Master Admin.
The tenant Automation area is a simplified proprietary rule engine with four trigger types. It is not the full n8n editor, which remains restricted to Master Admin.
A rule combines a trigger, conditions and an action. Define a controlled test prior to activation. The Runs tab shows executions but has no retry button.
The `automation_n8n` add-on costs EUR 29 per month and may be activated automatically. The tenant interface nevertheless remains the simplified rule editor.
For a failed run, record rule name, trigger, time and status. Correct the cause and generate a new normal trigger instead of repeatedly forcing the same event.
For “n8n Automation Guide - Create Your Automations”, the expanded text must remain specific to https://zentor-app.de/en/hilfe/n8n, use only verified facts and clearly separate tenant self-service from actions performed by Zentor. Any support case is best advised to identify this exact page, the active tenant and the observed step without disclosing credentials.
This page also explains its role within the Help Center, from the first check to the expected result, while naming verified limitations and the relevant detailed area. Statements that are not supported for https://zentor-app.de/en/hilfe/n8n are not added. The expansion is therefore substantial without importing unrelated features or repeating generic filler.
When using “n8n Automation Guide - Create Your Automations”, test one controlled scenario at a time and compare the visible setting, the actual system status and the expected result. If the outcome differs, record the exact time, tenant, channel and unchanged error message. Screenshots and support notes must exclude passwords, tokens and unnecessary personal data so that troubleshooting remains both useful and safe.