Meeting follow ups your agent drafts, files, and posts

The hour after a meeting is when its outcome gets recorded, and it is the hour that most often gets skipped. The recap email you meant to send sits in your head until the context fades. The three things you agreed to do never make it into the tracker. The people who were not in the room never hear what was decided.

Each of those is a small job in a different app, landing right when you are already moving to the next call.

Research on meeting productivity consistently points to the same fix: a written recap with named owners and deadlines, sent while the discussion is still fresh. Alfred's guide to meeting follow up emails recommends five elements in every recap: decisions made, action items with a specific owner and deadline for each, open questions parked for next time, the next meeting date if there is one, and a one line thank you.

Fyxer adds the practical timing: same day, under 200 words, scannable format with bold headers rather than narrative paragraphs. The format is simple; the friction is doing it three times across email, a task tracker, and a team channel.

An agent that can reach your inbox, your task tool, and your team chat at once closes that gap in one pass. Composio is the connection that gives your Operator.io agent all three through one setup, so a single prompt can turn the end of a meeting into a drafted email, a set of tasks, and a posted recap, each one held for your yes before it goes anywhere.

How it works

You send the follow up prompt, and the agent runs the same routine after a meeting ends.

• It drafts a short recap email to the attendees from the notes you give it or the agenda on the calendar invite, capturing what you agreed and the next steps, and shows you the draft before anything sends.
• It turns each action item into a task in your project tool, with an owner and a due date.
• It drafts a brief recap for the Slack channel for that project so the people who were not there are caught up.

Nothing leaves without your approval, and that includes the Slack post. The agent shows you the email, the task list, and the recap it wants to put in the channel, then waits for your yes on all three before it sends, files, or posts anything. The Slack recap matters here because it is the one output that goes to other people the moment it lands, so it gets the same look as the email rather than going out on its own. If the channel it picked is wrong, or a line in the recap says more than you want the wider team to read, you fix it before you approve.

The agent pulls meeting context from your calendar through Composio's Google Calendar or Outlook integration, reads attendee lists and agenda text from the invite, and uses your notes or a transcript you paste into the channel to fill in what was actually discussed. What you paste is what it works from, so a few lines of your own notes give it enough to draft from, and you do not need to drop a full recording transcript into the chat to get a good recap. If part of the conversation was salary, a personnel issue, or a number that should not sit in your channel history, trim it out of the notes before you hand them over and the recap still covers the decisions and the next steps.

The recap email goes out through Gmail or Outlook depending on which you connected. Tasks land in Notion, Linear, Asana, or whichever project tool you named in the prompt. The team recap posts to a Slack channel you specify.

Connect Composio first

This prompt reaches your calendar, your inbox, your task tool, and Slack, so it needs Composio connected to your agent. Open the MCPs page in your Operator dashboard and add Composio, signing in to your own account in the window that opens. The Composio setup guide covers it end to end, and the prompts library will offer to connect it inline the first time you send a prompt that depends on it. Composio's free tier covers twenty thousand tool calls a month with no card, which is far more than a normal week of meetings will use.

Each app authorizes the first time the agent uses it, so expect a quick approval for Google, your task tool, and Slack on the first run. Composio supports Gmail, Google Calendar, Slack, Notion, Linear, Asana, and other common tools through its toolkit directory, so whichever stack you run, the agent works against the tools you already use rather than asking you to switch.

The prompt

This is the instruction the agent acts on:

Help me with meeting follow ups using the apps I connected through Composio.
After a meeting on my calendar ends, draft a short follow up email to the
attendees from the notes I give you or the agenda on the invite, capturing
what we agreed and the next steps, and show me the draft before anything
sends. Turn each action item into a task in my project tool with an owner
and a due date, and draft a brief recap for the Slack channel for that
project. Show me the email, the task list, and the Slack recap together,
and wait for my yes before you send the email, create the tasks, or post to
Slack. Before you start, ask me which calendar, task tool, and Slack
channels to use, how you should decide which meetings are worth a follow up,
and confirm that you always show me the email and the Slack recap first.

The same prompt is saved in the prompts library, so you can send it to your agent without retyping a word.

Using it day to day

The flow fits the way a meeting ends. You drop your notes into the channel, or just say the meeting wrapped, and the agent comes back with a draft email, a short list of tasks it wants to create, and the recap it plans to post. You read the email and the recap, fix the line that is off in either one, and tell it to go. The tasks land in your tracker with owners and dates, and the recap posts to the project channel, all from a single back and forth instead of three trips into three apps.

A good recap email names every action item with a single owner and a specific date. "Sarah sends the revised contract to Legal by Thursday" beats "follow up on the contract situation." The agent drafts in that format because the prompt asks it to capture what you agreed, and you can tighten any line that is still vague before you approve the send. If someone on the call was responsible for a task but their name is missing from the draft, add it before you say go.

You decide which meetings are worth the routine. Tell it to follow up on external calls and skip the internal standups, or to only run when you hand it notes, and it holds to that. Because the same agent files the tasks and sends the email, you can ask it later what is still open from a given meeting, and it can answer from the tasks it created rather than you digging through the tracker yourself.

For recurring meetings, the agent can learn your preferences over time: which Slack channel maps to which project, whether standups get a Slack post but no email, and how formal the recap tone should be for client calls versus internal syncs. Those preferences live in the agent's memory and the prompt, so you refine the routine as you use it rather than configuring a workflow builder.

Why route it through Composio

The reason this is one prompt and not three separate integrations is Composio. It holds the OAuth for your calendar, your inbox, your task tool, and Slack and keeps the tokens fresh, so the agent moves across all four without you managing a credential for each.

Wiring Gmail, Google Calendar, Slack, and Linear directly would mean four separate OAuth apps, four token refresh handlers, and four sets of API documentation to maintain. Composio exposes each service as named tools the agent can call, and loads only the tools a given step needs so the context stays focused.

Swap your tracker from Notion to Linear later and the prompt does not change, because Composio carries both toolkits and the agent just points at whichever you connected. Everything runs against your own Composio account, with the apps and tokens under your control.

To set it up, connect Composio on the MCPs page, then open the prompts library and send the meeting follow ups prompt. It asks which calendar, tracker, and channels to use and how to pick which meetings get a follow up, and then the recap email, the tasks, and the Slack note land after each call without you chasing them.