Skip to content
LVIS AI
EN|KO

Event-driven flow

Meeting End → Action Item Extraction (Not a Routine)

This flow is handled by work-assistant's meeting-summary detector, not RoutineEngine — when the meeting plugin emits meeting.summary.created, the detector decides whether to surface it and shows the user a card.

event-driven
meeting.summary.created
meeting-summary-detector
Meeting-end trigger — action items extracted automatically
Converting extracted action items into TODOs/emails

One cycle

  1. 01

    Meeting end detected

    meeting

    The meeting plugin emits meeting.ended on user stop / floating window close → the full transcript is saved to SessionStore.

  2. 02

    Summary generated

    The meeting plugin summarizes the transcript and extracts actionItems using the host LLM (callLlm). The result is emitted as meeting.summary.created.

  3. 03

    Work Assistant detector kicks in

    work-assistant

    On the plugin side, src/decision/meeting-summary-detector.ts subscribes to the event. It evaluates policy (allow-listed domains, etc.) and then decides whether to surface it. That path is in the plugin's own repository, not the host repository.

  4. 04

    Proactive card

    When surfacing is decided, hostApi.triggerConversation shows a card in the chat body. User options are displayed (TODO / mail / save summary).

  5. 05

    Follow-up action

    Final

    Once the user chooses, work-assistant carries out the actual task using ms-graph tools (e.g. adding a calendar entry, creating a work-board card).

To turn this flow off
  • Plugin level: set meeting autoSummarize=false to block the summary itself.
  • Detector level: work_assistant_set_detector_enabled({ id: 'meeting-summary', enabled: false })
  • Config level: an empty meetingDetectorAllowedSenderDomains array means fail-closed.
Previous

Routine Setup & Trigger Flow

Next

What Is a Plugin?