OppermindDocs
Try Oppermind
Sign inTry Oppermind

Customize

Connectors

Bring approved context and actions into Oppermind from the tools your team uses.

On this pageWhat connectors doAuthorize the smallest useful scopeUse approvals for consequential actionsRemove access when it is no longer neededAttach a connector to a turn

What connectors do

A connector can give Oppermind access to relevant information or actions in another service. Capabilities depend on the service and granted permissions.

Lato reads through the connector and answers in chat; what it can touch is set by the permissions you granted.
Try this
✦With Gmail connected and its connector chip attached, ask: Find the last three emails from our accountant about the BAS lodgement and summarise what she is still waiting on from us.
What you getOppermind reads the matching messages through the connector and lists the outstanding items in chat; what it can read or do depends on the permissions you granted when connecting.

Authorize the smallest useful scope

Connect only the sources and actions required for the workflow. Review what Oppermind can read, create, or change.

Settings → Connectors showing connected services and the catalogue of available connectors.
Connect and disconnect services in Settings → Connectors.
Try this
✦Open Settings from the avatar, choose Connectors, and connect Notion only because the tender team needs Oppermind to read the shared Tenders workspace. Do not connect email or a project tracker for this job.
What you getThe Notion card switches to Connected and shows the account it is connected as and its last sync, so you can confirm the access matches the tender job and nothing more.

Use approvals for consequential actions

Require review before sending messages, publishing content, changing records, or sharing sensitive material.

The draft lands in chat, not Slack; posting waits for your go and the connector's permission.
Try this
✦With the Slack connector chip attached, ask: Draft a message for the #customers channel about tomorrow's 2am maintenance window. Show me the draft here first and do not post anything until I say go.
What you getThe draft appears in chat rather than in Slack, and nothing is posted unless you approve it in a later turn and the connector's permissions allow the action.

Remove access when it is no longer needed

Review active connectors regularly and disconnect services that no longer support a current workflow.

After Disconnect, the service is gone from the composer's Connectors tab and Lato cannot reach it.
Try this
✦Open Settings, choose Connectors, find the project-tracking connector you set up for last quarter's data migration, and click Disconnect. Confirm when Oppermind asks Disconnect this integration?
What you getThe card returns to its unconnected state, and that service is no longer offered as a connected source in the composer's Connectors tab for future turns.

Attach a connector to a turn

Open the composer plus menu, choose Connectors, select the connected service, and confirm its connector chip. Remove it when the next request does not need that live context.

Attach a connector to a turn from + → Connectors.
Every attached item shows as its own chip, so you can see exactly what shapes the next message.
Try this
✦Click +, open the Connectors tab and select GitHub, confirm the connector chip, then ask: List the pull requests opened on the storefront repo this week that still have no reviewer. After the answer, close the chip before your next, unrelated question.
What you getThe connector chip shows the turn will include live GitHub context; removing it means your next message, say about a marketing email, is answered without repository data in the prompt.
◎
GUIDED LEARNING

Practise this in Oppermind Academy

Follow the related tutorial or course and apply the concept to a real task.

Open learning path