Use June in Slack

Add June to your Slack workspace and talk to it where your team already works: in a direct message for your own things, or in a channel thread when the work is shared.

On the Integrations page, open Slack.

If you administer an organization, choose under Belongs to whether the workspace is yours (Just me) or the organization's. Without an organization you administer there is no choice: the workspace is yours.

Choose Add to Slack and approve June for your workspace. Slack sends you back to June, with your Slack account linked to your June account, unless that Slack account is already linked to another June account; unlink it in that account's Settings first.

Open a direct message with June in Slack, or mention @June in a channel.

June is not in the Slack Marketplace; adding it from the Integrations page is the only way in.

Direct messages and channels

• In a direct message, June answers every message, with your own context, as in a chat on the web.
• In a channel, June answers only when someone mentions it. Mentioned partway through a thread, it first reads up to 50 replies from before the mention, the post that started the thread included, as text without their files, and skips messages from people outside your workspace. A post from an app or bot, such as a form or webhook card, reads with every field it shows. From then on it follows that thread: it reads the later replies, and answers again when it is mentioned again. Each time it is mentioned it first catches up on the replies since it last read the thread, up to 15 at a time, so an app's answer that Slack sent while June wasn't reading is still part of what June sees. An app that writes its reply as it goes is read once its reply is finished.
• When an app or bot mentions June, June reads that message as part of the thread but does not answer it or act on it. Only people in your workspace can ask June to do something.
• While June is working, mention it again to steer the reply it is writing.

While it works, Slack shows that June is typing, its reply arrives as it writes, and its steps show as they run. Once the reply is done, Slack's preview of it, in the Threads list for example, starts with June's answer, not with the names of its steps.

Steps that need your approval

Before June makes a change for you from Slack, such as sending an email, creating a calendar event, posting a message or changing a file, it posts a card in the thread, as a normal reply. Everyone in the thread sees it, the same people who saw your request: what will happen, the account it runs on, who it reaches, and the message or the change. A long message is cut on the card; View full opens it in June.

• Approve runs that one step, once, as shown, and Deny stops it. Your card then says what happened, the note in the thread says who decided, and June replies in the thread.
• Only the person whose account the change would use can decide it. The card identifies the approver; being able to read the thread does not give someone else permission to approve.
• Your next message to June in the thread cancels a card you left open, and so do 24 hours.
• Connected-service changes, including Gmail sends and Google Drive edits, can run after you approve the card in Slack. The thread gets a short result; links and service responses go privately to the approver in a direct message, or stay in the same conversation if the request was already a direct message.
• Where the action and your organization’s rules permit it, you can allow that kind of change for the thread or everywhere. Review the scope before choosing: a lasting permission can affect later requests too. Manage these rules in Approvals.

A step that needs your confirmation has the details.

Who can use it

That depends on who the workspace belongs to:

• A workspace that is yours (Just me): only you. Anyone else who asks June there is told to ask you to connect the workspace to an organization.
• A workspace that belongs to an organization: any full member of the Slack workspace who links a June account. Someone who has not linked one yet and mentions June gets a direct message with a link to connect, so the link never lands in the channel. Linking makes them a member of the organization, and members can read its public channel threads on the web. Direct messages and private channels stay with the people in them.

Memory in Slack

In a direct message June uses your personal memory, the same one as on the web. In a channel it keeps memory for the room, shared by every thread in that channel, and it does not save personal facts there; tell it those in a direct message.

In Slack, June saves a memory only when someone asks it to remember something; it does not look back over the conversation on its own as it does on the web. Which memory each place reads and writes has the details.

What June does not do in Slack

• It does not list Slack conversations in the web sidebar or the app’s chat list. Reply in Slack; an organization’s public channel thread can be read on the web by its members.
• It does not work for guests, or for people from other organizations in a shared channel.