SUMMARIZATION

Meeting Digest with Follow-Up Email and Linear Issues

After a recorded meeting, emails attendees a clean recap and files any engineering action items as Linear issues routed to the right team.

CategorySummarization
Enginesim
Difficultyadvanced
Triggerevent
Steps5
Setup~25 min

How it runs

The automated pipeline, trigger to output.

  • TriggerZoom recording completedZoomZoom
  • ActionSummarize recap + classify action itemsOpenAI
  • LogicRoute engineering items vs. notes
  • ActionCreate routed Linear issuesLinearLinear
  • OutputEmail recap with issue linksGmailGmail

What it does

Closes the loop after meetings two ways at once. From a finished Zoom recording it builds a readable recap and a structured action list, emails the recap to attendees so everyone has the same notes, and converts engineering-flavored action items into Linear issues on the correct team. People get their summary and the work gets tracked where engineers actually live.

When to use it

Use it for product and engineering meetings where some follow-ups are general (share notes) and some are real dev work that belongs in Linear. Best when you want a polished attendee email plus traceable issues without manual triage.

How it works

  1. 1A Zoom recording-completed event triggers the flow.
  2. 2Fetch the transcript and summarize it into a recap plus a classified action list.
  3. 3Branch each action item: engineering items go to Linear, the rest stay in the recap only.
  4. 4Create Linear issues for the engineering items on the routed team.
  5. 5Email the full recap, including links to any created issues, to all attendees.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect ZoomMeetings, recordings, transcripts.
  2. 2
    Connect OpenAIModels, embeddings, files.
  3. 3
    Connect LinearIssues, projects, cycles, triage.
  4. 4
    Connect GmailRead, draft, send, label.
  5. 5
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  6. 6
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  7. 7
    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.