# Microsoft Teams · Graph API - Workflow node | Docs - nodulz

Source: https://nodulz.com/docs/nodes/teams_graph

Language: en

Teams, channels, members and messages through Microsoft Graph application permissions.

## Usage and specifics

Use a Microsoft Graph credential with the required Teams permissions. Supply team, channel and message identifiers for the action. Tenant permissions and consent restrict operations.

Technical type : `teams_graph`. Runtime : `nodulz`.

## Credentials and prerequisites

- [Microsoft Graph](/docs/credentials) (`integration` / `microsoft_graph`). OneDrive, SharePoint and Outlook with an Entra ID application.

Create credentials in your nodulz instance’s Credentials area, then select them on the node. Availability depends on ownership and sharing. See the [credentials guide](/docs/credentials) for access and rotation.

## Parameters

Names below are technical keys. Defaults are not a ready-to-run configuration: complete fields required by your operation. Paths containing [] describe list items; some fields depend on the selected mode.

| Parameter | Type | Default | Values / limits |
| --- | --- | --- | --- |
| `credentialId` | `string` | - | - |
| `operation` | `enum` | `"list_teams"` | `list_teams`, `get_team`, `list_channels`, `get_channel`, `create_channel`, `update_channel`, `delete_channel`, `list_team_members`, `add_team_member`, `remove_team_member`, `list_channel_members`, `get_chat`, `list_chat_members`, `list_channel_messages`, `get_channel_message`, `list_replies`, `list_chat_messages`, `get_chat_message`, `rest` |
| `teamId` | `string` | `""` | - |
| `channelId` | `string` | `""` | - |
| `chatId` | `string` | `""` | - |
| `messageId` | `string` | `""` | - |
| `memberId` | `string` | `""` | - |
| `method` | `enum` | `"GET"` | `GET`, `POST`, `PUT`, `PATCH`, `DELETE` |
| `path` | `string` | `""` | - |
| `body` | `string` | `""` | - |
| `query` | `string` | `""` | - |

## Initial configuration

Initial catalog configuration example, to adapt before running. Keep secrets in credentials.

```json
{
  "operation": "list_teams",
  "teamId": "",
  "channelId": "",
  "chatId": "",
  "messageId": "",
  "memberId": "",
  "method": "GET",
  "path": "",
  "body": "",
  "query": ""
}
```

## Verification

Test with representative data. Check node output in the inspector and logs, then use editor mapping for downstream fields. A trigger test with a simulated payload does not validate external service delivery.

See also : [Expressions and data](/docs/expressions), [Executions](/docs/executions), [Node catalog](/docs/nodes).

## Explore further

- [Features - nodulz](https://nodulz.com/product/overview)
- [Node catalog - nodulz](https://nodulz.com/product/catalog)
- [MCP server - nodulz](https://nodulz.com/product/mcp)
- [Pricing - nodulz](https://nodulz.com/pricing)
- [Use cases and workflow automation - nodulz](https://nodulz.com/use-cases)
- [Choose what your workflows can do. - nodulz](https://nodulz.com/compare)
- [Documentation - nodulz](https://nodulz.com/docs)