A meeting note's write-up is a summary of the meeting, the decisions made in it, the action items agreed and a follow-up email. Magpie does not write it for you: any chatbot you use, such as Claude or ChatGPT, writes it from your notes and the transcript, and you paste its answer back.

On a meeting note, open More:

  • Use a chatbot… gives you instructions to copy, with the meeting's title, date and people, your notes and the transcript. Paste them into a chatbot. It answers with a JSON document in the format below.
  • Import JSON… takes that answer and fills in the write-up.

Your notes and the transcript never change when you import. If the meeting note already has a write-up, Magpie asks before replacing it. A follow-up email in the answer replaces the one the meeting note has; an answer without one leaves it as it is.

Action items are offered as To-dos, unticked. Tick the ones you want, choose a To-do List, and add them. An owner whose name matches exactly one person who can use To-dos in the meeting note's team is assigned the To-do; otherwise the To-do is not assigned and its notes say who was named. A due date becomes the To-do's deadline. Importing again never offers or makes a To-do twice, and never changes a To-do already made.

The whole answer is checked before anything is saved. If any part of it does not fit the format, nothing changes and the problem is shown under the box, with the field that caused it. An answer can be at most 300 KB.

Rules for a chatbot

  • Answer with one JSON object in one json code block, and nothing else.
  • Use only what the notes and the transcript say. Add no facts, names, numbers, prices or dates.
  • The person's notes are the most important source. The transcript comes from speech recognition and may get names wrong.
  • Write in the language the meeting was held in.
  • Ask nothing first. Leave out what is unclear, and leave out any field there is nothing for.

The document

Field Type Notes
format string, optional Always magpie.meeting-note-writeup.
version number, optional Always 1.
summary_markdown string, required The write-up, in Markdown, with ## headings. At most 60,000 characters.
decisions list of strings, optional What was decided, one short sentence each. At most 50, each at most 1,000 characters. Shown under a Decisions heading after the summary.
action_items list, optional What someone agreed to do. At most 50.
follow_up_email_markdown string, optional An email to send to the people in the meeting, in Markdown, with no subject line. At most 60,000 characters.

Each action item

Field Type Notes
title string, required What to do, starting with a verb. At most 255 characters.
owner string, optional The name of the person who agreed to do it, as it was said in the meeting. At most 255 characters.
due string, optional The date it is due, written as YYYY-MM-DD, such as 2026-11-07. Only when a date or a day was said.

Example

{
  "format": "magpie.meeting-note-writeup",
  "version": 1,
  "summary_markdown": "## Their situation\n\nHalden Freight runs 40 vans and plans its routes by hand each morning.\n\n## Needs and objections\n\n- Routes ready by 7am\n- Worried about the time to train drivers\n\n## Pricing discussed\n\nThe annual plan at the quoted price, with the first month free.\n\n## Next steps\n\nA revised quote, then a trial with five vans.",
  "decisions": [
    "Start with a trial of five vans in November."
  ],
  "action_items": [
    { "title": "Send the revised quote", "owner": "Priya Shah", "due": "2026-11-07" },
    { "title": "Choose the five vans for the trial", "owner": "Tom Becker" }
  ],
  "follow_up_email_markdown": "Hi Tom,\n\nThank you for your time today. We agreed to start with a trial of five vans in November.\n\n- I will send the revised quote by 7 November.\n- You will choose the five vans for the trial.\n\nBest wishes,\nPriya"
}

If an answer is rejected for a reason you can't work out, Support kontaktieren.

Den Magpie-Support fragen

Senden Sie dem Magpie-Team eine Frage zu allem, was dieser Artikel nicht beantwortet.