For n8n + automation
n8n to Public URL in One Step.
Your workflow generates the content. One HTTP Request node POSTs it to Anchorify and gets the published URL back. No Vercel project, no deploy pipeline, no FTP.
What changes when n8n posts straight to a URL
One node, one credential
The HTTP Request node POSTs your content with a Bearer token header. The response includes the published URL. No build step, no deploy wait.
Same URL on every run
POST with the same slug on subsequent runs and the URL stays stable. Your client bookmarks it once; each workflow run updates the content in place.
HTML, markdown, and JSON
Anchorify renders each type correctly. HTML becomes a web page, markdown becomes a styled document, JSON becomes formatted code. Set the filename or the type field.
Analytics and versions included
Every published share gets per-visitor analytics (view count, time-on-doc, scroll depth) and a version history. No extra configuration.
Versus Vercel + GitHub Pages
| Anchorify | Vercel + FTP | |
|---|---|---|
| Nodes to publish | 1 (HTTP Request) | 3-5 (write, trigger, wait, extract) |
| Credentials needed | 1 Bearer token | Deploy token + project config |
| Publish latency | Under 2 seconds | 30-90 seconds |
| URL stable across runs | Yes (same slug) | No (new deploy URL) |
| External infrastructure | None | Vercel project / hosting account |
| Accepts HTML natively | Yes | Yes |
| Accepts markdown natively | Yes | Build step required |
| Built-in analytics | Yes | No |
| Version history | Yes | Via deploy history |
| Cost | Free (beta) | Vercel Pro $20/mo or hosting plan |
FAQ
Can I update the URL in subsequent runs?
Does this work with Make.com or Zapier?
What is the rate limit?
Can I auto-publish HTML or markdown?
Your next n8n report deserves a URL, not a file attachment.
Free during beta. Get your API token from the dashboard and drop in one HTTP Request node.