For agents and technical readers

Install a selected sensor and verify capture

Check the exact selected bundle, required connection and normal scheduled output without treating store selection or a liveness probe as capture acceptance.

Contents

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 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.

Calendar Sensor: named google connection, meetings capture destination, selected default every 30 minutes. 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. Use a disposable supported text/Office/PDF/PowerPoint file and compare converted text with the original. The Portal upload form is a distinct route with explicit private/team destination and its own returned status.

Granola: named granola connection and compatible bundle. Have the owner use the actual supported provider setup; no token or configuration is inferred from the name. Inspect the installed schedule and a fresh meeting note/transcript capture.

Telegram Sensor: dedicated bot and named telegram connection. Follow the bot setup guide. Selected default every 10 minutes. Do not print, request or accept the token in the agent conversation.

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 · Choose an app, sensor or connector for your Mind · Install an approved agent and check its first result · Read, correct and verify memory

Practical guides for people and agents

Start with one useful job

Join the waitlist

Plain text for AI agents. Same content as the human page.

## 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://app.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://app.mensara.ai/llms.txt lists every page as Markdown and the tool input references for connected agents.

---

# Install a selected sensor and verify capture

Operating procedures · For agents and technical readers · [How it works](https://app.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://app.mensara.ai/how-it-works/sensor-setup-procedure.md)

[Human guide](https://app.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://app.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.

**Calendar Sensor:** named `google` connection, meetings capture destination, selected default every 30 minutes. 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. Use a disposable supported text/Office/PDF/PowerPoint file and compare converted text with the original. The Portal upload form is a distinct route with explicit private/team destination and its own returned status.

**Granola:** named `granola` connection and compatible bundle. Have the owner use the actual supported provider setup; no token or configuration is inferred from the name. Inspect the installed schedule and a fresh meeting note/transcript capture.

**Telegram Sensor:** dedicated bot and named `telegram` connection. Follow [the bot setup guide](https://app.mensara.ai/how-it-works/connect-telegram). Selected default every 10 minutes. Do not print, request or accept the token in the agent conversation.

## 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://app.mensara.ai/how-it-works/connections-and-capture)
- [Choose an app, sensor or connector for your Mind](https://app.mensara.ai/how-it-works/apps-sensors-connectors)
- [Install an approved agent and check its first result](https://app.mensara.ai/how-it-works/install-an-agent)
- [Read, correct and verify memory](https://app.mensara.ai/how-it-works/correct-memory-procedure)

[Join the waitlist](https://app.mensara.ai/#waitlist)