Microsoft Teams

Manage teams, channels, messages, and meetings via Microsoft Graph.

Detail	Value
Category	Productivity
Base URL	https://graph.microsoft.com/v1.0
Authentication	OAuth2
Endpoints	6
Connector key	microsoft-teams

Using Microsoft Teams in a workflow

1. Go to Connections and click New Connection.
2. Pick Microsoft Teams from the marketplace.
3. Enter your credentials (see Authentication above for what's expected).
4. In a workflow, drop an API Call node and select this connection.
5. Pick the operation you need from the Operation dropdown — the full list is below.

Available endpoints

Endpoint	Summary
GET /me/joinedTeams	List joined teams
POST /teams	Create a team
GET /teams/{teamId}/channels	List channels in a team
POST /teams/{teamId}/channels/{channelId}/messages	Send a channel message
GET /teams/{teamId}/members	List team members
POST /me/onlineMeetings	Create an online meeting

Each endpoint is documented in full below. Use the outline on the right to jump to one.

GET /me/joinedTeams

List joined teams

Detail	Value
Operation ID	productivity.listJoinedTeams
Method	GET
Path	/me/joinedTeams

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Microsoft Teams connection from the Connection dropdown.
3. In the Operation dropdown, select productivity.listJoinedTeams.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Microsoft Teams API reference.

POST /teams

Create a team

Detail	Value
Operation ID	productivity.createTeam
Method	POST
Path	/teams

Parameters

No parameters.

Request Body

Field	Type
displayName	string

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Microsoft Teams connection from the Connection dropdown.
3. In the Operation dropdown, select productivity.createTeam.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

Required fields are marked — fill them or the call will fail at runtime.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Microsoft Teams API reference.

GET /teams/{teamId}/channels

List channels in a team

Detail	Value
Operation ID	productivity.listChannels
Method	GET
Path	/teams/{teamId}/channels

Parameters

Name	Location	Type	Required
teamId	path	string	Yes

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Microsoft Teams connection from the Connection dropdown.
3. In the Operation dropdown, select productivity.listChannels.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

Required fields are marked — fill them or the call will fail at runtime.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Microsoft Teams API reference.

POST /teams/{teamId}/channels/{channelId}/messages

Send a channel message

Detail	Value
Operation ID	productivity.sendMessage
Method	POST
Path	/teams/{teamId}/channels/{channelId}/messages

Parameters

Name	Location	Type	Required
teamId	path	string	Yes
channelId	path	string	Yes

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Microsoft Teams connection from the Connection dropdown.
3. In the Operation dropdown, select productivity.sendMessage.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

Required fields are marked — fill them or the call will fail at runtime.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Microsoft Teams API reference.

GET /teams/{teamId}/members

List team members

Detail	Value
Operation ID	productivity.listMembers
Method	GET
Path	/teams/{teamId}/members

Parameters

Name	Location	Type	Required
teamId	path	string	Yes

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Microsoft Teams connection from the Connection dropdown.
3. In the Operation dropdown, select productivity.listMembers.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

Required fields are marked — fill them or the call will fail at runtime.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Microsoft Teams API reference.

POST /me/onlineMeetings

Create an online meeting

Detail	Value
Operation ID	productivity.createMeeting
Method	POST
Path	/me/onlineMeetings

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Microsoft Teams connection from the Connection dropdown.
3. In the Operation dropdown, select productivity.createMeeting.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Microsoft Teams API reference.