CONNECT APP
Build with Microsoft Teams Events
Communication
- OAuth
MCP
Give your agent Microsoft Teams Events tools
Every Microsoft Teams Events action is exposed as an MCP tool on Pipedream's remote server. Point a client at it with your end user's ID and Connect resolves that user's Microsoft Teams Events account for each tool call — you store no tokens.
// accessToken: mint a short-lived token with the Connect SDK — see the MCP guide
const transport = new StreamableHTTPClientTransport(
new URL("https://remote.mcp.pipedream.net/v3"),
{
requestInit: {
headers: {
Authorization: `Bearer ${accessToken}`,
"x-pd-project-id": "{project_id}",
"x-pd-environment": "production",
"x-pd-external-user-id": "{external_user_id}", // any stable ID for this user in your system
"x-pd-app-slug": "microsoft_teams_events",
},
},
},
)
const mcp = new Client({ name: "my-agent", version: "1.0.0" })
await mcp.connect(transport)
const { tools } = await mcp.listTools()
// Every tool arrives with its own input schema — run one with mcp.callTool().# access_token: mint a short-lived token with the Connect SDK — see the MCP guide
headers = {
"Authorization": f"Bearer {access_token}",
"x-pd-project-id": "{project_id}",
"x-pd-environment": "production",
"x-pd-external-user-id": "{external_user_id}", # any stable ID for this user in your system
"x-pd-app-slug": "microsoft_teams_events",
}
async with streamablehttp_client("https://remote.mcp.pipedream.net/v3", headers=headers) as (read, write, _):
async with ClientSession(read, write) as session:
await session.initialize()
tools = await session.list_tools()
# Every tool arrives with its own input schema — run one with call_tool().API PROXY
Call the Microsoft Teams Events API directly
For an endpoint with no pre-built tool, the Connect proxy forwards your request to the Microsoft Teams Events API with the connected user's credentials attached. You store no tokens and write no refresh logic.
const resp = await pd.proxy.get({
externalUserId: "{external_user_id}", // any stable ID for this user in your system
accountId: "apn_xxxxxxx",
url: "https://graph.microsoft.com/v1.0/me",
})
// Any allowed Microsoft Teams Events endpoint works here. Pipedream attaches the
// connected account's credentials to the outgoing request.# The path segment is the target URL, URL-safe base64 encoded:
# https://graph.microsoft.com/v1.0/me
curl "https://api.pipedream.com/v1/connect/{project_id}/proxy/aHR0cHM6Ly9ncmFwaC5taWNyb3NvZnQuY29tL3YxLjAvbWU?external_user_id={external_user_id}&account_id=apn_xxxxxxx" \
-H "Authorization: Bearer {access_token}" \
-H "x-pd-environment: production"SDK
Run Microsoft Teams Events actions from your backend
Connect a user's Microsoft Teams Events account once, then discover and run its tools on their behalf from your own code — TypeScript, Python, or plain HTTP.
import { PipedreamClient } from "@pipedream/sdk"
const pd = new PipedreamClient({
projectId: process.env.PIPEDREAM_PROJECT_ID!,
clientId: process.env.PIPEDREAM_CLIENT_ID!,
clientSecret: process.env.PIPEDREAM_CLIENT_SECRET!,
projectEnvironment: "production",
})
const tools = await pd.components.list({
app: "microsoft_teams_events",
componentType: "action",
})from pipedream import Pipedream
pd = Pipedream(
client_id="{oauth_client_id}",
client_secret="{oauth_client_secret}",
project_id="{project_id}",
project_environment="production",
)
tools = pd.components.list(
app="microsoft_teams_events",
component_type="action",
)curl "https://api.pipedream.com/v1/connect/{project_id}/components?app=microsoft_teams_events&component_type=action" \
-H "X-PD-Environment: production" \
-H "Authorization: Bearer {access_token}"TOOLS
Microsoft Teams Events actions
On-demand operations your product or agent can configure and run on behalf of a connected user.
No Microsoft Teams Events actions are available yet.
EVENTS
Microsoft Teams Events triggers
Event sources your backend can deploy for users and receive through a webhook.
No Microsoft Teams Events triggers are available yet.
MULTI-APP
Use Microsoft Teams Events with other popular apps
Most products don't stop at one integration. Pair Microsoft Teams Events with the other apps your users rely on, and ship use cases that span both.
REFERENCE
App details
Reference metadata for the Microsoft Teams Events connector in the Pipedream registry.
- App slug
- microsoft_teams_events
- Authentication
- OAuth
- Categories
- Communication
- Actions
- 0
- Triggers
- 0
- API proxy
- Available
OAuth scopes
These are the scopes Pipedream's managed Microsoft Teams Events OAuth client requests when one of your users connects an account. Supply your own OAuth client to request a different set.
- User.Read
- offline_access
- openid
- Team.ReadBasic.All
- VirtualEvent.Read
- OnlineMeetingArtifact.Read.All