# AI Meeting Notes to Action Tracker with Zapier Agents + Jodoo

Use this workflow when meeting notes contain decisions, follow-up items, owners, dates, and blockers that need to become tracked work instead of staying inside a transcript or chat thread.

## What The Workflow Does

1. A meeting note or transcript summary is sent to a Zapier Agent.
2. The agent extracts one clear action item with owner, due date, priority, risk, and confidence.
3. Zapier sends the structured result to a Jodoo writeback step.
4. Jodoo stores the action item in a shared tracker with owner queues, due-date views, and blocker review.

## Jodoo App Pattern

App: AI Meeting Action Tracker  
Form: Meeting Action Record

Recommended fields:

- Meeting Title
- Meeting Date
- Source Notes
- Decision Summary
- Action Item
- Owner
- Due Date
- Priority
- Risk or Blocker
- Follow-up Status
- Source Platform
- Agent Confidence
- Original Agent Output

Recommended views:

- Open action items
- Due this week
- Blocked or at risk
- Owner queue
- All meeting actions

## Agent Output Contract

Ask the agent to return a single JSON object with these keys:

- `meeting_title`
- `meeting_date`
- `decision_summary`
- `action_item`
- `owner`
- `due_date`
- `priority`
- `risk_or_blocker`
- `follow_up_status`
- `source_platform`
- `agent_confidence`

## Production Notes

Use synthetic meeting notes for the first test run. Before using production transcripts, confirm data retention, access control, and who is allowed to review the generated action items.

For production use, route high-priority or blocked items to the right owner queue in Jodoo and keep the original agent output for review.

## Reuse Checklist

- Replace the sample meeting note with your own meeting source.
- Adjust priority values to match your operating model.
- Add an owner directory or team mapping if names need to route to queues.
- Keep the Jodoo fields stable before connecting more transcript sources.
- Review the first several runs before turning on automatic follow-up.