Skip to content
LVIS AI
EN|KO

Host · Integration Recipes

A Collection of Plugin Combination Scenarios

What matters more than using a single plugin is the 'chain' where several plugins work together. This page lays out four commonly used combination scenarios as short flows. Every chain goes through a user consent card, and any step that runs automatically is marked explicitly.

Meeting + Work Assistant + MS-Graph
Local Indexer + Meeting + Agent Hub
MS-Graph + LGE EP
Agent Hub + Meeting + EP

Recipe 1 — Meeting → Action → Schedule → Reply

The most frequent chain. Decisions made in a meeting flow naturally into a schedule entry and a reply.

  1. 01

    Meeting ends

    Meeting

    The Meeting plugin ends the recording → automatically extracts meeting notes and candidate action items.

  2. 02

    Follow-up card appears

    Work Assistant

    Work Assistant surfaces the action item candidates as a user confirmation card. Choose from "add as TODO / reply by mail / add to schedule."

  3. 03

    Schedule entry + reply draft

    MS-Graph

    If the user picks "schedule + reply" → the event is added to the Microsoft 365 calendar, and a reply draft appears in chat. It is only actually sent the moment "Send" is pressed.

  4. 04

    Records preserved

    Every step is logged in the audit trail, and extracted action items are also synced as work-board cards.

Minutes to Outlook draft 1 — automatically drafts a share email addressed to attendees
Minutes to Outlook draft 2 — sent after the user confirms

Recipe 2 — From "Where was that file?" to a Presentation Slide

The Local Indexer is the core here — one flow from search, to path lookup, to content summary, to a presentation-ready reformat.

  1. 01

    Natural language search

    Local Indexer

    Ask in chat, "where was the material about OOO?" → Local Indexer answers with candidate files and its reasoning.

  2. 02

    Path lookup

    Ask for the "exact file path" → the absolute path (including NAS mounts) is printed as-is. Open it directly from the OS file manager.

  3. 03

    Summarize + reformat

    Reused

    On the same file, ask to "format this into one slide for a presentation" → the host LLM reuses the same match result and reformats it for a presentation.

  4. 04

    Send to a work-board card

    Agent Hub

    Register the summary as a "prepare presentation material" card on the Agent Hub work board to share with the team.

Recipe 3 — All the Way to Booking an Internal Meeting Room

The chain that links ordinary meeting scheduling to the internal portal. Works only inside the internal network.

  1. 01

    Meeting request mail arrives

    MS-Graph

    Microsoft 365 detects a new meeting request. Candidate times are extracted from the body.

  2. 02

    Available room suggested

    Work Assistant

    Work Assistant checks the user's calendar together with room availability from the internal system, then surfaces a candidate card.

  3. 03

    Room booked + video call added

    LGE EP

    The chosen room is confirmed with LGE EP's room booking tool. If there are external attendees, a video call link is generated automatically and attached to the event body.

  4. 04

    Reply sent

    Sent after confirmation

    A card showing "booking complete + room + video call link" is shown to the meeting requester in chat → it is only actually sent the moment the user presses "Reply."

Recipe 4 — Video Call → Automatic Meeting Notes → Team Board

Wrapping up a meeting with external attendees. Notes, action items, and team sharing, all in one pass.

  1. 01

    Join the video call

    LGE EP

    Start the video call from the link attached to the event — LGE EP's video call flow.

  2. 02

    Automatic meeting notes

    Meeting

    During the meeting, the Meeting plugin runs live transcription. On end, it automatically generates notes, a summary, and action items.

  3. 03

    Distributed to the team board

    Agent Hub

    Action item cards are registered automatically on the Agent Hub work board. Candidate assignees are filled in automatically, and cards nearing their deadline are sent as notifications.

  4. 04

    Notes stay in their own area

    Only on your PC

    The original meeting notes are kept only inside the Meeting plugin's own area. They are not automatically sent to an external server.

Make a recipe your own
Each recipe can be registered as an "automation rule." When a trigger arrives — a meeting ending, new mail arriving, a specific time — the host fires the same flow automatically, and the user only needs to check the resulting card.
Every chain goes through a consent card
Separately from the word "automation," risky steps (sending mail, calling external services, submitting an approval) always go through a consent card. Being registered under automation once does not mean risky steps afterward are handled without asking.