IT OPS

Teams Meeting Triage: Route Action Items by Urgency

Transcribes a finished Microsoft Teams meeting, scores each action item by urgency, and routes high-priority items to PagerDuty while logging the rest as Trello cards.

CategoryIT Ops
Enginesim
Difficultyadvanced
Triggerevent
Steps6
Setup~25 min

How it runs

The automated pipeline, trigger to output.

  • TriggerTeams recording availableMicrosoft Teams
  • ActionFetch meeting transcriptMicrosoft Teams
  • ActionExtract items with urgency scoreOpenAI
  • LogicBranch on urgency level
  • ActionEscalate critical items to PagerDutyPagerDutyPagerDuty
  • OutputLog remaining items as Trello cardsTrelloTrello

What it does

Applies triage logic to meeting outcomes. It transcribes a Teams recording, extracts action items, and scores each by urgency. Time-critical items get escalated to PagerDuty for on-call attention; everything else becomes a Trello card on the team board.

When to use it

For operations and incident-review meetings where some follow-ups are genuinely urgent and others are routine. Stops critical items from being buried in a flat task list while keeping the board tidy.

How it works

  1. 1A Microsoft Teams recording-available trigger fires after the meeting.
  2. 2The transcript is retrieved from the meeting record.
  3. 3An OpenAI call extracts action items, each with an owner and an urgency score from low to critical.
  4. 4A logic step branches on the urgency score.
  5. 5Critical and high items create a PagerDuty incident routed to the on-call team.
  6. 6Remaining items are created as Trello cards on the team board, and a summary of the routing is returned.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect Microsoft TeamsChannels, chats, files.
  2. 2
    Connect OpenAIModels, embeddings, files.
  3. 3
    Connect PagerDutyIncidents, on-call, escalations.
  4. 4
    Connect TrelloKanban boards for everything.
  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.