Send teammates a briefing before every meeting starts

Fifteen minutes before each meeting, attendees get a Slack DM with relevant notes, pull requests, and tickets.

How the work actually flows

It branches. Every path runs; all paths must finish before it continues; runs once per each meeting attendee.

Pattern: Parallel Split (2) · Synchronisation (3) · Multiple Instances with a priori Design-Time Knowledge (13)

flowchart TD trig>"new meeting created"]:::trig s0["pull notes from last meeting"]:::task s1["combine briefing"]:::task s2[["send briefing to attendee"]]:::mi trig --> s0 s1 -->|"one per each meeting attendee"| s2 gx{"+ gather context before meeting"}:::gate s0 --> gx p00["find related GitHub PRs"]:::task gx -->|"search pull requests"| p00 p10["find related Jira tickets"]:::task gx -->|"search tickets"| p10 jn{"+ briefing assembled"}:::gate p00 --> jn p10 --> jn jn --> s1 out[/"personalized briefing sent before meeting"/]:::out pay{{"attendees arrive with full context"}}:::pay s2 --> out out --> pay classDef task fill:#e7f6fe,stroke:#34b8f0,color:#2c2a29 classDef svc fill:#f6f8fa,stroke:#7c8795,color:#2c2a29 classDef mi fill:#e7f6fe,stroke:#0079a8,color:#2c2a29,stroke-width:2px classDef human fill:#fff,stroke:#0079a8,color:#0079a8 classDef store fill:#f6f8fa,stroke:#0079a8,color:#2c2a29 classDef trig fill:#00a4eb,stroke:#0079a8,color:#fff,font-weight:bold classDef trigtime fill:#00a4eb,stroke:#0079a8,color:#fff,font-weight:bold classDef trigdata fill:#8ad4f5,stroke:#0079a8,color:#06314c,font-weight:bold classDef gate fill:#fff,stroke:#e8a23d,color:#6b4708,font-weight:bold classDef out fill:#1f9d6b,stroke:#167a53,color:#fff,font-weight:bold classDef pay fill:#06314c,stroke:#021f33,color:#fff
Starts itA stepRuns once per itemEvery pathWaits for allResultPayoff
Build size
Advanced

A larger build with multiple systems, AI reasoning, and custom rules.

Business functions
Messaging & NotificationsProject & Task ManagementScheduling & CalendarDevOps & IT Operations
Connects
Google CalendarNotionGitHubJiraSlack

The problem it solves

Walking into a meeting without the context from last time, or without knowing what's already in progress, wastes everyone's time. Digging through Notion, GitHub, and Jira right before a call to catch up is a scramble nobody enjoys.

Who it fits

Engineering managers, product managers, and team leads who run recurring status or planning meetings.

How it works

  1. A new meeting is created on your Google Calendar
  2. The system pulls notes from the last related meeting in Notion
  3. Fifteen minutes before the meeting, it searches GitHub for relevant pull requests and Jira for related tickets
  4. A briefing combining notes, pull requests, and tickets is put together
  5. Each attendee receives the briefing as a direct message in Slack
What you get

Relevant notes and tickets ready before every meeting

Fifteen minutes before each meeting, every attendee gets a Slack message with relevant notes, pull requests, and tickets pulled together for them.

What you get

A personalized Slack briefing for every attendee, sent shortly before the meeting starts.

What you need

A Google Calendar account, a Notion account, a GitHub account, a Jira account, and a Slack workspace.

We can build this. But should you?

The hard question is not how to build it. It is whether this is the right thing to build first.

That is what a Fractional Chief AI Officer figures out with you, before anyone writes a line of code.

Let's Talk Strategy

Related automations

Back to the AI Playbook