# n8n Workflow Recipe: Meeting Notes to Jodoo Action Tracker

This recipe shows the n8n proof structure for turning meeting notes into a Jodoo action record. Adapt the webhook source and endpoint before using it with production meeting notes.

## Input Contract

The webhook can receive the full meeting note or an already-normalized object.

```json
{
  "meeting_title": "Customer onboarding risk review",
  "meeting_date": "2026-06-04 10:30",
  "source_notes": "The customer success, implementation, and billing teams reviewed the onboarding plan..."
}
```

## Agent Or Code Instruction

Read the meeting notes and return one structured action item that a team can track in Jodoo.

Rules:

- Return one JSON object per run.
- Do not invent owners, dates, or commitments that are not supported by the notes.
- If the owner is unclear, set `owner` to `Needs assignment`.
- If the due date is unclear, set `due_date` to `Needs date`.
- Use one of these priority values: `Critical`, `High`, `Medium`, `Low`.
- Use one of these follow-up statuses: `Needs owner confirmation`, `Open`, `In progress`, `Blocked`, `Done`.

Required JSON keys:

```json
{
  "meeting_title": "",
  "meeting_date": "",
  "source_notes": "",
  "decision_summary": "",
  "action_item": "",
  "owner": "",
  "due_date": "",
  "priority": "",
  "risk_or_blocker": "",
  "follow_up_status": "",
  "source_platform": "n8n",
  "agent_confidence": ""
}
```

## n8n Workflow Shape

1. Add a Webhook trigger and use the test URL for the first proof run.
2. Send a sample meeting-note payload while n8n is listening.
3. Add a Code, Set, or AI Agent step that produces the required JSON.
4. Add an HTTP Request node.
5. Set method to `POST`.
6. Set body content type to `JSON`.
7. Use `Using Fields Below` with a `payload` field, or send a raw JSON body.
8. If using a `payload` field, set the value expression to `{{ JSON.stringify($json) }}`.
9. Confirm the HTTP Request node completes and returns a Jodoo data ID.
10. Open Jodoo and verify the owner, due date, priority, blocker, status, and original output.

## Jodoo Mapping

- `meeting_title` -> Meeting Title
- `meeting_date` -> Meeting Date
- `source_notes` -> Source Notes
- `decision_summary` -> Decision Summary
- `action_item` -> Action Item
- `owner` -> Owner
- `due_date` -> Due Date
- `priority` -> Priority
- `risk_or_blocker` -> Risk or Blocker
- `follow_up_status` -> Follow-up Status
- `source_platform` -> Source Platform
- `agent_confidence` -> Agent Confidence
- Full JSON output -> Original Agent Output