Microsoft Teams has communities, events, chats, channels, meetings, storage, tasks, and calendars in one place.
12 actions Leo can use in the apps and agents it builds for you: 9 that read Microsoft Teams data, 3 that create or update it.
Returns the authenticated Microsoft Teams user's ID, display name, email, and principal name via Microsoft Graph. Call this first when the user says 'my channels', 'my chats', or needs identity context. Use the returned id to identify the sender in Send Channel Message or Send Chat Message results.
Lists messages in a Microsoft Teams channel.
Docs ↗Lists all teams the authenticated user has joined.
Docs ↗Lists all chat conversations for the authenticated user.
Docs ↗Search for email or chat messages.
Docs ↗Get the list of shift instances for a team.
Docs ↗Get the list of messages in a chat.
Docs ↗Lists all channels in a Microsoft Team. See the docs here
Get a specific message from a chat.
Docs ↗Send a message to a team's chat. Optionally include inline images via hostedContents. See the docs here
Send a message to a team's channel. Optionally include inline images via hostedContents.
Create a new channel in Microsoft Teams. See the docs here
Leo connects Microsoft Teams to the ERP your business already runs on: the records it reads in Microsoft Teams land in your ERP, and what changes in the ERP flows back.
Authorize Microsoft Teams once, in a couple of clicks. Leo only gets the permissions you grant.
In plain language: the dashboard, portal or agent you want across Microsoft Teams and your ERP. No code, no mapping spreadsheets.
Leo builds it, you review, it goes live. Agents run on a schedule or on events, under the guardrails you set.