# Stacktree is an n8n node now

Source: https://stacktr.ee/blog/stacktree-n8n-node

[Skip to content](#main) [Stacktree](/)[Developers](/developers)[Agents](/agents)[Docs](/docs)[Use cases](/use-cases)[Pricing](/pricing)[Blog](/blog)[Dashboard](https://app.stacktr.ee)[Sign in →](https://app.stacktr.ee)      By [ Steve Smith ](/about) · Founder, Stacktree  ·  Last updated July 28, 2026          blog

#  Stacktree is an n8n node now.

   n8n-nodes-stacktree is live in the community registry after passing n8n's security review. Any workflow gets a publish step: HTML in, a private unguessable link out, updated in place on the same URL for as long as the workflow keeps running.

  [ Get started free ](https://app.stacktr.ee/?join=1&from=seo_blog_stacktree_n8n_node)   install npx stacktree-install
Copy
     No card · 3 pages free · about a minute

## 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.

     See it in one call, no account

```
`curl -X POST https://api.stacktr.ee/sites -F file=@index.html
# &rarr; a private URL, live for 24h. Claim it free to keep it.`
```

If your agents emit HTML, they need a durable publish target: publish once, then
`update_site`
on every revision keeps the same URL forever. MCP, REST, and skills all speak it:
        the map is at [agent.txt](https://stacktr.ee/agent.txt).

[
Get an API key free
](https://app.stacktr.ee/?join=1&from=bridge_blog_stacktree_n8n_node)
FAQ

## Frequent questions

     What is n8n-nodes-stacktree? +  A community node for n8n that gives workflows a publish step: HTML in, private unguessable stacktr.ee link out. Two resources (Site and Feedback), nine operations mirroring the Stacktree MCP server: publish, update in place, get, list, delete, settings (password, email gate, expiry, feedback toolbar), and reading or resolving viewer feedback.   Does it run on n8n Cloud? +  Yes. The node passed n8n's security review, which is the requirement for community nodes to be installable on n8n Cloud. Self-hosted installs work from Settings, Community nodes, with the package name.   Can an n8n AI Agent use it as a tool? +  Yes, it is registered as usable-as-tool. An AI Agent node can decide to publish the HTML it just produced, get the private link back, and hand it to the next step without a hard-wired node in between.   Why not just use the HTTP Request node? +  You can; the API is open. The node handles multipart uploads from text or binary data, ships a credential test, applies sensible defaults for expiry and the PII pre-flight scan, and exposes typed operations that agents and teammates can read at a glance.
Keep reading

## Related guides

   -  [ Publish HTML from n8n The integration page: install, operations, and the weekly-report pattern. ](/n8n)
-  [ Host AI reports The report-publishing job the node automates. ](/host-ai-reports)
-  [ Client feedback loop On-page comments your workflow can read and resolve. ](/client-feedback-loop)
-  [ The MCP publish tool The same operations, exposed to MCP agents. ](/mcp-publish-html)

References

## Sources and further reading

   -  [ n8n-nodes-stacktree on npm ↗ The published package, with npm provenance. ](https://www.npmjs.com/package/n8n-nodes-stacktree)
-  [ stacktree-n8n on GitHub ↗ Source: two resources, nine operations, MIT. ](https://github.com/stevysmith/stacktree-n8n)
-  [ n8n docs: community nodes ↗ How community nodes install, self-hosted and Cloud. ](https://docs.n8n.io/integrations/community-nodes/installation/)

##  Give your workflows a publish step.

 Install n8n-nodes-stacktree. HTML in, private link out.

 [
Sign up free →
](https://app.stacktr.ee/?join=1&from=cta_blog_stacktree_n8n_node)   install npx stacktree-install
Copy
       Private hosting for the HTML your agents make.

[](https://betalist.com/startups/stacktree?utm_campaign=badge-stacktree&utm_medium=badge&utm_source=badge-featured)[Featured on](https://devhunt.org/tool/stacktree)[](https://buildlist.io)[Get started free](https://app.stacktr.ee/?join=1)

## Product

- [Example deliverables](/examples)
- [Custom domains](/custom-domains)
- [Client feedback](/client-feedback-loop)
- [One-time links](/one-time-view-links)
- [See how pages get read](/page-engagement)
- [Made with Stacktree](/made-with)
- [Security](/security)
- [Watch the demo](/demo)

## Agents

- [All integrations](/agents)
- [Claude Code](/claude-code)
- [OpenAI Codex](/codex)
- [Cursor](/cursor)
- [Claude.ai connector](/claude-ai-connector)
- [MCP server](/mcp-publish-html)
- [Deploy from Claude Code](/deploy-html-from-claude-code)
- [Skills](/skills)
- [Slack app](/slack)
- [n8n node](/n8n)
- [Agent payments (x402)](/x402)

## Alternatives

- [All comparisons](/alternatives)
- [Head-to-head comparisons](/compare)
- [Tiiny Host](/tiiny-host-alternative)
- [GitHub Pages (private)](/github-pages-private-alternative)
- [Vercel](/vercel-alternative-for-agents)
- [ngrok](/ngrok-alternative-for-html)
- [Display.dev](/display-dev-alternative)
- [Static.app](/static-app-alternative)
- [OpenAI Codex Sites](/openai-codex-sites-alternative)
- [here.now](/here-now-alternative)
- [Shippage](/shippage-ai-alternative)
- [Best private hosting](/best-private-html-hosting)

## Use cases

- [All use cases](/use-cases)
- [Share with clients](/share-with-clients)
- [Send a file to a client](/share-html-file-with-client)
- [Share Claude artifacts](/share-claude-artifacts)
- [Share Jupyter notebooks](/share-jupyter-notebook-html)
- [Host Storybook privately](/host-storybook-privately)
- [Architecture diagrams](/share-architecture-diagrams)
- [AI-generated reports](/host-ai-reports)
- [Internal HTML tools](/internal-tool-hosting)
- [Private HTML hosting](/private-html-hosting)
- [Vibe-coded page hosting](/vibe-coding-hosting)
- [Leave a website builder](/website-builder-migration)

## Learn

- [Blog](/blog)
- [Glossary](/glossary)
- [FAQ](/faq)
- [Agent-loop hosting](/agent-loop-hosting)
- [Why agents need a publish primitive](/blog/why-agents-need-a-publish-primitive)
- [MCP servers explained](/blog/mcp-servers-explained-for-developers)
- [What changed in the 2026-07 MCP spec](/blog/mcp-2026-spec-changes)
- [Sites in Codex explained](/blog/sites-in-codex-explained)
- [Private-by-default hosting](/blog/private-by-default-html-hosting)
- [An agent paid us $1 (x402)](/blog/agent-paid-to-provision-itself)
- [When a loop hits a paywall](/blog/loop-engineering-paywall)
- [Pricing](/pricing)
- [Self-host (new)](/self-host)
- [Changelog](/changelog)
- [Docs](https://stacktr.ee/docs)
- [About](/about)
© 2026 Stacktree · stacktr.ee

[Privacy](/privacy)[Terms](/terms)[Security](/security)[Dashboard](https://app.stacktr.ee)[npm](https://www.npmjs.com/package/stacktree-mcp)[Sitemap](/sitemap.xml)[llms.txt](/llms.txt)[API spec](/openapi.json)

---
Full markdown summary of the Stacktree marketing surface: https://stacktr.ee/llms-full.txt
