Meeting Action Hub

Problem: Action items scatter across meeting context

After 4-6 meetings a day, decisions, owners, and deadlines often remain split across chat, email, and notes. Manual cleanup can miss vague action items and is hard to follow up. ActionHub targets this workflow: it turns meeting minutes into structured action items and a local follow-up board, rather than sending messages or taking over a project management system.

How it works: from minutes to a board

The pipeline starts with input validation, then extracts decisions, action items, and open questions. It matches owners using tiered confidence levels and suggests deadlines based on action-item type. It supports WeCom, Feishu, email, and JSON output, and can use actionhub.py for batch extraction, board generation, and configuration. Key capabilities include:
- Structured minutes: decisions → action items → open questions → information sync
- Action-item extraction and owner correction: vague items can be marked to be assigned
- Deadline suggestions: applies policies for information confirmation, deliverable, and decision-dependent items, skipping weekends by default
- Follow-up copy: generates reminders around D-1, D-0, and D+1

Fit and limits

It is best for lightweight meeting follow-up, not for live transcription, complex cross-department approval chains, Jira/TAPD/Asana integration, or automatic sending. Keep action items to about 15 per meeting and active items under 50. Write items as owner + action + output for more stable matching.