Stacktree is an n8n node now.

What shipped

Install n8n-nodes-stacktree (Settings, Community nodes, or search the nodes panel on n8n Cloud) and workflows gain a Stacktree node with two resources. Site covers publish from text or binary, update in place, get the raw HTML back, list, delete, and settings: password, email-domain gate, expiry, burn-after-read, and the on-page feedback toolbar. Feedback reads what viewers annotated on a published page and marks items resolved.

The node is also registered as a tool for n8n's AI Agent workflows, so an agent can publish what it just wrote and pass the link onward without a dedicated node wired in.

Why it exists

n8n workflows end with an artifact surprisingly often: a weekly report, a status dashboard, a generated one-pager for a client. The usual endings are a PDF attachment or a screenshot in Slack, both dead on arrival, or a public page somewhere it should not be. The missing step is a link that renders, stays private, and stays current. Publish once, and next week's run updates the same URL; the bookmark your team made keeps working, and the page it opens is always the latest run.

The loop matters more than the publish. Enable the feedback toolbar and viewers annotate the page in the browser with no account; the workflow reads those comments on its next run, regenerates, updates in place, and resolves them. A review cycle with no meetings in it.

The details that took the time

Passing n8n's review had one instructive wrinkle: their scanner lints the compiled output, not your source, so the usual escape hatches (inline lint suppressions) simply do not exist in what gets scanned. The node hand-builds its multipart uploads against the modern request helpers instead of the deprecated ones, ships no type-declaration files in the package, and publishes with npm provenance from CI. None of that is visible in the workflow editor, which is rather the point.