Validate Meeting Tasks with Owners and Due Dates Automatically
Teams can maintain a clear overview after meetings: Task lists are received via webhook, mandatory fields such as task, owner, due date, and meeting are checked for completeness, and complete tasks are grouped by owner. Incomplete tasks are displayed separately. This streamlines meeting follow-ups and helps identify errors early.
Aimed at teams, project managers, and organizations seeking structured capture and tracking of meeting tasks, this workflow offers a reliable solution. Task lists containing the fields 'task', 'owner', 'dueDate', and 'meeting' can be securely submitted via webhook as an array of objects. Each task is checked for completeness of mandatory fields, complete tasks are grouped by owner, and the results are clearly structured. Incomplete tasks are listed separately with missing fields indicated. Integration with existing tools is straightforward due to the standardized JSON format. Webhook authentication must be set up separately in n8n to prevent unauthorized access. The workflow does not store data permanently, but execution logs can be saved in n8n—this should be considered during setup. Mandatory fields can be adjusted directly in the code node. This workflow is ideal for teams aiming to make their meeting follow-up both efficient and error-free.
AI-generated image
Installation
1. Import the workflow into n8n.
2. Open the Webhook node and copy the displayed test URL.
3. Start the test listener in n8n (do not activate the node separately).
4. Send a POST request to the test URL using a tool like Postman or curl (Content-Type: application/json, see example below).
5. Check the result in the n8n execution log and as the HTTP response.
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.
8. Optionally, adjust mandatory fields in the code node.
9. Configure retention and access to execution data in n8n according to data protection requirements.
Usage
1. Send task lists as a POST request to the webhook URL. The JSON must include a field 'actions' containing an array of tasks.
Example input:
```json
{
"actions": [
{"task": "Protokoll schreiben", "owner": "Anna", "dueDate": "2024-07-01", "meeting": "Teammeeting"},
{"task": "Präsentation vorbereiten", "owner": "", "dueDate": "2024-07-02", "meeting": "Teammeeting"}
]
}
```
Expected successful response (HTTP 200):
```json
{
"status": "needs_work",
"ready": [
{"index":0,"task":"Protokoll schreiben","owner":"Anna","dueDate":"2024-07-01","meeting":"Teammeeting","complete":true,"missing":[]}
],
"needsWork": [
{"index":1,"task":"Präsentation vorbereiten","owner":"","dueDate":"2024-07-02","meeting":"Teammeeting","complete":false,"missing":["owner"]}
],
"byOwner": {
"Anna": [
{"index":0,"task":"Protokoll schreiben","owner":"Anna","dueDate":"2024-07-01","meeting":"Teammeeting","complete":true,"missing":[]}
]
},
"total": 2
}
```
Incorrect input (e.g., no array):
```json
{
"actions": null
}
```
Response (HTTP 200):
```json
{
"status": "error",
"message": "actions muss ein nicht-leeres Array sein."
}
```
2. Mandatory fields can be adjusted in the code node.
3. Webhook authentication must be enabled separately in n8n.
4. Execution data is stored in n8n unless configured otherwise.
Required connections and APIs
API connections
No saved API credentials were detected in the workflow JSON. Still check webhooks, target systems, credentials, and data protection before activation.
Nodes
WebhookCodeRespond to Webhook
Isolated functional test passed
Optional isolated functional test
The isolated data flow was tested without external services or credentials.
✓ Standard case with complete dataChecks the complete standard flow with valid sample data.Isolated functional test passed✓ Variation or boundary caseChecks a valid variation or an important boundary case.Isolated functional test passed✓ Additional processing ruleChecks this workflow's additional business processing rule.Isolated functional test passed✓ Invalid or incomplete inputChecks that invalid or incomplete data is rejected safely.Isolated functional test passed✓ Empty inputChecks that an empty request receives a controlled response.Isolated functional test passed
