Overview
Customer experienceN8Forge gives you a managed n8n workspace rather than a raw server. Most day-to-day tasks happen from the product dashboards instead of directly through infrastructure tools.
- Your workspace is tied to a tenant record created when you subscribe or onboard. You may have multiple workspaces if you manage separate environments.
- Your runtime (the n8n container) may take a short time to become ready because provisioning runs as background jobs — check the status card to confirm.
- Launching the workspace takes you into the managed n8n editor via SSO. No separate login or password is needed beyond your platform credentials.
Dashboards
Where to do whatUse this for workspace-level management such as domains, provisioning activity, and account-facing controls.
Use this for launch URLs, managed instance visibility, and template installs into your selected workspace.
If the action changes how you access the workspace, start in the SaaSForge dashboard. If the action changes what is inside the n8n workspace, start in the N8NForge dashboard.
Getting to your workspace
Launch flow- Sign in through the normal platform or partner-branded auth flow using your email and password.
- Open your dashboard — the workspace overview page shows your current workspace and provisioning status at a glance.
- Check provisioning status on the overview card. If it shows "succeeded", your runtime is ready. "Running" or "queued" means setup is still in progress.
- Launch the workspace from the N8NForge dashboard by clicking the "Open" button next to your instance. This opens the managed n8n editor via SSO — no separate credentials needed.
If the launch URL is missing, loops, or fails to load, check recent provisioning activity first. If the runtime still does not open, contact support or your partner.
Custom domains
Workspace access- Add a custom domain from the SaaSForge dashboard to attach branded access to your workspace.
- Select the target instance when adding a domain so it routes to the correct runtime.
- Expect propagation time if DNS changes are required before the domain starts serving traffic.
- Know the boundary: the dashboard records the domain and triggers domain sync, but DNS, SSL, and reverse-proxy routing are managed by the platform admin.
If DNS looks correct but the workspace domain still does not open, the issue may be SSL, proxy, or runtime routing and usually needs admin intervention.
Templates
Starter workflows- Template catalog is available from the N8NForge dashboard — browse by category, search by name, or filter by status.
- Installs are tracked in real time. The catalog card updates from "Install" to "Queued" to "Installed" as the scheduler processes the request.
- Featured templates may appear automatically for new workspaces when enabled by the platform.
- Quick search in the catalog header lets you filter templates without reloading the page.
Template installs run asynchronously. A queued state usually means the scheduler has not yet processed the request.
Metrics and history
InsightsThe N8NForge dashboard shows live runtime stats and historical trends for your workspace. Data refreshes automatically every 30 seconds.
- Stat cards at the top show active workflows, total executions, error count, and success rate (color-coded green / amber / red).
- Instance summary on the right panel shows memory, CPU, event loop lag, heap usage, open file descriptors, and the n8n version.
- History bars below the stat cards chart memory and event loop trends over recent data points — hover each bar for the exact value.
- Status badges on the template cards and activity list update in real time as installs and provisioning jobs progress.
- Metrics are collected automatically — no action needed on your part.
Provisioning activity
Status and history- Provisioning activity shows recent lifecycle jobs such as deploys, domain syncs, restarts, and suspends. Each entry includes the job type, status, and timestamp.
- Normal statuses include queued, running, succeeded, failed, and suspended. A succeeded job means the action completed — your workspace should reflect the change.
- Recent changes such as a subscription update, custom domain addition, or admin action may create new provisioning entries automatically.
- Multiple entries for the same action can appear if a previous job failed and was retried — the latest entry reflects the current state.
If a job stays failed or queued for too long, contact support. Customers cannot directly run low-level restart, redeploy, or infrastructure repair actions.
What support handles
Responsibility boundaries| You can do | Support or admin handles |
|---|---|
| Review activity, set a workspace domain, launch the workspace, install templates, and manage normal workspace-facing usage | Fix provisioning failures, change runtime hosts, enable external infrastructure, run backups, restart or redeploy the runtime, and repair platform-level domain routing |
When reporting a problem, include the workspace name, custom domain if relevant, the latest provisioning status you see, and what action you were trying to take.