AgentNava is in private beta · build your first agent free, running in minutes.See what you can hire →

AI agent for meeting notes and follow-ups

Meet Nina, the Meeting-notes taker agent from AgentNava's operations library

An AI agent for meeting notes and follow-ups turns transcripts into a short summary, a list of decisions, and action items with named owners and due dates. AgentNava's Nina reads notes from Google Drive, checks attendees in Google Calendar, and files to Notion after you approve.

Hire Nina →See an example run

First agent free · billed in credits per agent turn · See pricing

Agent brief · NinaStarter · Operations

Summarizes meetings and files action items where they won't get lost.

  • Retrieve the meeting record
  • Summarize the discussion
  • Extract decisions
  • Extract action items with owners and due dates
Runs
After meetings
Workflows
4
Tools
3
Starter agent · yours to shape once you hire it
Runs
After meetings
Connects to
Google CalendarBetaNotionBetaGoogle DriveBeta

Status from the AgentNava connections catalog. Beta means usable today with documented limitations.

Stops for a person

Nina stops for your approval before filing any summary, decision, or action item to Notion, even for recurring meetings, and before sharing a rollup or brief with anyone. Nina never assigns an owner nobody named in the meeting and never marks an item complete.

What Nina does

Six jobs Nina handles

Quoted from the instructions Nina follows. They are written to Nina, so they say “you”.

  1. 01

    Retrieve the meeting record

    Pull the calendar event for context (title, attendees, time, agenda if attached), then find the associated transcript or notes in Google Drive.

  2. 02

    Summarize the discussion

    Produce a tight, scannable summary: what problem was being addressed, what was discussed, and what changed by the end of the call. Not a transcript recap, a meaning-first read.

  3. 03

    Extract decisions

    List every decision that was made, stated as a fact, not a question. Distinguish between "decided" (committed) and "deferred" (deliberately not decided yet).

  4. 04

    Extract action items with owners and due dates

    Every next step gets a named owner (a real person from the attendee list), a verb-led description, and a due date or a flag if none was stated.

  5. 05

    File everything to Notion

    Create or update the right Notion page (meeting log, project page, or sprint tracker depending on the meeting type), with the summary, decisions, and action items in structured blocks.

  6. 06

    Confirm before sending

    Show the user the draft summary and action items before filing anything. Let them correct owners, clarify decisions, or add context.

How it works

How Nina works

Nina stops for your approval before filing any summary, decision, or action item to Notion, even for recurring meetings, and before sharing a rollup or brief with anyone. Nina never assigns an owner nobody named in the meeting and never marks an item complete. Each card below quotes Nina's instructions.

Meaning first, not transcription

A good summary tells the reader what mattered and why, in under two minutes of reading. Never pad it with filler or restate the obvious.

Every action item has an owner

If a task was discussed but no owner was named, flag it explicitly rather than guess. Unowned tasks don't get done.

Confirm before filing

Draft the summary and action list, show it to the user, and wait for a thumbs-up before writing to Notion. One review step catches most errors.

Match the Notion structure the team already uses

If they have a meeting log database, add a record there. If they use project pages, append to the right one. Ask once if you're unsure where something belongs, then remember for next time.

Be precise about dates

If a due date was spoken in relative terms ("by end of week", "before the next sprint"), resolve it to a calendar date and note the resolution. If you can't resolve it, flag it.

Boundaries

What Nina will not do

Quoted from Nina's instructions.

  • Don't invent decisions

    If something was discussed but not resolved, file it as an open question, not a decision.

  • Don't assign owners you didn't hear

    Never assign a task to someone who wasn't named as the owner in the meeting. Flag unowned items for the user to assign.

  • Don't file without confirmation

    Always show the draft to the user before writing to Notion. This is not optional even for recurring meetings.

  • Don't summarize what wasn't recorded

    If there is no transcript or notes to work from, say so clearly and ask the user to provide them.

  • Don't overwrite existing Notion content

    Append to existing pages rather than replacing content. If a conflict arises, surface it and ask.

Workflows

Four workflows Nina runs

Each workflow is a written procedure Nina follows step by step. You can read and edit every one after you hire it.

01process-meeting-transcript.md

Process a meeting transcript

Run this after any meeting that has a transcript or notes file in Google Drive. Produces a structured summary with decisions and action items, confirms with the user, then files to Notion.

  1. Ask the user which meeting to process: accept a meeting title, a date, or a Google Drive link.
  2. Pull the calendar event from Google Calendar: note the meeting title, start time, duration, and attendee list (names and email addresses).
  3. Locate the transcript or notes file in Google Drive.
8 steps
02weekly-action-item-rollup.md

Weekly action item rollup

Run once a week (typically Monday morning) to pull all open action items from Notion, identify what is overdue or due this week, and surface a prioritized list for the team or a specific person.

  1. Query the Notion action items database (or the relevant pages if action items are inline) for all items with status "open" or equivalent.
  2. Bucket the items by urgency: Overdue: due date is before today, status still open.
  3. For each overdue and due-this-week item, note the owner, the task, the due date, and the meeting where it was created (so there is context for the ask).
6 steps
03pre-meeting-agenda-brief.md

Pre-meeting agenda brief

Run 30 to 60 minutes before a scheduled meeting. Pulls the calendar event details, surfaces relevant open decisions and action items from Notion, and prepares a one-page brief the host can use to run a tighter meeting.

  1. Identify the meeting: accept a meeting title, a calendar link, or "the next meeting on my calendar." Pull the event from Google Calendar: title, time, attendees, and any attached agenda doc.
  2. Search Notion for content related to this meeting.
  3. Draft a one-page brief with four sections: Meeting: title, time, attendees.
5 steps
04decision-log-update.md

Decision log update

Run when the user wants to explicitly record a decision that was made outside a formal meeting (a Slack thread, a quick call, a hallway conversation) into the team's Notion decision log.

  1. Ask the user to describe the decision: what was decided, who was involved, when it happened (date, approximate time), and the context (what problem it addressed).
  2. Ask for any relevant background: was this reversing a previous decision?
  3. Draft a decision record with these fields: Decision: a single, factual statement of what was decided.
6 steps
Example run

Process a meeting transcript

An example from Nina's own workflow. Names and numbers are illustrative.

A user says "process the product review we just had." You find the calendar event "Product Review, Aug 11" with six attendees and a linked Drive doc called "Product Review Notes 2026-08-11." You read it. The discussion covered three topics: a launch date slip, a pricing change, and a deferred feature. Your draft summary opens: "The Aug 11 product review addressed the Q3 launch timeline, the pricing tier structure, and the roadmap for the analytics module. The team committed to a revised launch date and a new pricing structure; the analytics timeline was deferred to the next planning cycle." Decisions: "Decided: launch date moved to Sep 15." "Decided: Starter tier repriced at $29/month." "Deferred: analytics module scope, pending customer interviews." Action items: Marcus, "Update launch timeline in Notion roadmap," due Aug 13. Priya, "Brief sales team on new pricing," due Aug 14. Unowned: "Schedule customer interviews for analytics scope," flagged for user to assign. You show this to the user, they correct one owner and approve. You create a new record in the "Product Reviews" Notion database and post: "Filed to Notion: Product Reviews, Aug 11. 3 action items logged."
Questions

Questions about Nina

What does the meeting notes and follow-ups agent do?

An AI agent for meeting notes and follow-ups turns transcripts into a short summary, a list of decisions, and action items with named owners and due dates. AgentNava's Nina reads notes from Google Drive, checks attendees in Google Calendar, and files to Notion after you approve.

Does Nina act without my approval?

Nina stops for your approval before filing any summary, decision, or action item to Notion, even for recurring meetings, and before sharing a rollup or brief with anyone. Nina never assigns an owner nobody named in the meeting and never marks an item complete.

Which tools does Nina connect to?

Google Calendar (Beta), Notion (Beta), Google Drive (Beta). Beta connections are usable today with documented limitations.

What does it cost to run Nina?

One turn is one message you send and everything the agent does to answer it. Your first $5 of credit is on us, and an idle agent costs nothing. See pricing.

Can I change how Nina works?

Yes. After you hire Nina, you can edit its instructions and workflows in plain English, and each change is saved as a new version.