Agent connectors: Slack & Notion

Table of contents

• How do I connect Slack to Leapsome AI features?
• What are external context sources?
• How do I enable external context sources for my organization?
• How do employees set up external context sources?
• How does the review assistant use Slack context?
• What can the AI assistants do with Slack and Notion data?
• How to reconnect Slack or Notion account
• FAQ

How do I connect Slack to Leapsome AI features?

Leapsome's AI assistants (the Review assistant and Leapy) can use context from tools your team already works in, like Slack and Notion. To do this, employees connect their own personal Slack or Notion account in their personal settings. The assistants can then search and read relevant messages or pages for them, so they no longer need to switch apps or copy and paste information manually.

Connection is personal: each user links their own account, and the assistants only ever see content that user can already see in Slack or Notion. An admin needs to enable the integration for the organization first.

What are external context sources?

External context sources are third-party tools employees connect to Leapsome so its AI assistants can pull in relevant information on demand. Slack and Notion are the first available sources. Each personal connection is used only when that user works with an AI assistant. It does not change what Leapsome stores or what colleagues can see.

How do I enable external context sources for my organization?

Three settings work together. All three are required before anyone in your organization can use Slack or Notion with the AI assistants:

1. Assign the Connect personal MCP permission to the users who should be able to link their own accounts. This is the only permission needed. Users without it do not see the connection option anywhere.

2. Enable the source under Agent connections for at least one AI assistant, for example the review assistant or Leapy. This controls which assistants may use the source. Note that this step will likely be simplified soon.

3. Let users connect their own accounts in personal settings (clicking on the user's name at the top right, and selecting 'Personal settings'). Each user links their own Slack or Notion account individually.

Enabling a source does not connect anything on behalf of your employees. Each user connects their own personal account, and the assistants only ever see content that user can already see in Slack or Notion. If any of the three settings is missing, users will not see the option to connect, and the assistants fall back to Leapsome data only.

How do employees set up external context sources?

How do employees connect a personal Slack account?

1. Click on your name > select 'Personal settings' and go to the external context sources section.
2. Find Slack in the list of available sources.
3. Click 'Connect' and complete the Slack authorization in your browser.
4. When the connection is successful, the status shows 'Connected'.

One Slack connection per user is enough. All AI assistants that have the source allowed under Agent connections use the same personal connection. There is no separate setup per assistant.

Users can disconnect at any time from the same place. Disconnecting revokes Leapsome's access to their Slack account and removes the stored connection.

How do employees connect a personal Notion account?

The steps are the same as for Slack:

1. Click on your name > select 'Personal settings' and go to the external context sources section.
2. Find Notion and click 'Connect'.
3. Complete the Notion authorization in your browser.

How does the review assistant use Slack context?

When a reviewer starts the review assistant with Slack connected, it automatically searches for relevant Slack messages about the reviewee, for example:

• Messages the reviewee wrote, such as project updates and announcements
• Messages where the reviewee was mentioned
• Direct messages between the reviewer and the reviewee (for manager and peer reviews)

The search covers the review cycle's time window. The assistant filters the results and keeps only messages that help answer the review questions. These messages are added to the conversation as supporting evidence, each with a link to the original Slack message so the reviewer can verify the source. Reviewers do not need to search Slack manually.

What can the AI assistants do with Slack and Notion data?

Once connected, employees can ask the review assistant or Leapy to find information for them, for example:

• "Find messages about the billing migration in #project-billing"
• "What feedback did I share with Alex in our DMs?"
• "Summarize what was discussed about this project in Slack"
• "Find the Notion page where we documented this launch"

With Leapy, users can also combine fetched context with other Leapsome actions, for example:

• "Read our strategy document in Notion and create a goal from it"
• "Summarize the discussion about this project in Slack and turn it into a talking point"

The assistants use search and read tools:

• Search: they find relevant messages, channels, people, or pages based on the question
• Read: they can open a specific thread or channel to get more detail when the search results are not enough

Keep in mind:

• Access is read-only. The assistants cannot post, edit, or delete anything in Slack or Notion.
• Slack and Notion content is treated as external, supporting evidence. The assistants cite it with links, and they ask the user to confirm or elaborate rather than treating a message as a complete fact.
• The assistant only sees what the connected user's own Slack or Notion account can see. It does not crawl the whole workspace.
• Fetched Slack and Notion content is not stored on Leapsome's side. It is used within the user's conversation history only and is not copied anywhere else in the workspace.
• If no relevant messages are found, the assistant says so and continues with Leapsome data.

How to reconnect Slack or Notion account

If a user's token expires or access is revoked, the status in their personal settings changes to 'Needs reconnect'. The assistant also tells them when a connection needs attention instead of failing silently.

To reconnect, users go to their personal settings, open the external context sources section, and click 'Connect' again for the affected source. If a source is disabled for the organization, the assistants fall back to Leapsome data only.

FAQ

Can the assistants see employees' private messages?

With a personal Slack connection, the assistants can access the same content the user can see in Slack, including direct messages they are part of. This is why the connection is per user: a colleague connecting their own account sees only their own Slack. Admins can restrict which sources are enabled, and the assistants only fetch content when it is relevant to what the user is working on.

Does connecting Slack give Leapsome access to post messages on an employee's behalf?

No. The connection is read-only. The assistants can search and read, but they cannot write, post, or edit anything in Slack or Notion.

Do employees need to connect Slack separately for the review assistant and for Leapy?

No. One personal connection per source is used by all AI assistants that are allowed to use it under Agent connections.

Is employee Slack or Notion data stored in Leapsome?

No. Content from external sources is retrieved on demand and used only within the user's conversation history. Leapsome does not store fetched Slack or Notion data anywhere else on its side, and nothing is copied into the Leapsome workspace.

Can admins see what employees searched for in Slack?

Connections and searches are tied to each user's own account. Admins control whether the integration is enabled and who may connect accounts, but they do not use employee connections.