n8n workflow
Priority-focused overviews of customer feedback help teams act quickly on what matters most. This workflow receives feedback entries via webhook, checks data validity, groups responses by topic, and calculates count, average, and maximum severity for each topic. Results are sorted by priority and ready for immediate action. Especially useful for product, support, or marketing teams that handle regular feedback streams.
Teams can use this workflow to automatically receive, validate, and prioritize structured customer feedback. The process begins with a webhook that accepts POST requests containing an array of feedback entries (each with id, text, theme, severity 1-5). Data is checked for completeness and validity; invalid entries are rejected with an error message and index. Valid feedback is grouped by topic, with count, average, and maximum severity calculated per topic, and topics are sorted by priority (count × max severity) in the output. The structured JSON response allows for direct further processing or visualization. Webhook authentication must be enabled separately in n8n to prevent unauthorized access. Execution data is stored in n8n and should be managed accordingly. This workflow is particularly suitable for companies that regularly collect feedback and want to quickly identify key focus areas. The grouping and prioritization logic can be customized if needed.
Installation
1. Import the workflow into n8n. 2. Open the Webhook node and copy the test webhook URL. 3. Use a tool like Postman or curl to send a POST request with Content-Type application/json to the test URL (see example below). 4. Check the structured response. 5. After successful testing, enable webhook authentication in n8n and publish/activate the workflow. 6. Use the production URL from the Webhook node.
Usage
1. Send feedback data as a POST request to the webhook URL. Example: ```json { "feedback": [ {"id": "1", "text": "Login dauert zu lange", "theme": "Performance", "severity": 4}, {"id": "2", "text": "Design gefällt nicht", "theme": "UI", "severity": 2}, {"id": "3", "text": "Seite lädt langsam", "theme": "Performance", "severity": 5} ] } ``` Expected response: ```json { "status": "success", "themes": [ { "theme": "Performance", "count": 2, "averageSeverity": 4.5, "maxSeverity": 5, "ids": ["1", "3"], "priority": 10 }, { "theme": "UI", "count": 1, "averageSeverity": 2, "maxSeverity": 2, "ids": ["2"], "priority": 2 } ], "total": 3 } ``` Error case (e.g., empty feedback array): ```json { "status": "error", "message": "feedback muss ein nicht-leeres Array sein." } ``` HTTP status: 200 on success, 200 on error (response contains status: error). 2. The grouping and prioritization logic can be adjusted in the code node. 3. Enable webhook authentication in n8n before using the production URL. 4. Note that all transmitted data may be stored in n8n execution logs. Configure retention and access rights accordingly.
Required connections and APIs
No saved API credentials were detected in the workflow JSON. Still check webhooks, target systems, credentials, and data protection before activation.
Isolated functional test passed
The isolated data flow was tested without external services or credentials.
Buyer feedback
No reviews yet.
Back to product