Choose the source and destination
Start with information that helps answer a real question. Decide which account or folder may be read, where captures should land and who may see that area. A source can contain confidential material even when the app only reads it. Zones and permissions explains how saved areas are separated.
The selected apps and sensors include Gmail, Calendar, Granola, Telegram and File Drop capture. Selection means an app is available to compatible Minds; it does not mean it is already installed or connected in yours.
Connect the account as its owner
In your Mind’s Portal, its web interface, open Settings, then Connections. The API-key form asks for a name, type, optional base URL and provider, and a secret. Use the exact connection name and provider specified by the app. Enter secrets into that protected form, not into a chat, record or file for an agent to read.
Google uses a separate owner consent flow for read-only Gmail and Calendar access. A disabled Google option in the API-key form does not perform that flow. Ask your connected agent to start the supported Google connection ceremony, then complete the account consent in your browser. The connection procedure gives the exact agent calls and the owner handoff.
After connecting, use Test where offered. A passing liveness test says the stored connection can reach the service. It does not prove a sensor has the connection, has run, or has produced a useful capture.
Install and grant the sensor
Have the authorised installer open Agents, choose the available store bundle and review its access, connection requirements and schedule. Installing an agent explains the approval and installation steps. Grant the named connection only to the app that needs it.
Check the installed schedule rather than assuming the store default was copied. The selected Gmail Sensor polls every 15 minutes, Calendar Sensor every 30 minutes, and Telegram Sensor every 10 minutes. A sensor that has been paused or has lost its connection will not provide continuous capture.
Upload one file directly
The Portal’s file-capture page lets you choose a file and Who can see it. Only me saves to your private space, which the Mind’s owner can also see. Team inbox submits a capture for inbox review. Choose the destination before selecting File capture.
Read the returned message. A file waiting for review has not become an approved shared source.
This route keeps text only from plain-text files, such as text, CSV, HTML, JSON, Markdown, TSV, XML and YAML, up to 10 MB. Very long text is cut off, and the saved note says so. For a Word, Excel, PDF or PowerPoint file, or any file that is not valid text, the saved note records only the file name, type, size and checksum and says that extracted text is unavailable. It does not save the original file, so keep the original and send it through the File Drop Sensor when you need Office or PDF conversion. This upload works without the File Drop Sensor installed.
Open the captured note after it is saved and compare any extracted text with the original, especially tables and long files.
Check a harmless first capture
Use a new test item in the approved account or folder. Wait for the installed sensor’s next scheduled run, inspect its outcome and open the resulting capture. Check source, date, text and destination. If it was held, review the proposed change before treating it as saved information.
Capturing material does not establish that it is true or current. An imported email remains evidence of what that email said. Decide what belongs in a current policy or decision separately, with its source attached.
From an external source to a checked record
Each stage answers a different setup question.
The owner connects the approved external account. The installer grants that connection to the intended sensor and checks its schedule. A normal run proposes a capture into its authorised destination. Inspect the proposal state, review it if required and open the saved record to compare it with the original source.
Stop or repair capture
If nothing arrives, check the installed app, schedule, connection grant, liveness result and waiting proposals in that order. A sensor only proposes captures. If its proposals repeatedly fail the automatic checks, its trust in that area can be lowered so that every later capture waits for review, so look in the review queue before assuming nothing was captured. Reconnect an expired service through its supported owner route. Do not paste credentials into a retry request.
Before removing a connection, inspect the apps using it and pause or reconfigure the affected work. Removing a connection with active grants is refused unless an owner explicitly chooses the supported grant-revocation route. Interrupted work explains how to inspect an uncertain result before repeating it.
Related
Practical guides for people and agents