AI AGENTS

Post-meeting board deck archive and recap

After the board meeting, exports the finalized deck, archives it to Google Drive in the dated board folder, generates a one-page executive recap.

CategoryAI Agents
Enginesim
Difficultybeginner
Triggerevent
Steps5
Setup~5 min

How it runs

The automated pipeline, trigger to output.

  • TriggerCalendar event: board meeting endsGoogle CalendarGoogle Calendar
  • ActionRead finalized deckNotionNotion
  • ActionGenerate one-page executive recapOpenAI
  • ActionArchive deck to dated Drive folderGoogle DriveGoogle Drive
  • OutputPost recap link to board Slack channelSlack

What it does

Closes the loop after the board meeting. It takes the finalized deck, files a permanent copy in the correctly dated board folder on Google Drive, distills a one-page executive recap of the decisions and headline metrics, and shares that recap where the board and staff can find it. No more decks lost in someone's downloads folder.

When to use it

Use it when board materials are scattered and there's no clean record of what was presented when, or when people who missed the meeting need a fast catch-up without reading the full deck.

How it works

  1. 1A calendar event marking the board meeting's end triggers the run.
  2. 2The finalized deck is read from Notion.
  3. 3OpenAI condenses it into a one-page executive recap of decisions and key numbers.
  4. 4The full deck is archived to the dated board folder in Google Drive.
  5. 5The recap link is posted to the board Slack channel.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect Google CalendarEvents, attendees, availability.
  2. 2
    Connect NotionPages, databases, comments.
  3. 3
    Connect OpenAIModels, embeddings, files.
  4. 4
    Connect Google DriveDocs, sheets, slides, files.
  5. 5
    Connect SlackChannels, DMs, threads, mentions.
  6. 6
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  7. 7
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  8. 8
    Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.

Run this workflow in your colony.

14-day trial. No DevOps. No Sales call. Provisioned in under a minute.