Every team has a version of this story. The meeting ends, somebody says "I'll send the recap," everyone nods, and three days later a decision nobody wrote down gets re-litigated from memory. It isn't laziness — writing up a meeting takes ten minutes that nobody has between back-to-back calls, so the follow-up quietly stops happening.

The meeting follow-up recipe removes the volunteer from the equation. A recording bot joins the call, transcription and summarization happen automatically, and a webhook handler emails the recap — summary plus action items — to everyone who was on the calendar invite. If you give that handler its own Agent Account (currently in beta), the recap comes from a dedicated address like meetings@yourcompany.com and replies thread back into a mailbox your code can read.

Five steps, one webhook

The pipeline is short: Notetaker joins the meeting → the recording gets processed → notetaker.media fires → your handler downloads the summary and action items, looks up the event's attendees → sends the recap through the send endpoint. Each step fails independently, so one broken attendee lookup doesn't stall the rest. Subscribe to notetaker.meeting_state alongside the media trigger and you'll also know when the bot joins and leaves each call, which makes failures visible instead of silent.