SourceLace Docs
FAQOpen the app

Slack and Microsoft Teams

How to connect Slack and Microsoft Teams. SourceLace reads the channels, chats and direct messages each person is in, reads threads, searches messages, looks up people and reads files shared in conversations; in Teams it can also read meeting transcripts. If you allow it, it posts messages, creates channels, adds reactions and more, as the person, after they confirm a preview.

Status: Pilot. New or partial, offered to pilot customers. Built on Slack's Web API and Microsoft Graph's published Teams APIs.

At a glance

Connects through Sign-in Network Status First test question
Slack Slack Web API, with each person's own user token Personal sign-in Nothing to open Pilot "Show the last 10 messages in #general."
Microsoft Teams Microsoft Graph (Teams, chats, online meetings) Personal sign-in Nothing to open Pilot "Which teams and channels am I in?"

Add each source with the usual steps. The network answers are explained in What your network needs. If the first test question fails, the error message tells you what to fix: look it up under When something goes wrong below.

These sources let people read and draft in Slack and Teams. Separately, as an optional way to start your AI agents, people can type a Slack slash command or mention a Teams outgoing webhook: see Start from Slack or Teams.

What SourceLace can and cannot do

Kind Reads Changes Who signs in
Slack (slack) Conversations you are in, messages, threads, search, people, shared files Post or schedule a message or thread reply (messages), create a channel (channels), create a canvas or update one you created (canvases), add an emoji reaction (reactions), post files an agent made with a message (files) Each person, with their own Slack account
Microsoft Teams (microsoft_teams) Teams and channels you joined, your chats, messages, channel replies, search, people, shared files; with meetings on, your meetings, their transcripts and recording details Post a channel message, channel reply or chat message (messages), create a channel (channels), add a website tab (tabs), add a reaction (reactions), post files an agent made in a channel (files) Each person, with their own Microsoft work or school account
  • Only what you can see. SourceLace uses each person's own access (Slack user tokens, Microsoft Graph delegated permissions). There is no bot or shared account, so a person sees only the conversations they are a member of.
  • Nothing changes without you. Every change is off unless an admin allows changes to that object on the source. Each change is previewed (exactly what will happen, and where) and is made only after the person confirms. When the place is a public Slack channel, the preview says so and shows how many people are in it, with a reminder that anyone in the workspace can read it, so check that the text holds nothing the channel should not see.
  • Never: edit or delete messages (yours or anyone's); delete or rename channels, canvases, tabs or reactions; change a canvas someone else created; post or react in a conversation that includes people outside your organization (direct or group messages with outside people, Slack Connect channels, Teams shared channels and chats with other organizations); or post to a channel you have not joined. Teams cannot schedule messages, so SourceLace refuses that for Teams.
  • Searching everything. Where it is on, Searching everything also searches the messages you can see, with your own access, together with your other systems.
  • Not copied. Messages, files and transcripts are read when asked, held for up to 30 minutes for joins and charts (your admin can make this shorter), and never written to a database except inside a saved chat that shows them.

Slack

Kind: Slack (slack).

Add SourceLace to Slack

SourceLace is added to Slack in two parts: a SourceLace admin adds a Slack source, then each person signs in to Slack once. There is no bot to install and nothing to download. About 5 minutes.

  1. Add the Slack source (a SourceLace admin, once). Sign in to the SourceLace app, open Connections, add a source of kind Slack and save. The usual steps apply. Optionally enter your Workspace ID to accept only that workspace.
  2. Approve SourceLace in Slack if your workspace asks for it (a Slack admin). If Slack tells a person that an admin must approve the app, a Slack Workspace Owner or Admin opens Tools & settings → Manage apps and approves SourceLace. See What your admin does in Slack.
  3. Each person connects their own Slack account. In SourceLace, open My connections, find the Slack source and click Connect. Slack opens: choose your workspace and click Allow. SourceLace asks to act as you, with your own access, and only for the permissions listed below.
  4. Check that it worked. The Slack source shows as connected. Ask "List my Slack channels": you should see the channels and conversations you are in.

To stop, a Slack admin removes SourceLace under Manage apps in Slack; every person's connection ends at once. Questions: support.

How sign-in works. SourceLace has its own Slack app. Each person clicks Connect, chooses the workspace and allows SourceLace to see their conversations as them. SourceLace asks for these user scopes: channels:read, groups:read, im:read, mpim:read, channels:history, groups:history, im:history, mpim:history, search:read, users:read, users:read.email, files:read; and only for the objects you made writable: chat:write (messages), channels:write and groups:write (channels), canvases:write (canvases), reactions:write (reactions), files:write (files: an agent posting the files it made, see Sending files the agent made).

What your admin does in Slack

Nothing is registered unless you choose your own app (step 3). About 5 minutes.

Who: a Slack Workspace Owner or Admin; on Enterprise Grid, an Org Owner or Admin.

  1. Approve SourceLace if your workspace requires app approval. In Slack, Tools & settings → Manage apps (on Enterprise Grid, the Admin dashboard → Integrations → Apps Manager): when someone requests SourceLace, open the request and Approve. On Enterprise Grid, also allow it in each workspace that should use it.

  2. Write down the Workspace ID if you want to pin the source to one workspace: in a browser, open Slack; the address app.slack.com/client/T0123ABCD/... shows it (the part starting with T, or E for an Enterprise Grid organization).

  3. Optional: your own internal Slack app (avoids Slack's lower limits, below). At api.slack.com/apps, Create New App → From a manifest in your workspace, paste the manifest SourceLace support sends you, then under OAuth & Permissions → Redirect URLs add https://mcp.sourcelace.ai/connect/callback exactly. Copy the Client ID and Client Secret from Basic Information → App Credentials into the source. An internal app works only in the workspace it was made in: set Workspace ID to that workspace.

  4. Optional: let agents post files. Only when agents should post the files they make (a Word report, an Excel sheet) in Slack. Done by a SourceLace admin, plus a Slack admin if you use your own app:

    1. In SourceLace, Connections, open the Slack source, turn on Allow changes and add files to Objects that can be changed (next to messages, such as messages, files). Save.
    2. If you use your own internal Slack app (step 3): a Slack Workspace Owner or Admin opens api.slack.com/apps, the app, OAuth & Permissions → Scopes → User Token Scopes → Add an OAuth Scope, adds files:write, and clicks Reinstall to Workspace if Slack shows it. SourceLace's own app already has it.
    3. Each person who runs such an agent clicks Connect on the Slack source again and clicks Allow: Slack then shows "Upload, edit, and delete files on your behalf". SourceLace only uploads new files and never edits or deletes one.

Check that it worked: one person clicks Connect, chooses the workspace, clicks Allow, and asks for the last messages in a channel they are in. For files: run an agent that posts its file in a test channel; the run's Deliveries list says Sent and the file is in the channel.

Slack's own guide: Slack Help Center (search for "Manage app approval").

Slack's limits for apps outside its Marketplace. Since May 2025 Slack lets apps that are distributed commercially but not yet approved for the Slack Marketplace read a channel or thread only once a minute, 15 messages at a time. Searching is not limited this way. If this slows you down, your Slack admin can create your organization's own internal Slack app (SourceLace support sends the manifest) and enter its Client ID and Client Secret in the source's options: internal apps keep Slack's normal limits.

Option Example What it does
team_id T0123ABCD Optional (step 2). Only sign-ins to this workspace or Enterprise Grid organization are accepted.
client_id 1234567890.1234567890 Optional: your organization's own Slack app (step 3).
client_secret With client_id. Stored encrypted and never shown again.

Microsoft Teams

Kind: Microsoft Teams (microsoft_teams).

How sign-in works. Each person signs in with their Microsoft work or school account through SourceLace's Microsoft app (the same one as Microsoft sign-in, Outlook and SharePoint) and approves these delegated permissions: User.Read, offline_access, User.ReadBasic.All, Team.ReadBasic.All, Channel.ReadBasic.All, Chat.Read, Files.Read.All, ChannelMessage.Read.All; with meetings on, Calendars.Read, OnlineMeetings.Read, OnlineMeetingTranscript.Read.All and OnlineMeetingRecording.Read.All; and only for the objects you made writable: ChannelMessage.Send and ChatMessage.Send (messages, reactions), Channel.Create (channels), TeamsTab.Create (tabs).

What your admin does in Microsoft Teams

Nothing is registered: SourceLace provides the Microsoft app. About 5 minutes.

Who: a Microsoft Entra admin who may grant tenant-wide consent (Global Administrator, Cloud Application Administrator or Application Administrator), and a Microsoft 365 admin for licences.

  1. Decide what the source reads. With Read channel messages On (the default), sign-in asks for ChannelMessage.Read.All; with Read meetings and transcripts On, for OnlineMeetingTranscript.Read.All and OnlineMeetingRecording.Read.All; with tabs writable, for TeamsTab.Create. Microsoft always needs an admin's approval for these. With both set to Off, people can usually approve the rest themselves and read their chats.
  2. Approve SourceLace once. Connect once yourself and tick Consent on behalf of your organization, or open the Entra admin center → Enterprise applications → SourceLace → Permissions → Grant admin consent. If your organization turned off user consent, this approves every permission. When you later turn an option On, approve again: the new permission is added.
  3. Licences. Each person needs a licence that includes Teams (Microsoft 365 admin center → Users → Active users → the person → Licenses and apps).
  4. Transcripts. Transcripts exist only for meetings where transcription was turned on and your Teams meeting policy allows it (Teams admin center → Meetings → Meeting policies → Recording & transcription). Microsoft gives them for meetings the person organized, and may refuse them for meetings the person only attended.

Check that it worked: one person connects and asks for their latest chats; with channel messages on, for the last messages in a team channel.

Microsoft's own guides: Microsoft Entra documentation (search for "Grant tenant-wide admin consent") and Microsoft Teams admin documentation.

Option Choices What it does
channel_messages (Read channel messages) On or Off On by default. Off leaves out ChannelMessage.Read.All, so no admin consent is needed: people read and search their chats, but not channel messages.
meetings (Read meetings and transcripts) On or Off Off by default. On lets people read their Teams meetings, transcripts and recording details (needs admin consent for the transcript and recording permissions).

Optional: let agents post files in channels. Only when agents should post the files they make in Teams channels (not chats: a chat's files would have to be shared with each member one by one). About 5 minutes.

  1. A SourceLace admin opens Connections, the Teams source, and adds files to Objects that can be changed (next to messages). Save.
  2. SourceLace then also asks for the delegated permissions Files.ReadWrite.All (a channel's files live in its SharePoint folder, so the file is added there first) and ChannelMessage.Send. If your organization does not let people approve apps, an Entra admin opens the Microsoft Entra admin center: Enterprise applications → SourceLace → Permissions → Grant admin consent for your organization.
  3. Each person who runs such an agent connects Teams again and accepts.

Check that it worked: run an agent that posts its file in a test channel; the run's Deliveries list says Sent, and the file is in the channel's Files tab and in the post.

Queries

Both use the chat_json language: one small JSON object. Use describe_object for every key.

In Slack, conversation can be the channel's id (such as C0123ABCD) or its name as Slack spells it (such as csm-renewals-risk, with or without the # when posting). SourceLace looks the id up among the channels you are in.

Object Example
conversations {"object": "conversations", "types": ["public_channel", "private_channel"], "name": "sales"} (Slack types: public_channel, private_channel, mpim, im; Teams: channel, chat)
messages {"object": "messages", "conversation": "<id>", "after": "2026-10-01", "limit": 50}
replies {"object": "replies", "conversation": "<id>", "thread": "<thread column>"}
search {"object": "search", "text": "renewal", "from": "ann", "after": "2026-09-01"}
users {"object": "users", "text": "ann@corvanta.com"}
files {"object": "files", "conversation": "<id>"} (in Teams, conversation is required)
file_text {"object": "file_text", "file": "<id column of files>"}: the file's text in chunks, read on demand
meetings (Teams) {"object": "meetings", "after": "2026-09-01"} (default: the last 30 days)
transcript, recordings (Teams) {"object": "transcript", "meeting": "<id column of meetings>"}

Queries are checked before anything is sent: unknown keys, quotes, colons, brackets and ranges over a year are refused. At most 200 messages, 100 search results, 500 conversations or 200 people per query.

Changes, through propose_change (operation create unless noted):

Object Fields
messages conversation, text, optionally thread; Slack only: post_at (a time with a zone, at most 120 days ahead) to schedule it
channels name, optionally private (true or false); Teams: team (required) and description
canvases (Slack) title, markdown, optionally conversation for a channel's canvas; operation update with the canvas id replaces the markdown of a canvas you created
tabs (Teams) conversation (a channel), name, url (https)
reactions conversation, message, emoji (Slack: an emoji name such as thumbsup; Teams: like, heart, laugh, surprised, sad or angry)

When something goes wrong

Slack

What you see What it means What to do
"SourceLace found no channel called '...' among the channels you are in." The name is spelled differently in Slack, the channel is archived, or you have not joined it (SourceLace uses your own access). Check the spelling, join the channel in Slack, or use its id from a conversations query.
"Sign-in was not completed: access_denied. If you chose Cancel, connect again and choose Allow ..." The person cancelled, or the workspace needs an admin to approve SourceLace. Connect again and choose Allow, or a Slack admin approves the app (step 1).
"Slack refused because of your organization's Slack settings: on Enterprise Grid ..." The Grid organization has not approved SourceLace for this workspace. A Slack org admin approves the app and allows it in the workspace (step 1).
"Slack sign-in failed (bad_client_secret): the Client ID or Client Secret saved on ... does not match your Slack app ..." (or invalid_client_id) Your own app's credentials are wrong or were regenerated. Copy both again (step 3).
"Slack sign-in did not grant .... Connect again and allow every permission." A permission was not allowed. Connect again and allow every permission.
"You signed in to Slack workspace ..., but ... is workspace .... Connect again and choose that workspace." The person chose another workspace than team_id. Connect again and choose the right one.
"Slack is limiting how often SourceLace can read conversation history..." Slack's limits for apps outside its Marketplace. Wait a minute or use a search query; or use your own app (step 3).
"You are not a member of that Slack conversation. Join it in Slack first." The person is not in that channel. Join the channel.
"Your Slack sign-in does not include the permission this needs..." The sign-in was made before an admin allowed changes. Connect again.
"Slack: not found, or you are not in that conversation." The id is wrong, or the person cannot see it. Use ids from a query.
"Your Slack sign-in was revoked or has expired. Connect Slack again." The app was removed, or the token revoked. Connect again.
"SourceLace's Slack app is not set up yet ..." SourceLace's Slack app is not ready yet, and the source has no app of its own. Contact support, or use your own app (step 3).
"Writes to files are turned off for ... An admin can enable them per source and object." An agent tried to post a file, and files is not in the source's Objects that can be changed. A SourceLace admin adds files (step 4.1), then the person connects again.
"Your Slack sign-in does not include the permission this needs (files:write) ..." The person connected before files was allowed, or your own app lacks files:write. Add the scope to your own app (step 4.2), then the person connects again (step 4.3).
"Slack did not take the file ... (HTTP ...)" or "Slack sent the upload to an unexpected address; stopping." Slack refused the upload, or answered in a way SourceLace does not trust. Nothing was posted. Retry it from the run's Deliveries list; if it keeps failing, contact SourceLace support.
"Slack is limiting how fast SourceLace can call it ..." (on a delivery: Retrying) Slack asked to wait. Nothing: SourceLace tries again by itself for up to a day.
"Slack takes at most 10 files at once here: send fewer." or "A file is larger than Slack's limit ..." The post holds more files than Slack takes in one message, or a file over 1 GB. Post fewer files per message.
"The Slack team_id (Workspace ID) for ... must be a workspace or organization id, such as T0123ABCD." The team_id option holds something other than a Slack workspace or organization id. An admin enters the workspace or organization id in the source's Workspace ID field.
"...: client_id must be your Slack app's Client ID (such as 1234567890.1234567890), and client_secret its Client Secret." The Client ID or Client Secret in the source is not from your Slack app. An admin copies both from Basic Information → App Credentials in the Slack app (see What your admin does in Slack).
"This Slack conversation is archived." An archived channel cannot be posted to or changed. Unarchive it in Slack, or use another channel.
"Slack: no such person in your workspace." The person is not in the workspace you signed in to. Check the name or id.
"Slack: no message with that id that you can see." The message id is wrong, or it is in a conversation you are not in. Use an id from a query's results.
"Slack did not give a download address SourceLace can use for that file." or "SourceLace refused to make that call to Slack." Slack sent SourceLace to an address outside Slack's file servers, which it never uses. Try again. If it repeats, contact support.

Microsoft Teams

What you see What it means What to do
"Microsoft needs an administrator of your organization to approve SourceLace's Teams permissions first (... always need an admin's approval) ..." No admin has approved the admin-only permissions this source asks for. Grant admin consent (step 2), or set Read channel messages to Off.
"Microsoft sign-in failed: ..." Microsoft's own reason follows. Check step 2.
"Microsoft Teams: your account has no Teams license, or Teams is turned off for you." The person has no Teams licence. Give them one (step 3).
"... does not read channel messages (channel_messages is off) ..." Read channel messages is Off. Read chats, or an admin turns it On and grants consent.
"... does not read meetings ..." Read meetings and transcripts is Off. An admin turns it On and grants consent.
"Microsoft did not give that meeting's transcript or recordings..." Transcription was off, the policy forbids it, or the person did not organize the meeting. Check step 4.
"Teams cannot schedule messages through SourceLace..." Teams has no scheduled messages. Post now, or schedule it in Teams yourself.
"Your Microsoft sign-in has expired." The sign-in ended. Connect again.
"In Microsoft Teams, files go only in channels (team id/channel id), not in chats." An agent tried to post a file in a chat. Post it in a channel, or attach it to an email draft.
"Microsoft Graph: you may not add files to the channel's files, or the sign-in lacks Files.ReadWrite.All ..." The person connected before files was allowed, or consent is missing, or they cannot add files to the channel. Connect again; an Entra admin grants consent (step 2 above); check the person is a member of the channel.
"Microsoft Graph asked SourceLace to wait ..." (a delivery shows Retrying) Microsoft is limiting requests. Nothing: SourceLace tries again by itself for up to a day.
Needs a check on a Teams post SourceLace restarted while posting and Teams cannot say whether it arrived. Look in the channel; press It did not arrive: send again only if it is not there.
"The meetings option of ... must be on or off." or "The channel_messages option of ... must be on or off." The option holds something other than on or off. An admin sets it to on or off.
"Microsoft Teams did not find that meeting for your account." or "Microsoft Teams has no transcript for that meeting. Transcription must be turned on during the meeting." You were not at that meeting, or its transcript was not recorded. Check the meeting link. Transcripts exist only when someone turned transcription on during the meeting.
"Microsoft Teams: no message with that id that you can see." The message id is wrong, or it is in a chat or channel you cannot see. Use an id from a query's results.
"SourceLace's Microsoft sign-in is not set up correctly." SourceLace's own Microsoft app is not configured properly on SourceLace's side. Contact support.
"Microsoft Graph returned an unexpected link.", "Microsoft Graph sent the download to an unexpected address; stopping." or "SourceLace refused to make that call to Microsoft Graph." Microsoft pointed to an address outside Microsoft Graph, which SourceLace never calls. Try again. If it repeats, contact support.

Both

What you see What to do
"SourceLace does not send direct messages to people outside your organization." By design: post from Slack or Teams yourself.
"Your sign-in to ... has expired. Call connect_source to sign in again." The token was revoked or expired: connect again.
"Allow changes is on for ..., but Objects that can be changed is empty ..." A SourceLace admin lists the objects, such as messages, reactions.