Teams, reachable from where you already are.
Cedric lives in Slack, Telegram or Discord; connect Microsoft Teams and it reads the channel, drafts the post and asks before anything is sent.
$50 in free credits when you sign up. No card needed.
- Half the company is in Microsoft Teams and the other half is not, so updates get retyped.
- Cedric reads recent messages and history from the Teams chats and channels the connected account can access, and summarizes them where you are.
- It posts to a channel, a chat or an existing thread on your behalf, plain or formatted with cards and links, previewed first.
- It schedules online meetings and shares the join link, checks presence to see who is free, and finds people in your organization.
- Every post and every new team or channel is confirmed first, and many of these permissions need an administrator's approval before the connection works.
What can a Microsoft Teams AI agent do?
Microsoft Teams is often the other chat: the one the client, the parent company or the other department uses. Cedric lives in Slack, Telegram or Discord, and this connection lets it reach Teams on your behalf. It reads recent messages and conversation history from the chats and channels the connected account has access to, lists the teams and channels you belong to and looks up their members, so a question like what the client said in their channel this week can be answered without switching apps.
Posting goes the other way. Cedric sends messages to a channel, a one-on-one or group chat, or as a reply in an existing thread, including rich formatted messages and cards with buttons or links. It can search for people in your organization to start a conversation with them, and read presence status to tell you who is available, busy or away before you go looking. Each post is drafted and previewed first.
Meetings and structure are covered too. Cedric schedules online meetings and shares the join link with participants, and it creates new teams and channels and adds or removes people from them, on your yes. Three things to know before connecting: many of these actions require an administrator to approve the permissions, bulk message reading is rate limited and may need special licensing, and this connection reads and posts on your behalf rather than installing Cedric as a bot inside Teams. For where Cedric does live, see AI for Slack.
The other chat
What the client said in Teams, answered from Slack.
Daniel Osei9:14 AM
@Cedric what did Northwind post in their Teams project channel since Friday? And let them know the revised timeline goes out Thursday.
CedricAPP9:15 AM
Six messages since Friday. Their PM asked twice about the revised timeline (Monday, Wednesday), their IT lead confirmed SSO testing is done, and three are scheduling chatter. Their PM shows as available right now. Proposed reply in the project channel, as you: "Thanks for the patience. The revised timeline goes out Thursday. SSO test results noted, thank you." Nothing else posted.
Read
Recent messages and history from the Teams chats and channels the connected account can see, summarized where you are.
Posted
A message to a channel, a chat or an existing thread, plain or with a formatted card, previewed and sent on your yes.
Scheduled
An online meeting with the join link shared, plus presence checks so you know who is free before you ask.
Connect Microsoft Teams in a minute
No setup project, no workflow builder, no field mapping. The flow is the same for every tool Cedric connects to.
- 01
Install Cedric where your team talks
One click. It joins your Slack like any other member, and everyone shares the same Cedric.
- 02
Connect Microsoft Teams from the dashboard
Open the Integrations page and sign in with Microsoft Teams on its own screen. Cedric never sees or stores your password, and you can revoke the connection in one click at any time.
A fresh connection can look but not touch: read-only until you say otherwise.
- 03
Ask in plain words
Back in the channel, try it: "what was posted in the project channel on teams this week?". You describe the outcome; Cedric picks the Microsoft Teams actions the ask needs. There is nothing to configure.
Connect for the whole workspace so the team shares it, or keep the connection personal. Two accounts are fine too; each gets a short name.
- 04
Let it become routine
Schedule the recurring version of the ask, and let Cedric fold Microsoft Teams into bigger jobs that cross your other tools. Anything that would leave your workspace still comes back as a preview to approve first.
Better in company
A meeting set up in Teams still needs to land on your own Google Calendar, and the summary still goes out through Gmail. Ask Cedric to schedule the Teams meeting, hold the slot, and draft the email with the join link, all previewed before anything sends.
When the client's requests live in Teams and the work lives in Linear or Notion, Cedric can read the channel and propose the issues or the doc update, so nothing said in the other chat gets retyped by hand.
Where the limits are
Microsoft Teams is a catalog connection, not a built-in playbook. Cedric works from what the Microsoft Teams connection can read and do; ask in plain words and it says what it can reach there, and what it cannot.
An administrator has to approve the permissions. Many Teams actions, reading channels or creating teams among them, need admin consent before the connection can do them; until then Cedric says what it cannot reach.
Bulk reading is rate limited and may need licensing. Reading a long history across many channels is throttled, and some message-reading permissions require a specific Microsoft license.
Cedric sees what the Microsoft Teams connection grants and nothing more. Access is scoped, logged, and revocable from the dashboard, effective immediately.
Nothing sends itself. An email, a post, a change to a record: anything with consequences comes back as a preview for a human yes. That is the design, not a beta caveat.
FAQ
Yes. Microsoft Teams is one of the 3,200+ apps in Cedric's catalog: connect it once from the dashboard, on Microsoft Teams's own sign-in screen, and ask in plain words. There is no built-in playbook for it, so Cedric works from what the connection can read and do, and tells you when something is out of reach.
Not through this connection. Cedric lives in Slack, Telegram and Discord; the Teams connection lets it read and post there on your behalf, as the connected account. It is a bridge to the other chat, not a bot living in it.
Only the teams and channels the connected account belongs to, and only once an administrator has approved the reading permission. Private chats are reachable the same way: the connected user's own, nothing beyond.
Connect it for the whole workspace and everyone shares it, with one person authorising once. A connection you would rather not share, a personal inbox for instance, can stay personal to you.
Yes, and it starts that way: a fresh connection can look but not touch until you say otherwise. Even with write access granted, anything that changes or sends waits for an approval.
Every workspace starts with $50 in credits, free, no card. Each task consumes credits in proportion to the work involved. See pricing for the plans.
Connect Microsoft Teams in a minute.
Ask what was posted in one channel this week, then let it draft your reply.
100K credits ($50) on sign up. No card needed.