# AI Meeting Notes to Action Tracker with Pipedream + Jodoo

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

## What The Workflow Does

1. A Pipedream HTTP trigger receives a meeting-note payload.
2. A code or API step prepares a structured action payload.
3. A Pipedream API Request action posts the JSON body to the Jodoo writeback layer.
4. Jodoo stores the follow-up 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

## Pipedream Workflow Notes

Keep the first version compact and inspectable:

- HTTP trigger receives the source note or transcript summary.
- A code, transform, or AI/API step returns one action-item object.
- API Request posts JSON to the Jodoo writeback layer.
- Test output confirms `ok: true` and a Jodoo data ID.

For the proof run, the API Request sent a `payload` field containing a parseable JSON string. The Jodoo bridge parsed that payload and created the action record.

## 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, store endpoints and credentials safely, add retry handling, and return clear errors when owners, due dates, or required fields are missing.

## 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 API Request body remains valid JSON after editing.
- Review the first several runs before enabling automated notifications.