Description

BrewPage for n8n

n8n community node for BrewPage. Other BrewPage integrations:
BrewPage publishing plugins.

Publish HTML and Markdown reports as temporary HTTPS reader links. No signup,
credentials or API key. The node installs no runtime dependency; its only peer
is n8n-workflow, which the n8n host provides. This package is an unverified
self-hosted community node, separate from the existing BrewPage workflow
template.

Use

On self-hosted n8n, install n8n-nodes-brewpage through **Settings →
Community nodes** and accept the native unverified-code
notice. Add BrewPage, choose Publish Report, select HTML or Markdown,
and map Content from a previous node, for example ={{ $json.report }}.
Choose Access explicitly and set Lifetime from 1 to 30 days (default 15).
Content must be nonempty and at most 5 MiB in UTF-8.
Content, Format and Access expressions must return strings; structured values
are rejected before any request.

• Unlisted: anyone with the link can read it. It is not private.
• Public: discoverable in the gallery; anyone can read it.
• Content expires permanently. Identical existing content may retain its original

expiry; check the returned expiresAt and reusedExisting.

• Output contains only link, access, format, expiresAt,

requestedTtlDays, and reusedExisting. Owner tokens, management links,
response bodies and input content are discarded from node output.

• link is the reader address BrewPage returned: https://brewpage.app//

or the page’s own host https://.brewpage.app/ (HTML in the unlisted
namespace). A successful create is never reported as a failure.

• Ownership tokens are deliberately discarded: this node cannot update or delete

a publication. Do not publish material that needs early deletion.

• Publish only reports intended for sharing. Do not include secrets or personal

data. This node has no password option.

Before using report inputs, disable workflow execution saving for success,
errors, progress and manual runs, and do not pin data. n8n itself can persist
workflow parameters, input data, execution snapshots and logs. This package
cannot override instance administration, upstream nodes, telemetry or logging;
keep report content out of literal node parameters and persistent upstream data.
Credential/response redaction in this node does not guarantee platform-wide
secrecy.

The only network destination is https://brewpage.app/api/html. Requests send
User-Agent: brewpage-n8n/0.1.4 (+https://brewpage.app). Redirects are disabled.
Every failure throws an n8n NodeOperationError with one fixed message and no
original error or response; there is no automatic retry, because a timed-out
publication may already exist.
Requests time out after 60 seconds and decoded responses are capped at 64 KiB.

Development

The repository follows the layout of n8n’s
starter template: package.json,
nodes/ and the build config live at the root. The node has no credentials.
Use Node.js 24 and npm 11:

npm ci --ignore-scripts
npm run format
npm run lint
npm run build
npm test
npm run test:native   # Docker: runs the built node inside n8n 2.44.7

Development pins: @n8n/node-cli 0.55.5, n8n-workflow 2.44.2 (the host
supplies it at runtime), TypeScript 5.9.3, Prettier 3.9.10.

Host dependency advisory

The tested n8n 2.44.7 host’s SDK includes Zod 3.25.76, affected by
GHSA-mrhx-c7xc-m3w5
(memory exhaustion from oversized constrained collections). The published fix is
Zod 4.6.6; replacing the host’s 3.x API with that major version has not been
qualified. The compiled node loads n8n-workflow from the host as a peer, for
NodeOperationError and NodeConnectionTypes, and installs no dependency of its
own. It adds no dependency graph; it does not repair an existing host. The
node’s input limits do not establish host-wide immunity.

Publication and provenance

Releases are published only by GitHub Actions. Pushing a vX.Y.Z tag that
matches package.json runs publish.yml:
format, unit and native checks, then npm run release, which lints, builds and
publishes with an npm provenance statement through npm trusted publishing
(GitHub OIDC). No registry token is stored in the repository. Verify a release
with npm audit signatures or on the package’s npm page.

Versions up to 0.1.3 were published from
brewpage-publish-plugins;
this repository carries their history.

Official guidance:
node CLI,
verification,
submission,
self-hosted installation,
BrewPage API.

Related

All BrewPage integrations ·
BrewPage ·
MCP server ·
Cookbook