Skip to main content

Run a meeting follow-up with AI

Review a prepared meeting Action and continue it in your preferred AI client without losing the meeting context.

Written by Topi Järvinen

Meeting Actions turn captured context into a starting point for follow-up work. Review the source and intended outcome before handing an Action to an AI client.

Before you start

  • The Recorder must have joined and finished processing the meeting.

  • You need access to the meeting and its connected Workspace.

  • Follow the connection instructions shown by the Action if it needs another AI client or destination tool.

Open the meeting Actions

  1. Select Meetings in the navigation.

  2. Open the completed meeting.

  3. Select Actions.

If the tab says No updates yet, there is no prepared follow-up to run from that view. Review Notes for the agreed next step and create the follow-up in the appropriate tool instead.

A fictional Quartz Retro meeting with populated Action cards and a Run with Claude handoff

Review the proposed follow-up

Before running an Action, confirm:

  • the requested outcome;

  • the source meeting and relevant Workspace;

  • the intended audience and destination;

  • names, dates, owners, and commitments;

  • whether the follow-up would disclose sensitive context.

The Action is a draft based on captured context. It is not proof that participants approved the wording or authorized an external change.

Continue from the Action

Use the action offered on the prepared follow-up. The exact label and destination can depend on the follow-up type and the tools connected to your account.

In the receiving client:

  1. review the prepared prompt and included context;

  2. make the requested draft or analysis specific;

  3. check the result against the meeting Notes or Transcript;

  4. confirm the final audience and destination;

  5. approve any send, save, booking, or record change explicitly.

If the product offers a prompt preview or copy option, inspect the prepared context before continuing.

Keep source and execution separate

The meeting remains the source record. The destination tool is where you refine or carry out the follow-up.

For example:

  • check an email recap against the meeting before sending it;

  • confirm a tracker update belongs in the correct project;

  • review a proposed Slack message for channel visibility;

  • confirm participants and timing before booking another meeting.

Return to the meeting when you need to resolve an attribution or source question. Do not treat an AI-generated draft as a new meeting decision.

Related

Did this answer your question?