See llms.txt for all machine-readable content.

Back to Templates

Build a GitHub release digest and publish a one-day BrewPage report

Created by

Created by: Maksim Kochetkov || brewpage
Maksim Kochetkov

Last update

Last update 9 hours ago

Categories

Quick overview

This manual workflow publishes a short HTML or Markdown report to BrewPage as a read-only link that expires after one day, with a safe dry-run mode and validation checks before it sends a single HTTP POST request.

How it works

  1. Starts when you manually execute the workflow.
  2. Loads the report settings (title, content, format, visibility choice, one-day TTL, and dry-run flag).
  3. Validates that the report has a non-empty title and content, the format is HTML or Markdown, and the expiry is exactly 1 day, then prepares the BrewPage API request parameters.
  4. If dry-run is enabled, skips publishing and returns a preview message explaining what must be confirmed for a live run.
  5. If dry-run is disabled and the required acknowledgements are set, sends the report to the BrewPage publish API via an HTTP POST request.
  6. Extracts and validates the returned BrewPage reader link and outputs only the final {url}.

Setup

  1. Update the report title, content, and format (html or markdown) in the workflow inputs.
  2. Run once with dryRun: true to verify the validation and prepared request behavior without sending anything to BrewPage.
  3. For a live publish, set visibility to public or unlisted, set acknowledgeWriteOnce: true, and then set dryRun: false.
  4. Use an n8n instance that allows the Code and HTTP Request nodes to run, and avoid sharing raw execution data because it may include sensitive publish response details.

Requirements

  • Tested with n8n 2.44.7. Uses built-in Code and HTTP Request nodes; no community nodes, AI model, BrewPage account or API key is needed. Live publishing requires outbound HTTPS. Choose public or unlisted access and acknowledge the write-once limit before turning off dry run.

Customization

  • Replace the fictional report title and content, select HTML or Markdown, and choose public or unlisted access. Keep the expiry at one day. Leave dryRun true until you have reviewed the preview and accepted the write-once limit.

Additional info

Write-once limitation: this workflow does not retain owner capabilities, so it cannot update or delete the report. Unlisted links are readable by anyone with the link. The final output contains only the reader URL; do not share raw execution data. The workflow requests a one-day expiry and disables saved manual, success and error execution data. Runtime views can still expose transient response details, so restrict access to your n8n instance.