Block 1 - Hook: Get Items
- Type / Role
- n8n-nodes-base.webhook - webhook
- Config choices
- Version 2
This workflow is provided as-is. Please review and test before using in production.
Build a Redis Powered CRUD App with HTML Frontend  application without relying on any external server or hosting. It not only acts as the backend, handling all CRUD operations through Webhook endpoints, but also serves a fully functional HTML Single Page Application (SPA) directly via a webhook response.
Redis is used as a lightweight data store, providing fast and simple key-value storage with auto-incremented IDs. Because both the frontend (HTML app) and backend (API endpoints) are managed entirely within a single n8n workflow, you can quickly prototype or deploy small tools without additional infrastructure.
This approach is ideal for:
Before importing and running the workflow, make sure you have:
For the REST API, use a consistent path. For example, if you choose items as the path:
2a. Get All Items
GET items2b. Add Item
POST items2c. Edit Item
PUT items2d. Delete Item
DELETE items2e. Reset Items
POST items-resetSet the API URL in the SET API URL node. Use your n8n webhook URL, for example:https://yourn8n.com/webhook/items
Once everything is set:
This webhook serves a self-contained HTML Single Page Application (SPA) for basic CRUD operations. The HTML content is returned directly in the webhook response.
This setup is ideal for lightweight, browser-based tools without external hosting.
api_url in the SET API URL node to match your webhook endpointThis webhook handles retrieving all saved items from Redis. Each item is returned with its corresponding ID and associated data (e.g., name). This endpoint is used by the HTML CRUD App to display the full list of items.
GETThis webhook handles the Add Item functionality. This endpoint is typically called by the HTML CRUD App when adding a new item.
POST{ "name": "item name" }This webhook handles updating an existing item in Redis.
PUT{ "id": 1, "name": "Updated Item Name" }id and updates its data in RedisThis webhook handles deleting a specific item from Redis.
DELETE{ "id": 1 }id from RedisThis webhook handles resetting all data in the application.
POSTThis catalog entry is organized from the workflow JSON. The node-level section below shows the executable blocks available for review before importing the template.
Showing the first 24 of 27 workflow blocks. Download the JSON for the full node graph.
| Workflow | Create a self-contained CRUD app with Redis storage and HTML frontend |
|---|---|
| Complexity | advanced |
| Nodes | 27 |
| Categories | Engineering |
| Author | Ficky |
| Published | 06 Jul 2025 |
Use the JSON export at /data/workflows/5708/5708.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.
Build a Redis Powered CRUD App with HTML Frontend ![App Screenshot](https:/...
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 Engineering use case.