n8n workflow
Missing mandatory fields and duplicate posts in editorial calendars are reliably detected: data submitted via webhook is automatically checked, allowing marketing teams and content managers to manage editorial plans efficiently and error-free. The structured output highlights errors, duplicates, and provides an overview of posts per channel—ready for further automation.
Common errors in editorial calendars can be identified automatically with this solution. Marketing teams, agencies, and content managers submit scheduled posts as JSON via a secure webhook. The analysis checks whether all mandatory fields (topic, channel, date) are filled, detects duplicate posts per channel and date, and generates an overview of posts per channel. Errors and duplicates are returned in a structured result. This solution is suitable for anyone who wants to manage editorial plans efficiently and without errors. Webhook authentication must be configured separately in n8n to prevent unauthorized access. Execution stores user data in the n8n log; this should be considered when handling personal data. Validation rules can be adjusted in the code node if needed. The workflow is ready to use immediately, requires no external integrations, and can be flexibly integrated into existing processes.
Installation
1. Import the workflow into n8n. 2. Select the Webhook node and start the test listener. 3. Copy the displayed test URL and use it for test requests. 4. Send a sample POST with Content-Type application/json to the test URL (see usage instructions). 5. Check the result in the n8n execution log. 6. After successful testing, publish/activate the workflow and use the production URL from the Webhook node. 7. Set up webhook authentication in n8n to prevent unauthorized access.
Usage
1. Send a POST request with the following example JSON to the webhook URL: ```json { "posts": [ {"topic": "Blogartikel", "channel": "Facebook", "date": "2024-07-01"}, {"topic": "Video", "channel": "Facebook", "date": "2024-07-01"}, {"topic": "Newsletter", "channel": "Mail", "date": "2024-07-02"}, {"channel": "Instagram", "date": "2024-07-03"} ] } ``` Expected response (status 200): ```json { "status": "needs_work", "errors": [ {"index": 3, "message": "topic, channel und date sind erforderlich."} ], "duplicates": [ {"firstIndex": 0, "secondIndex": 1, "channel": "Facebook", "date": "2024-07-01"} ], "byChannel": {"Facebook": 2, "Mail": 1, "Instagram": 1}, "total": 4 } ``` Error case (empty posts array, status 200): ```json { "status": "error", "message": "posts muss ein nicht-leeres Array sein." } ``` 2. The fields "errors" and "duplicates" show all detected issues. "byChannel" provides the count of posts per channel. 3. If needed, you can edit mandatory fields or validation rules in the code node. 4. Webhook authentication must be configured separately in n8n. 5. Note that all submitted data may be stored in the n8n execution log.
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