# AI Meeting Notes to Action Tracker with Make + Jodoo

Use this workflow when meeting notes contain decisions, follow-up items, owners, dates, and blockers that should become tracked work in Jodoo.

## What The Workflow Does

1. A Make Custom webhook receives a meeting-note payload.
2. Make keeps the scenario visible with a webhook trigger and HTTP writeback module.
3. The workflow sends structured action fields to the Jodoo writeback layer.
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

## Make Scenario Notes

Keep the first version compact:

- Custom webhook receives the source note or transcript summary.
- A transformation or agent step returns one action-item object.
- HTTP module posts JSON to the Jodoo writeback layer.
- Run once mode confirms the webhook bundle, HTTP response, and Jodoo data ID.

## 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 generated follow-up items.

For production use, add retry handling, error notifications, and a review queue for missing owners, unclear dates, or low-confidence output.

## Reuse Checklist

- Replace the sample meeting note with your real meeting source.
- Keep the output schema stable before connecting more transcript sources.
- Match priority and follow-up status values to your Jodoo options.
- Confirm the Make HTTP module parses the Jodoo writeback response.
- Review the first several runs before enabling automated notifications.