## For agents - What Mensara is: it gives a team its own Mind, one shared memory for the team and their AI agents, built by Xanadu Labs LLC. - Status: signup is not open. A person joins the waitlist at https://www.mensara.ai/#waitlist. Agents cannot create an account or sign up. - How you can help your person: explain what Mensara does, check whether it fits a job their team repeats, and share the waitlist link. - Agent references: https://www.mensara.ai/llms.txt lists every page as Markdown and the tool input references for connected agents. --- # Install a selected sensor and verify capture Content updated 29 October 2026. Operating procedures · For agents and technical readers · [How it works](https://www.mensara.ai/how-it-works) Check the exact selected bundle, required connection and normal scheduled output without treating store selection or a liveness probe as capture acceptance. [Page as Markdown](https://www.mensara.ai/how-it-works/sensor-setup-procedure.md) [Human guide](https://www.mensara.ai/how-it-works/connect-telegram) ## Use the released interface with current authority Availability: Core0.20.11 / Portal0.3.47 source checked; discover the actual installed client and enabled features. Who can do this: The connected principal with the permissions named in this procedure What changes: The procedure explains its actual reads, writes or external effects before action. Limits: An input accepted by a source schema is not a successful installed-runtime task.; Keep human decisions, client exclusions and pending results explicit. Verification: Source checked and independently reviewed; scoped runtime receipts are recorded separately. ## Compatibility and scope Use an owner or authorised installer for installation, and owner authority for service connections and app grants. Discover `list_available_apps` and the current store route rather than naming an unpublished source bundle. Minimum Core versions in the selected snapshot: Gmail/Calendar 0.18.5, File Drop 0.19.11, Granola 0.20.2 and Telegram 0.20.8. The app’s read-only external behaviour can still propose saved information and move external content into the Mind. Agree source account/folders, destination area, visibility and review policy first. ## Inspect and install 1. Discover the intended Mind/principal with `orient {}`. 2. Inspect the current selected store bundle, version, minimum client release, declared zones, actions, connections and schedule. 3. Complete its supported owner connection ceremony. Use [connect-source-procedure](https://www.mensara.ai/how-it-works/connect-source-procedure) for Google or API-key sources. 4. Review and install the exact approved store offer through **Agents → Agent store** or the supported lifecycle route. Do not install a source checkout to bypass store availability. 5. Inspect the installed app with `list_available_apps {}`. Grant only the named connection and inspect its saved grant. ## Select the capture family **Gmail Sensor:** named `google` connection, inbox capture destination, selected default every 15 minutes. Check new authorised mail, not an old item that may be outside the sensor’s cursor. Attachments are never fetched or stored, and a published later version also imports the account’s existing mail on its first runs, so confirm which version is installed. **Calendar Sensor:** named `google` connection, selected default every 30 minutes. The selected snapshot saves to the meetings capture destination; a later published version saves under `01-inbox/captures/calendar` instead, so read the installed bundle’s declared zone first. Check an event visible to the intended authorised account and inspect its date/time. **File Drop Sensor:** installed file-drop capture service, inbox destination, selected default every 10 minutes. It watches the runner-managed `/work/drop` folder. Owners normally use the hosted file-drop page; an operator can place files in the folder with SCP or SFTP. Use a disposable supported text/Office/PDF/PowerPoint file and compare converted text with the original. The Portal upload form is a distinct route that does not use this sensor: it has an explicit private/team destination and its own returned status, keeps text only from plain-text files up to 10 MB, and records only the name, size and checksum for Office, PDF and other binary files. **Granola:** named `granola` connection and compatible bundle. The connection is an `api_key` connection with base URL `https://public-api.granola.ai`, holding a personal API key with personal-notes scope from a Granola Business or Enterprise plan; workspace keys do not work. No token or configuration is inferred from the name. Inspect the installed schedule (30 minutes by default) and a fresh meeting note that already has an AI summary and transcript. The first run looks back seven days, the connection’s default quota is 200 calls a day, and a note edited after capture keeps its first version. **Telegram Sensor:** dedicated bot and named `telegram` connection. Follow [the bot setup guide](https://www.mensara.ai/how-it-works/connect-telegram). Selected default every 10 minutes, at most 20 notes per run. Do not print, request or accept the token in the agent conversation. If every capture from a sensor is held, check the review queue and the app’s trust before debugging the source. A sensor only proposes, and repeated automatic-check failures lower its trust so its later captures wait for review. ## Observe a normal run Create one harmless input in the approved source. Wait for the installed schedule, then inspect the existing run result and proposed or saved capture. Where permitted, `list_files` uses `dir`, not `path`: ``` {"dir":"01-inbox/captures/telegram"} ``` Use the actual authorised destination, then `read` the capture. If held, inspect and decide the original proposal through the reviewer’s supported route. Read the saved record after application. Verify text, source identity, date, destination and exclusions. ## Failure and resumption Inspect schedule, active/suspended state, connection grant, connection liveness, run error and waiting proposals. A failed run or a missing result is not an empty source. Reconcile the original capture/run before repeating input. Telegram cannot recover updates older than its upstream retention window, and media markers do not establish downloaded files. Stop affected recurring work before correcting persistent bad scope or mapping. Keep app version, run reference and bounded error. Avoid tokens, original private bodies and recovery material in diagnostics. ## Related - [Bring email, calendar events and files into your Mind](https://www.mensara.ai/how-it-works/connections-and-capture) - [Choose an app, sensor or connector for your Mind](https://www.mensara.ai/how-it-works/apps-sensors-connectors) - [Install an approved agent and check its first result](https://www.mensara.ai/how-it-works/install-an-agent) - [Read, correct and verify memory](https://www.mensara.ai/how-it-works/correct-memory-procedure) [Join the waitlist](https://www.mensara.ai/?guide_attribution=eyJfcmFpbHMiOnsiZGF0YSI6eyJvcmlnaW5fcGF0aCI6Ii9ob3ctaXQtd29ya3Mvc2Vuc29yLXNldHVwLXByb2NlZHVyZSIsImN0YV9pZCI6Im1hcmtkb3duIiwiY29udGVudF9yZXZpc2lvbiI6IjQ5NjMwODg2NmNmMjdhZGUifSwicHVyIjoiZ3VpZGUtY2xpY2sifX0%3D--d2a7f96da411d41b5d19c3bfe5e61c6b34c1a51a#waitlist)