# Meeting follow-up

Saves a follow-up email draft for each outside meeting that ended today.

Requires Google Calendar, through Composio. Requires Gmail, through Composio. Runs on a schedule.

## Install

No one has run this against real Google Calendar and Gmail accounts through Composio yet. Its eval cases use stand-ins.

```sh
npx @parcha/agentrun template install github:Parcha-ai/agentrun-templates/templates/meeting-follow-up@242f29da8317fbe51d0cce4628bdb5ab61d7ccc9 --trust
```

Or open `<your AgentRun address>/#/templates/install?src=github%3AParcha-ai%2Fagentrun-templates%2Ftemplates%2Fmeeting-follow-up%40242f29da8317fbe51d0cce4628bdb5ab61d7ccc9`. Pinned to commit 242f29da8317fbe51d0cce4628bdb5ab61d7ccc9.

## What it does

At the end of each workday it goes through the meetings that ended today with people from outside your company and saves a follow-up email for each one as a Gmail draft. Each draft thanks them, lists the invite's agenda with a bracketed blank for each outcome, and leaves a blank for the next step. It never invents what was agreed and never sends. Each draft waits for your yes before it's saved, then you fill the blanks and press send. Internal meetings, ones you declined, cancelled ones and ones it already drafted are skipped.

- Skill `meeting-follow-up`: Draft a follow-up email for each of today's ended meetings with outside attendees, through Composio's Google Calendar and Gmail tools. Read the day's events, keep the outside meetings the owner attended that have ended, skip any already drafted, and save one Gmail draft per meeting to one outside attendee, with the invite's agenda and bracketed blanks for every outcome. Never a send. Use for the end-of-day schedule and for "draft follow-ups for \<day\>".

## What starts it

- On a schedule: weekdays at 17:00 (UTC), unless you pick another time when you install it.
- By hand, any time: from the console, the API or the CLI.

## Inputs

| Name | Type | Required | What it is |
| --- | --- | --- | --- |
| `date` | string, date | no | Draft follow-ups for this day's meetings instead of today's, for a run by hand. Example: `2026-11-17`. |
| `notes` | string, 0 to 2000 characters | no | What was agreed, per meeting, to fill in instead of blanks ("Globex: 30-day pilot from Dec 1, Kim sends the data export"). Blank: every outcome is a bracketed blank. Example: `Globex: 30-day pilot from Dec 1; Kim sends the data export by Friday.`. |

### Setup, filled in once at install

| Name | Type | Required | What it is |
| --- | --- | --- | --- |
| `calendar_id` | string | no | The Google calendar to read: primary (your main calendar) unless you set another calendar's id. Default: `primary`. |
| `internal_domains` | list of string | no | The email domains of your own company (acme.com, acme.co.uk). A meeting with only these people gets no draft. Blank: your own address's domain. |
| `voice` | string | no | How you write, in a line: "short, first names, sign off 'Best, Mia'". Blank: plain and short, signed with your first name. |
| `cron` | string, cron | no | When it runs, as a cron line (minute hour day-of-month month day-of-week): weekdays at 17:00 unless you set it. Only meetings that ended before the run get a draft. Default: `0 17 * * 1-5`. |
| `timezone` | string, timezone | no | Your IANA time zone (Europe/Madrid, America/New\_York): the cron line and "today" are read in it. UTC unless you set it. Default: `UTC`. |

## What it needs

- Harness: pi, claude-agent, codex
- Model: balanced tier, medium effort
- Tools: read
- Composio Google Calendar tools: GOOGLECALENDAR_EVENTS_LIST. Reads today's events on the one calendar you set. Never creates, moves or answers an event.
- Composio Gmail tools: GMAIL_CREATE_EMAIL_DRAFT. Saves one follow-up draft per outside meeting. It can't send. Each draft goes to someone who was in the meeting, which no setting can fix in advance, so you tick it yourself; cc, bcc and extra recipients are always off.
- Computer: Wherever your AgentRun puts a new agent
- Keys: A model key
- Learning: on

## Sample output

Input:

```json
{
  "content": "Draft follow-ups for Tuesday's outside meetings.",
  "date": "2026-11-17",
  "notes": "Globex: 30-day pilot from Dec 1; Kim sends the data export by Friday."
}
```

Output:

Illustrative output, written by hand to show the shape. A measured eval run replaces it.

Two follow-up drafts wait in Gmail. Neither is sent.

- **Globex pilot kickoff**, to Kim Lee. Pilot and next steps filled from your notes. Fill the success metrics and the rollout plan link. Add Raj Patel if you want Raj on it.
- **Intro: Brightpane**, to Sam Ortiz. Fill what stood out, the trial and the next step.

Skipped: the hiring sync (internal), Northwind (you declined), Umbrella (cancelled), and the Initech review (an earlier run drafted it).

> Hi Kim,
>
> Thanks for your time on Tuesday. A quick recap:
>
> - Pilot: 30 days, starting Dec 1.
> - Success metrics: [the metrics we agreed]
> - Rollout plan: [link: the draft rollout plan]
>
> Next steps: you send the data export by Friday. [anything else on our side]
>
> Best,
> Mia

## Tested

Passes 4 of 4 eval cases on pi, 3 of 4 on Claude Code and 4 of 4 on Codex.

4 eval cases: drafts-for-external, injection-in-description, no-repeats, thin-agenda.

## Source

- Package: https://github.com/Parcha-ai/agentrun-templates/tree/242f29da8317fbe51d0cce4628bdb5ab61d7ccc9/templates/meeting-follow-up
- Publisher: Parcha-ai
- Author: Parcha Labs
- Version: 0.1.0
- License: Apache-2.0
- Category: Sales
- Page: https://marketplace.agentrun.ai/templates/meeting-follow-up/
