Microsoft Teams

· #114 most-used

Where your team talks — and your agent acts

CommunicationProductivityProjectsSchedulingAutomation

Microsoft Teams is the Microsoft 365 collaboration hub where organisations run their daily chat, meetings, and file sharing. Connect it to Actionist and your agents can post to channels, reply in threads, create and manage chats, set your status, and react to new messages — all triggered by events across your entire stack. The payoff: decisions made in Teams drive action everywhere else, and information from everywhere else surfaces inside Teams exactly when the team needs it.

Average time saved
10 hours
per person · per month
1 workdays back

Eliminates manual work. Agents eliminate the manual work of copy-pasting updates between tools and Teams — no more hand-typing status messages, channel announcements, or digest posts that could be generated and delivered automatically.

Schedule

What your Microsoft Teams agent runs on autopilot

A week of scheduled jobs your Actionist agent will execute on your behalf.

28Scheduled jobs
7Agents at work
24/7Always on
Mon
Tue
Wed
Thu
Fri
7am
8am
9am
10am
11am
12pm
1pm
2pm
3pm
4pm
5pm
6pm
Agents
Multi-app workflows

Microsoft Teams × every other app you use

End-to-end automations that span multiple apps — each one a real business outcome.

6Workflows
9Apps spanned
~30 hrsSaved / week
6Personas served
customer-success★ FeaturedSaves 1h saved · runs ~10× /week

Escalation to resolution in under 5 minutes

When a client emails a complaint, the agent reads the customer's Teams channel history to surface any previous escalations, then posts a structured escalation card in the support channel with the email content and history digest — and simultaneously books a 30-minute call on the customer success rep's calendar and pings the team lead in Slack with a one-line priority summary. Every step happens before a human has even opened the email.

Trigger: When a new message arrives in the customer support Gmail inbox flagged as a complaint
Step 1 trigger
Gmail
Detect incoming complaint email
Step 2 read
Microsoft Teams
Get channel to find existing customer thread
Step 3 write
Microsoft Teams
Send Message with Card to #escalations with complaint details and history
Step 4 write
Slack
Send priority summary to CS team lead
Step 5 write
Google Calendar
Book 30-minute response call with the account rep
Every complaint hits the right person within 60 seconds
Savings

What this looks like for your team

The comparison strip shows real manual tasks your agent replaces. The calculator translates that into your team's numbers.

Without Actionist
With Microsoft Teams agent
  • Sales
    Manual win announcements
    Reps copy deal details from the CRM and paste a message into the sales channel after each close — easy to forget during a busy week.
    18 min/week
    Sales Agent
    Agent posts the win card instantly
    The moment a deal closes in the CRM, the agent posts an Adaptive Card to #wins with deal name, value, and rep — zero rep effort, zero delay.
  • Marketing
    Launch day DM chain
    Marketing leads manually message every stakeholder to confirm launch readiness, waiting for replies across Slack, email, and Teams.
    13 min/week
    Marketing Agent
    Agent posts checklist card to channel
    When a campaign goes live, the agent posts a single checklist card in #marketing-launches with every required sign-off so coordination happens in one thread.
  • Customer Support
    Escalation relay by hand
    Support agents manually forward complaint emails into Teams channels and then chase the right person to acknowledge them.
    18 min/week
    Customer Support Agent
    Agent routes and cards the escalation
    When a complaint email arrives, the agent posts a structured card to #escalations with context and severity — the right person is notified before a human opens the inbox.
  • Human Resources
    New hire welcome messages
    HR manually DMs each new hire's manager and buddy in Teams with onboarding links and first-week instructions on day one.
    7 min/week
    Human Resources Agent
    Agent sends personalised onboarding DMs
    When a new member joins the team, the agent opens a 1:1 with their manager and buddy and sends the onboarding checklist and resource links automatically.
  • Finance
    Approval request forwarding
    Finance staff copy budget request details from Notion or email into a Teams message and manually chase the approver for a reply.
    13 min/week
    Finance Agent
    Agent sends approval card and waits
    The agent posts an Adaptive Card with request details to the finance channel and pauses until the approver replies, then routes the outcome downstream without human intervention.
  • Operations
    Vendor digest copy-paste
    Ops managers review a spreadsheet of vendor statuses each Monday and manually type a summary into the ops Teams channel before the weekly review.
    25 min/week
    Operations Agent
    Agent posts live vendor digest
    When the vendor sheet updates, the agent reads the changes and posts a formatted digest to #ops-vendors — the Monday brief is ready before the team even arrives.
  • Legal
    Contract review pings
    Legal team members manually message counterparts in Teams to flag contracts awaiting review, with no automatic link to the document.
    6 min/week
    Legal Agent
    Agent sends review card with document link
    When a contract enters Awaiting Review status, the agent posts an Adaptive Card to the legal channel with the document link and deadline, so nothing waits on a manual ping.

+ 100s of other automations your agent handles

Average monthly savings
10 hours / person
ROI calculator

See what your team gets back

Team size
10 people
Fully-loaded rate
$20 / hour
Hours / week
25
Hours / year
1,250
Annual ROI
$25,000

Baseline: 2.5 hrs saved per person per week, across the full Microsoft Teams automation set.

Connect

How to plug Microsoft Teams into Actionist

Pick the connection method that suits your environment.

The fastest path. Install the Microsoft Teams MCP server in one click and the agent gains full read/write access to channels, chats, and messages through a permissioned OAuth handshake — no tokens to rotate, no client secret to manage.

1
Open the Apps tab

Find Microsoft Teams in the Apps library and click Connect. MCP is selected by default.

2
Authorise in Microsoft Teams

A Microsoft OAuth consent screen opens. Sign in with your Microsoft 365 account and grant the requested scopes — the agent needs Channel.ReadWrite, Chat.ReadWrite, and ChannelMessage.Send to cover all actions.

3
Test the connection

Actionist runs a read-only call to verify the handshake. You're ready.

Read the Microsoft Teams docs →
Actions

25 actions your agent can call

Read and write operations available to your Actionist agent.

Triggers

7 events your agent can react to

Events your agent watches for, and the actions it kicks off in response.

Skills

Skills that pair with Microsoft Teams

Reusable agent skills that work well alongside this app.

Clawdbot Documentation Expert

Navigates and queries official Clawdbot documentation to answer configuration and troubleshooting questions with config snippets.

Clawdbot Documentation Expert

Decision-tree documentation navigator for Clawdbot with search scripts, doc fetching, and version-specific config snippets.

OpenClaw Ecosystem Manager

CLI wrapper for the full OpenClaw stack — gateway, channels, models, agents, nodes, browser, memory, security, and automation.

MCP servers

MCP servers that work with Microsoft Teams

Connect Actionist to MCP servers built for or around this app.

Microsoft Teams
Official

Connects the agent to Microsoft Teams to read and send messages, list channels, and search chats via the Graph API.

Microsoft Teams API
Official

AI-native Teams integration for reading chat history, sending messages, and searching people across your Microsoft 365 tenant.

teams
Official

MCP server for collaborating, chatting, and managing meetings inside Microsoft Teams from any AI agent.

FAQs

Questions about Microsoft Teams + Actionist

How do I connect Microsoft Teams to Actionist?
Open the Apps tab, find Microsoft Teams, and click Connect. The MCP path is selected by default — click Authorise, sign in with your Microsoft 365 account, and grant the required Graph API scopes (Channel.ReadWrite, Chat.ReadWrite, ChannelMessage.Send). Actionist runs a read-only verification call and you are ready to build workflows.
What Microsoft 365 permissions does the agent need?
The agent needs Microsoft Graph API scopes that match the actions you use: Channel.ReadWrite.All for creating and updating channels, Chat.ReadWrite for opening and messaging chats, ChannelMessage.Send for posting to channels, and Presence.ReadWrite if you use Set Status. Grant only the scopes your workflows actually need — the consent screen lists each one before you approve.
Can I combine Microsoft Teams with other apps in one workflow?
Yes — Teams is almost always a notification or coordination layer in a multi-app workflow. Common patterns include triggering on a HubSpot deal close and posting a win card to Teams, reading a Google Sheet and posting a digest to a Teams channel, or sending a Teams approval card and waiting for the human reply before updating Salesforce. Any app in the Actionist library can be paired with Teams in the same workflow.
What are the most common Microsoft Teams automation use cases?
The highest-leverage patterns are: posting real-time notifications to channels when events happen elsewhere (deal closes, ticket escalations, CI failures); routing messages and creating chats when a new person joins a team or a process starts; using Send and Wait for Response as a human-in-the-loop approval gate inside a longer automated workflow; and compiling periodic digests from spreadsheets or databases into a formatted Teams post on a schedule.
Does Actionist charge per Teams message sent?
No. Actionist charges per workflow run, not per action inside the run. A single workflow that sends 3 Teams messages, reads a channel, and posts a card still counts as one run. Microsoft Teams itself has no per-message API cost. The main rate limit to be aware of is the Microsoft Graph API's throttling policy — around 4 requests per second per app per tenant — which Actionist handles automatically with built-in retry logic.
How do I avoid trigger loops when the agent posts to a channel it is also watching?
Two safeguards work together. First, use Send Bot Message instead of Send Channel Message when the agent is also monitoring that channel — messages from the bot identity are filtered out of the New Channel Message trigger by default. Second, add a condition step that checks the sender ID: if the incoming message sender matches the Actionist service account ID, exit the workflow immediately. Both together make loops impossible.
Can the agent read the full history of a channel or just new messages?
The New Channel Message trigger delivers only new messages as they arrive. To read historical messages, use Get Channel Message (single message by ID) or Get Channel by ID to retrieve channel metadata, then call the Microsoft Graph API via the API Request (Beta) action to fetch a batch of messages with a timestamp filter. For most notification and routing use cases, the real-time trigger is sufficient.
What happens if I disconnect Microsoft Teams — do scheduled workflows break?
Yes. Any workflow using a Teams trigger or action will fail its next run with an authentication error. The workflow itself is not deleted — it stays paused. To fix, open the Apps tab, find Microsoft Teams, click Reconnect, and re-authorise. All workflows that reference Teams will resume on their next scheduled or triggered run. Check the workflow run log for any failed runs that need to be manually retried after reconnection.