Meeting follow-up
Turn meeting notes into decisions and draft tasks, then confirm owners before saving anything.
Start with the example, follow the four steps and review the proposed output. Adapt the destinations to your own tools before connecting any writes.
The four steps
Capture the discussion
RulesKeep the notes, participants and meeting ID. Retain the original context for review.
Separate decisions and tasks
AIExtract explicit agreements and follow-ups. Keep unassigned owners and missing deadlines empty.
Confirm who does what
Your reviewReview each proposed task with its evidence. Confirm owners, deadlines and any disputed decision.
Save the approved follow-up
RulesSave approved tasks once using the meeting ID. Prepare a summary draft; sending remains a separate action.
Examples, setup, prompts and checks below use the portable English recipe. The steps above are translated. Examples are illustrative; this page runs no connections.
Example input
{
"notes": "We agreed to try the smaller launch. Lina will draft the page. Someone needs to check analytics. No date was agreed."
}Reviewed output to aim for
{
"decisions": [
"Try the smaller launch"
],
"tasks": [
{
"title": "Draft the launch page",
"owner": "Lina",
"due_date": null
},
{
"title": "Check analytics",
"owner": null,
"due_date": null
}
],
"needs_review": [
"Assign an analytics owner and confirm deadlines."
],
"messages_sent": 0
}Set it up
- Choose where meeting notes arrive and where approved tasks belong.
- Keep participant names and meeting IDs linked to each extracted task.
- Separate task creation from drafting or sending a follow-up message.
Reusable prompt
Extract decisions and tasks from {{meeting_notes}}. Distinguish explicit agreements from suggestions. Return tasks with title, owner, due_date and evidence. Owners or dates not stated must be null. Put ambiguities in needs_review. Do not invent commitments, create tasks or send messages.Check your version
- Suggestions are not recorded as agreed decisions.
- Missing owners and dates remain unset until reviewed.
- Re-running the same meeting produces no duplicate tasks or outgoing messages.
Limits and tradeoffs
The model proposes; rules validate and you review. Keep the original input, preserve missing values, and verify the result before saving or sending it. Re-running an input should not duplicate an approved action.