Meeting Prep: Pull Context Before Every Call

For an operator who runs 4–8 meetings a day and walks into most of them cold. Five minutes before each meeting, delivers a one-pager with attendee names + roles, last 3 emails with them, open Jira tickets, and recent Slack context.

Google Calendar logoGoogle Calendar
Gmail logoGmail
Slack logoSlack
Jira logoJira
Confluence logoConfluence
THE GRIND

Walking in cold

Here's what doing this by hand looks like today — and why it doesn't scale.

4–8 meetings a day and you prep for maybe one of them

Context lives across Gmail, Slack, Jira — never in one place

The 'who are they again?' moment in the first 30 seconds

Composio collapses all of this into one prompt — here's what that looks like.

THE FLOW
9 steps · 5 toolkits

Your agent runs it end-to-end.

  1. 01
    List upcoming calendar events in the horizon
    googlecalendar logo
  2. 02
    Extract attendee emails (skip room resources and internal auto-invites)
  3. 03
    For each external attendee, pull their most recent email thread
    gmail logo
  4. 04
    Fetch the body of the latest thread for context
    gmail logo
  5. 05
    Find open Jira tickets assigned to or reported by the attendee
    jira logo
  6. 06
    Search recent Slack messages with the attendee
    slack logo
  7. 07
    If the meeting references a project, pull relevant Confluence pages
    confluence logo
  8. 08
    Compose a one-pager per meetingAttendees + roles, last email thread subject + one-line summary, open Jira, recent Slack context, linked Confluence docs.
  9. 09
    DM the prep sheet to yourself before the call
    slack logo
THE PAYOFF

Walk in warm

Every call opens with a one-pager already in your DMs — no more cold starts, no more 'what was this about' in the first minute.

Paste this into Claude, Cursor, or Codex. It'll install the CLI, connect your apps, and run the task — end to end.