Check the installed prerequisites
The selected catalog snapshot behind these cards was checked on 26 October 2026. Your owner or authorised installer should check the current store, minimum Core version, app grants, named connections, schedule and budget. The latest published app artifact and the version selected for customers can differ.
Selection is not installation. After installing the approved bundle, check its actual configuration and one normal output before relying on it. The sensor setup procedure gives the checks for each capture family.
Capture email and calendar events
Gmail Sensor reads new mail into the inbox capture area. Calendar Sensor reads events into a capture area (the meetings area in version 0.1.0, the inbox capture area in 0.1.1). Both use an owner-authorised, read-only Google connection and require compatible Core 0.18.5 or later.
Their selected defaults poll mail every 15 minutes and calendar events every 30 minutes. Inspect the installed schedule, choose the intended account and check a harmless new item. Neither sensor fetches or stores attachments. Depending on the installed version, the first runs can also import existing mail and events, not only new ones, and the folder Calendar saves to can differ, so check where your installed version puts its captures. Connect and check Google capture explains the account consent and saved-result checks.
Capture files and meeting notes
File Drop Sensor captures supported files placed in its drop folder into the inbox. Owners normally add files through the hosted file-drop page; an operator can also copy them into the same folder with SCP or SFTP. Its selected bundle requires Core 0.19.11 or later and the file-drop capture service. Word, Excel, PDF and PowerPoint conversion needs its output checked against the original. The Portal’s one-file upload is a separate route that does not need this sensor and does not convert those formats.
Granola captures meeting notes and transcripts into the inbox. It requires Core 0.20.2 or later and a named Granola connection. That connection needs a Granola Business or Enterprise plan and a personal API key with personal-notes scope; workspace keys do not work. Create it as an API-key connection named granola with base URL https://public-api.granola.ai, then grant it to the sensor; a connection label alone does not start capture. The sensor lists only notes that already have an AI summary and transcript, looks back seven days on its first run, polls every 30 minutes by default and shares a default quota of 200 calls a day on its connection, which a large backfill or very long transcripts can use up. A note edited after capture keeps its first captured version. Bring your first information in explains destination and review.
Capture Telegram chats
Telegram Sensor reads the messages its dedicated bot can see and proposes them into the inbox. It requires Core 0.20.8 or later and a named Telegram connection. It does not post or answer in Telegram. Each run captures at most 20 notes, and all its calls share one daily connection quota. Connect Telegram explains bot scope, protected token entry and the first capture check.
Draft briefings and review memory
Morning Brief drafts an owner-scheduled daily briefing from inbox updates. Weekly Review drafts a weekly review. Both require compatible Core 0.19.5 or later, access to their input and output areas, and an owner-approved model route and budget.
Memory Promotion Review supplies actions used by a memory-review loop and requires compatible Core 0.19.4 or later. It does not make every saved note eligible for automatic promotion. Check the installed action, memory-review area, model setup and actual review output. Control agent autonomy explains the limits around this work.
Share selected work with a peer
Network Flows supplies peer or group Share and contextual Reply actions, with review-held incoming flows. It requires compatible Core 0.20.2 or later plus enabled Network support, an accepted connection and the required grants. Connect Minds explains the relationship; share and reply explains delivery states.
Recognise source candidates and incomplete examples
SharePoint Sensor, SharePoint Mirror, Records Engine, Web Enricher, Company Models, Chief of Staff and Deal Review Loop appear in the source inventory but were not entries in this selected customer snapshot. SharePoint planning and import review explain the checks before arranging a supported route.
The selected Daily + Weekly Digest Relay sample supplies placeholder sentences to its donated actions. It is not offered here as a working AI summarisation tutorial. Use the separately configured scheduled briefing agents when those meet your verified job.
Related
Practical guides for people and agents