Who this is for: self-serve plans (Free, Starter, Pro, Enterprise). Clu in Teams and Teams channels are included on Pro, Enterprise and the Pro trial. They are not part of the AppSumo deal; see the AppSumo documentation. Support agent: confirm whether the user is self-serve or AppSumo before giving plan-specific advice.
TL;DR: On Integrations → Communication, click + on the Clu in Teams card to add Clu in Teams, then message Clu in a 1:1 chat. A Cleanlist org admin opens the link Clu sends and clicks Connect. Every other member links their own account the same way (Link account). Then chat with Clu or @mention it in a channel. Reads run straight away; imports, enrichment and other changes wait for Approve. Same credit pricing as Clu in Slack, up to 40 credits per request. Separately, an admin can paste a Teams Workflows webhook on the Microsoft Teams card so a play's Notify step posts to that channel, free.
Clu in Microsoft Teams
There are two Teams connections on the Integrations page, both under Communication until they're set up and under Active connections after:
| Card | What it does | Who sets it up |
|---|---|---|
| Clu in Teams | Talk to Clu in Teams: 1:1 chats and @mentions in channels | An org admin connects your Microsoft organization; each member links their own account |
| Microsoft Teams | Post agent notifications to a Teams channel through a Workflows webhook | An org admin |
Who can use it
| Plan | Clu in Teams | Teams channels (Notify) |
|---|---|---|
| Pro, Enterprise | Included | Included |
| Pro trial | Included | Included |
| Starter, Free | Not included. The card shows the Pro pill, and Clu replies "Clu in Microsoft Teams isn't included in this workspace's Cleanlist plan. Ask your Cleanlist admin." | Not included |
| AppSumo only | Not included. A paid Cleanlist plan on top unlocks it. | Not included |
On an older plan, Clu in Teams works only if Clu in Slack is included in it; otherwise switch to current pricing. See Legacy plans.
If a workspace connected to Teams loses its plan, the card stays and shows Pro plan required, so an admin can still disconnect it.
Part 1: Clu in Teams
Step 1: an admin connects your Microsoft organization
You connect once per Microsoft organization (Teams tenant). The link comes from Clu in a 1:1 chat, and the admin who clicks Connect must be signed in to Cleanlist with the same email they use in Teams.
Add Clu in Teams
Click Integrations in the sidebar. Under Communication, find the Clu in Teams card ("Add Clu to Teams, then message Clu in a 1:1 chat to connect") and click +. Teams opens on the Clu app; add it.
Message Clu in a 1:1 chat
Send Clu any message in a 1:1 chat. Clu introduces itself and replies: "To get started, a Cleanlist admin connects your Microsoft Teams organization once. If that's you, open Cleanlist to connect and sign in with the email you use in Teams."
If you @mention Clu in a channel first, it replies "Message me directly to connect Cleanlist."
Click open Cleanlist to connect
Cleanlist opens on Integrations with a Connect Microsoft Teams dialog: "Connect [your Microsoft organization] to [your Cleanlist workspace]?" and "Requested in Teams by [name (email)]." Make sure you're in the Cleanlist workspace you want to connect.
Click Connect
Cleanlist shows "Microsoft Teams connected." and Clu posts "Connected to [workspace]. Ask me anything." in your 1:1 chat. The Clu in Teams card moves to Active connections with your Microsoft organization's name and Connected.
Good to know:
- Only an org admin can connect. Anyone else sees "Only an organization admin can connect Teams." and Connect stays off.
- The email must match. Signed in to Cleanlist with a different email, the dialog says "Sign in to Cleanlist as [your Teams email] to connect."
- The admin who connects is linked automatically. They don't need Step 2.
- The link works once and expires after a day. After that, message Clu again for a new one.
- One Microsoft organization per Cleanlist workspace, and one workspace per Microsoft organization: "This tenant or organization already has a Teams connection."
- Disconnect (admins only, on the card) opens "Disconnect Clu from Teams?": "Members of this organization can no longer use Clu from Teams until an admin reconnects Microsoft Teams." Click Disconnect.
Step 2: each member links their account
Clu acts as your own Cleanlist account, so every member links their Teams account once. Linking happens only in a 1:1 chat.
Message Clu in a 1:1 chat
The first time, Clu replies "To use Clu here, link your Cleanlist account. Sign in to Cleanlist, then press Link account." In a channel, it says "Message me directly to link your Cleanlist account."
Click link your Cleanlist account
Sign in to Cleanlist if asked. A Link your Teams account dialog asks "Link your Teams account to [your Cleanlist email] in [workspace]?" and shows your Teams account and Microsoft organization, with "Clu in Teams will act as you."
Click Link account
Cleanlist shows "Your Teams account is linked. Message Clu in Teams." Go back to Teams and ask your question again.
The link works once and expires after a day. It has to be opened in the Cleanlist workspace connected to your Microsoft organization; otherwise you see "This link is for another Cleanlist organization. Switch to it and open the link from Teams again."
To unlink, type sign out to Clu: "You're signed out of Cleanlist in Microsoft Teams. Message me anytime to sign in again." Type help at any time to see how to use Clu.
Step 3: talk to Clu
- 1:1 chat: just ask, for example "Find 5 VPs of Sales at SaaS companies in Toronto."
- Channels and group chats: @mention Clu. Each thread is its own conversation.
- Each conversation belongs to the person who started it. Anyone else gets "This thread belongs to someone else. Start a new chat or thread with Clu."
- One request at a time per conversation. A new message while Clu is working gets "Still working on the previous request."
- Not supported: shared channels and people from another Microsoft organization ("I can't run in externally shared channels or for users from another tenant. Send me a 1:1 message from your connected Teams account.").
- Files: send a CSV or TSV to Clu in a 1:1 chat to import it into a list. A file in a channel or group chat gets "Send the CSV to me in a 1:1 chat and I'll import it." XLSX files go in with the list's Import from CSV in Cleanlist; see Import from CSV.
What Clu can do in Teams
Clu in Teams uses the same tools and limits as Clu in Slack.
| Runs straight away | Needs your approval |
|---|---|
| Search for people or companies (one database search per request) | Import people into a list, or import a CSV or TSV you sent in a 1:1 chat |
| Search the web (one search, then up to 3 pages read per request) | Enrich leads (email, phone or both) |
| Read your lead lists and leads | Add a column or run a saved custom skill on a list |
| Check your credit balance and estimate a cost | Move leads, delete leads or delete a list |
| Read your company profile | Look up one person's work email, or check an email or phone |
| Read your CRM (HubSpot or Salesforce, if connected) | Save, change or forget a memory note |
| Read your memory notes and search your past chats | Run a saved agent on people you just imported |
| Find your saved agents | Send a Teams message to a connected channel or to a member who chats with Clu |
Lists, leads, people, companies and CRM results come back as Teams card tables (up to 3 tables of 50 rows per answer).
If Clu says Clu in Teams is read-only for now, writes are switched off for chat apps: Clu answers questions but does every change in the web app instead, and links you to the page.
Not in Teams (use the web app): Knowledge, Google Sheets, Google Docs and Airtable, building or editing agents, the 6sense lookups and 6sense for Clu, and reading files in channels or group chats.
Approving actions
When Clu wants to do something that changes data, contacts someone or costs credits, it posts a card with what it will do and two buttons, Approve and Cancel, with "You can also just reply yes or cancel."
- Only the person who asked can decide: anyone else gets "Only the person who requested this action can approve or cancel it."
- After a click, the card changes to "Approved · [name] · [time]. Running it now." or "Cancelled · [name] · [time]. Nothing was run."
- Long runs reply in the same conversation when they finish.
- An approval that waited too long gets "This request expired. Ask me again to start fresh."
Limits and costs
| Limit | Value |
|---|---|
| Tool calls per request | 10 |
| Time per request | 2 minutes |
| Credits per request | 40 |
| Credits needed to start a request | 40 available |
| Workspace AI spend for Clu | $37.50 per day (UTC), shared with the web app and Slack |
Clu in Teams uses the same pricing as Clu in the web app and in Slack: 0.2 credits per message you send, 0.2 credits per tool it completes, plus the AI model cost at $0.012 per credit. Paid actions you approve (enrichment, email lookup, skills) cost their normal price; importing a CSV is free. See What Clu costs.
Part 2: Teams channels for agent notifications
The Microsoft Teams card ("Post agent notifications to a Teams channel") connects a Teams channel through a Teams Workflows webhook. Agents then post to it from a play's Notify step. It doesn't need Clu in Teams. The card appears only on plans that include Agents.
Add a channel
Open the Add Teams channel dialog
An org admin goes to Integrations → Communication and clicks + on the Microsoft Teams card. Once a channel is connected, the button is Add channel. Members who aren't admins see the card and its channels but no buttons.
Make a webhook in Teams
In Teams, open the channel and select ⋯ (More options) → Workflows. Pick the Send webhook alerts to a channel template (the other two webhook templates need a sign-in, so Cleanlist can't post through them). Confirm the team and channel, select Save and copy the webhook URL Teams shows. If Workflows is missing, your Teams admin has to allow it.
Name it and paste the URL
Enter a Name (for example "Sales alerts"; it's how the channel appears in the Notify step) and paste the Webhook URL. It starts with https:// and ends in powerplatform.com, logic.azure.com or webhook.office.com. Anyone with the URL can post to the channel, so Cleanlist stores it encrypted and never shows it again.
Click Connect
Cleanlist posts a test card, "Cleanlist agents can post to this channel.", and saves the channel only if Teams accepts it. You see "Teams channel connected." and the card shows how many channels are connected.
To remove one, click Remove next to it and confirm in Remove Teams channel. It's removed for everyone in your organization.
Post from the Notify step
In a play, add the Microsoft Teams step ("Send a message", "Post to a channel or DM") and pick the channel under Teams channel. Channels you connected here show as "[Name] (Webhook)".
| Setting | Options |
|---|---|
| Send (agent plays) | Summary: one run summary. Digest: a list of the records, one line each. Each record: one message per record |
| Teams channel | A webhook channel, or, with Clu in Teams connected, a channel Clu was added to ("[Team] / [Channel] (Clu)") or Agent owner's Teams DM |
| Recipients (Clu channels only) | Teams channel, Agent owner's Teams DM, A teammate's Teams DM or Each record's owner |
Good to know:
- Cost: 0 credits.
- Digest and Each record work on an agent's play only.
- A digest shows up to 50 rows, then "and N more", with View the run and View leads buttons.
- In one run, past 25 Each record messages to a channel, the rest go out as one digest.
- A webhook channel posts to the channel only. DMs and Each record's owner need Clu in Teams, and the person has to have linked their Teams account.
- Webhook posts appear from the Workflows bot of the person who made the webhook in Teams.
- Try sends nothing; it shows what would be posted.
- To post through Clu to a channel, add Clu to that team in Teams so its channels show up. If Clu in Teams is disconnected, the step says "Clu in Teams isn't connected, so this step can't send. An admin can connect it on Integrations."
Troubleshooting
| What you see | Why, and what to do |
|---|---|
| The Clu in Teams card is missing | Clu in Teams isn't available for your workspace yet. Contact support. |
| Pro plan required on the card | Clu in Teams needs Pro, Enterprise or the Pro trial. Upgrade in Settings → Plans & billing. |
| "Clu in Microsoft Teams isn't included in this workspace's Cleanlist plan. Ask your Cleanlist admin." | Same: the workspace isn't on an eligible plan. |
| "Clu in Teams isn't enabled for this workspace." | Clu in Teams is turned off for your workspace. Contact support. |
| "Message me directly to connect Cleanlist." / "Message me directly to link your Cleanlist account." | Connecting and linking happen only in a 1:1 chat with Clu. |
| "Only an organization admin can connect Teams." | Ask an org admin to message Clu and connect. |
| "Sign in to Cleanlist as [email] to connect." | Sign in to Cleanlist with the email you use in Teams, or have that person connect. |
| "This Teams link has expired or is invalid." | Links work once and expire after a day. Message Clu for a new one. |
| "This tenant or organization already has a Teams connection." | Your Microsoft organization or Cleanlist workspace is already connected. Disconnect the old connection first. |
| "This Teams account is already linked to another Cleanlist user." | That user types sign out to Clu first. |
| "This link is for another Cleanlist organization..." | Switch to that workspace in Cleanlist and open the link from Teams again. |
| "Ask an admin to reconnect Clu in Teams." / "You're no longer a member of this Cleanlist organization." | Your link no longer matches the connected workspace. Ask an admin, then link again. |
| "I can't run in externally shared channels or for users from another tenant..." | Message Clu 1:1 from your connected Teams account. |
| "This thread belongs to someone else..." | Start your own chat or thread with Clu. |
| "Still working on the previous request." | Wait for Clu's answer, or approve or cancel the pending card. |
| "You're out of credits, balance X, this needs up to 40 reserved..." | Your workspace needs 40 credits available to start a request. Add credits in Settings → Plans & billing. |
| "This Clu request has reached its 40-credit limit. Start a new request to continue." | Start a new request to continue. |
| "That isn't a Teams webhook URL." / "Use the webhook URL from a Teams Workflows "Send webhook alerts to a channel" flow." | Make the webhook with that template and paste its URL. |
| "Teams refused the test message. Check the webhook URL and that its workflow is on." | Check the URL, and that the workflow is turned on in Teams. |
| "Teams didn't answer. Try again in a minute." / "Teams didn't confirm the test message..." | Try again in a minute, and check the channel. |
| "A Teams channel with that name is connected." | Pick another Name. |
| "Teams channel not connected" in a Notify step | The step has no channel, or its channel was removed. Pick a channel, or ask an admin to add one. |
Still stuck? Click Help and support in the Cleanlist sidebar or email support@cleanlist.ai.