Block 1 - Create Gist
- Type / Role
- n8n-nodes-base.httpRequest - httpRequest
- Config choices
- Version 4.2
This workflow is provided as-is. Please review and test before using in production.
Who’s it for This subworkflow is designed for developers, AI engineers, or automation builders who generate dynamic HTML content in their workflows (e.g. reports, dashboards, emails) and want a ...
n8n-nodes-base.httprequest, n8n-nodes-base.executeworkflowtrigger, n8n-nodes-base.set, n8n-nodes-base.stickynote
This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by Open Paws.
Original n8n.io sourceThis subworkflow is designed for developers, AI engineers, or automation builders who generate dynamic HTML content in their workflows (e.g. reports, dashboards, emails) and want a simple way to host and share it via a clean URL, without spinning up infrastructure or uploading to a CMS.
It’s especially useful when combined with AI agents that generate HTML content as part of a larger automated pipeline.
This subworkflow:
The result is a lightweight, fast, and free way to publish AI-generated HTML (such as reports, articles, or formatted data outputs) to the web.
html input parameter.gist scope.gist permissionsreport.html) if your use case needs a different format or extension.This catalog entry is organized from the workflow JSON. The node-level section below shows the executable blocks available for review before importing the template.
| Workflow | Publish HTML content with GitHub Gist and HTML preview |
|---|---|
| Complexity | beginner |
| Nodes | 4 |
| Categories | File Management |
| Author | Open Paws |
| Published | 30 Jul 2025 |
Use the JSON export at /data/workflows/6674/6674.json as the source template for this automation.
Open n8n, import the downloaded JSON, and review each node before activating the workflow.
Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.
Run the workflow manually or in a staging workspace, inspect node output, and confirm downstream systems receive the expected data.
Enable the workflow only after testing, then monitor executions, errors, and rate limits during the first production runs.
Review imported nodes carefully before activation. This catalog entry is intended to help you inspect the workflow structure, understand required services, and find related templates faster.
Node names, credentials, schedules, webhook paths, and external service limits may need adjustment for your workspace.
Who’s it for This subworkflow is designed for developers, AI engineers, or automation builders who generate dynamic HTML content in their workflows (e.g. reports, dashboards, emails) and want a ...
Review the workflow JSON, configure any required credentials in n8n, and test the automation in a safe workspace before using it in production.
Yes. Use the block-by-block analysis and the downloadable JSON to inspect each node, then adjust credentials, prompts, schedules, filters, or destinations for your File Management use case.