Integrations

An integration is a connection to one of your tools, such as your mailbox, Google Drive or GitHub. Once it is connected, June can look things up there and do work there when you ask, as you and within what you allowed.

Changes ask for approval by default. Saved permissions can allow later changes without another card; organization rules can still require approval or block a change. See Approvals.

Integration	Reads	Writes	Never	In organizations
Mailbox (Gmail or IMAP)	your mail	drafts; Gmail sends and Gmail or IMAP inbox changes	sends from IMAP or permanently deletes mail	personal only until you change it
Microsoft 365	Outlook mail and calendar, Teams chats, OneDrive and SharePoint files	drafts and forwards; approved sends, inbox changes, events, Teams messages, file and saved-contact writes	permanently deletes mail or files; changes Teams messages; invites someone you did not name	personal only until you change it
Google Drive	Docs, Sheets, Slides, PDFs, Office and text files, comments	saves files; edits Docs and Sheets, changes and shares files	edits Slides or permanently deletes files	every organization you're in, unless Personal only
Google Calendar	your calendars and events	events and invitation replies	invites someone you did not name	personal only until you change it
Google Contacts	your contacts, the people you have mailed, your Workspace directory	saves or changes a contact, adds contacts to a group	deletes a contact or changes anyone you only mailed	personal only until you change it
Google Search Console	search performance, index status, sitemaps	submits or removes a sitemap, adds a property	removes a property or changes a setting	every organization you're in, unless Personal only
GitHub	code, issues, pull requests	comments, reviews, issues, pull requests, pushes	reaches beyond your account	as you, including code changes in June’s chats
Notion	the pages and databases you share	new pages and rows, values, appended content; comments, block edits and removals	permanently deletes content or removes a database	every organization you're in, unless Personal only
Obsidian	the notes in your vault	note edits, pushed to the vault	force-pushes	your own chats only
ownCloud and Nextcloud	your files	uploads, moves and renames files; deletes	reaches beyond your account	your own chats only
Tailscale	the devices on your tailnet	what those devices let your account change	changes your tailnet's settings	your own chats only
X	posts, mentions, bookmarks, your posts' analytics	posts, replies, likes, bookmarks and follows	sends direct messages	every organization you're in, unless Personal only
Any MCP server	what its tools read	what its tools write	answers a server’s questions while a tool runs	every organization you're in, unless Personal only

June reads a tool when you ask, or when a schedule you set up runs with its integrations toolset on (what a run can use); it does not watch your tools on its own. Without integrations June can still talk things through, search the web, draft and remember.

Connect a tool

Open the Integrations page from the sidebar.

Find the tool. Most are rows in the connections table: choose Connect on the row and sign in to the tool. Mailbox, Obsidian, ownCloud and Tailscale are cards below the table; open the card and fill in its form.

When you come back, the row's status reads Connected. Ask June something that needs the tool.

The table lists every connection you have, with its status, the number of tools it gives June and when it was last checked. A connection whose sign-in has lapsed reads Re-auth required; choose Re-auth on its row to sign in again. To remove one, choose Disconnect in the row's menu; June stops using it at once.

You can also connect from a chat: when June needs a tool you have not connected, it sends you the link.

To connect a second account of a tool, choose Add integration: under Already set up it lists every integration you have, and Connect another beside one opens its page, where the new account gets its own name.

With more than one account of a tool, say which one you mean, by its connection name or its address. June knows each connection's name and the account it is signed in as in chat, in Slack and in schedules alike (whose sign-in June uses).

Slack is where you talk to June rather than a tool it uses; you install it from the Slack card on the same page. See Use June in Slack.

Personal or organization

Where you connect a tool decides where June uses it. A connection remains yours: making it available in an organization does not sign other members in to your account.

• Connected in your personal space, from the Integrations page, a connection works in your own chats and in every organization you belong to, from its first message, with nothing to reconnect.
• Connected inside an organization, from the organization's Integrations section or a link June sends in one of its chats, a connection works only in that organization and is removed when you leave it.

The Used in column shows where each connection reaches: Personal only, Personal also in your organizations, or one organization's name for a connection made inside it. To keep a personal connection out of your organizations, tick Personal only in its row's menu or on the Mailbox page. A connection made inside an organization has no such switch: to use that account everywhere, connect it on the Integrations page. Mailboxes, Microsoft 365, Google Calendar and Google Contacts start as personal only, so your mail, calendar and contacts never reach a company's chats unless you say so.

On an organization's page, Use work account connects an account used only there, and Use in all my organizations lets a connection you kept personal reach your organizations after all. Its admins can offer custom MCP servers there, and each member connects their own login to them (Custom MCP servers). X connects only in your personal space, and then reaches your organizations like any other connection.

Obsidian, ownCloud and Tailscale run in June's sandbox as you, so June uses them only in your own chats and projects (why). GitHub's git and pull request work runs there too: in an organization's chats it signs in as whoever wrote the message, with the GitHub they can use in that organization. Whose sign-in June uses has the rules for every place, schedules and steering included.

Anything else

Services without their own integration reach June through their MCP server: see Add any MCP server.