Eternet Portal Documentation
Workflows / n8n
How it works
The portal embeds the configured n8n URL in an iframe. The portal page is a navigation and embedding boundary; workflow authoring, execution history, credentials, and runtime are provided by n8n itself.
Security boundary
The portal deliberately does not place an OIDC access token in the browser URL. Availability and sign-in behavior depend on the configured n8n deployment and its own access controls.
What the embedded workflow experience does
The Workflows / n8n page is an authenticated entry point that embeds the configured n8n environment inside the portal. The source URL comes from the server’s N8N_URL configuration, with a default external n8n host if no override is set. The portal intentionally avoids putting an OIDC access token in the iframe URL. Once loaded, n8n provides its own workflow canvas and runtime features, such as editing nodes, arranging steps, configuring credentials, and viewing execution history, subject to the n8n deployment and the user’s n8n permissions.
This architecture keeps workflow execution outside the portal’s application server. The portal provides navigation and an embedding context, while n8n owns workflow definitions, scheduling, execution, secrets, retries, and operational logs. Integrations may call Eternet APIs or external systems, but the exact behavior is defined by each workflow and its credentials. A workflow visible in the n8n editor is not evidence that it has been activated or has successfully completed a recent run.
Security, availability, and support
Because the page is an iframe, browser framing rules, content security policy, cookies, and the n8n login configuration all influence whether it loads correctly. Authentication to the portal does not automatically guarantee an authenticated n8n session. The two systems may use separate identity configuration. Administrators should confirm that the trusted origin is configured, that n8n does not allow unauthorized framing, and that the user sees only workflows permitted by the n8n account. Credentials should remain stored in n8n’s credential facility rather than pasted into portal URLs or product documents.
When a workflow fails, inspect the n8n execution record and node-specific error details. The portal may not proxy or summarize those logs. For support, capture the workflow identifier, execution timestamp, and sanitized error message, but do not share secrets or payloads containing personal data. If the iframe is blank, distinguish a portal routing issue from a browser frame block, a network problem, or an n8n sign-in failure.
Customer value and presentation boundary
Embedding n8n makes it convenient to move from monitoring to process automation within the same portal navigation. Teams can orchestrate notifications, integrations, and recurring tasks without treating the portal as the workflow engine. In a customer demo, show a workflow only after confirming its owner, activation state, credentials, and latest execution. Explain that workflow behavior is configurable and customer-specific; the portal does not provide a universal automation recipe. Eternet Portal handles the access point, while n8n and its connected services remain responsible for the actual automation lifecycle.