Task catalogue / Microsoft Teams
Verified against Flow 5.0.0-beta.39
The Microsoft Teams category has 3 tasks. Each entry shows the task's latest revision, the one the palette adds. See Reading an entry.
Adds a user to a team as a member or an owner through Microsoft Graph. The app registration needs the TeamMember.ReadWrite.All application permission (TeamMember.ReadWriteNonOwnerRole.All for members only). Guests cannot be added with application permissions. See https://learn.microsoft.com/en-us/graph/api/team-post-members
add-teams-membertemplateParameters
| Label | Name | Type | Required | Default | Helper text |
|---|---|---|---|---|---|
| Tenant ID | tenantId |
Text | Yes | $(workspace.params.microsoft-tenant-id) |
Defaults to the tenant ID the workspace's Microsoft integration shares; or enter the Directory (tenant) ID of an Entra app registration |
| Client ID | clientId |
Text | Yes | $(workspace.params.microsoft-client-id) |
Defaults to the client ID the workspace's Microsoft integration shares; or enter the app registration's Application (client) ID |
| Client Secret | clientSecret |
Secured | Yes | $(workspace.params.microsoft-client-secret) |
Defaults to the client secret the workspace's Microsoft integration shares; or enter one of the app registration's. The task gets its own app-only Microsoft Graph token with it |
| Team ID | teamId |
Text | Yes | The team's ID (its Microsoft 365 group ID) | |
| User | user |
Text | Yes | The user's user principal name (e.g. jo@contoso.com) or object ID | |
| Role | role |
Select | No | member |
Results
| Name | Description |
|---|---|
membershipId |
The membership's ID |
userId |
The user's object ID |
Creates a standard or private channel in a team through Microsoft Graph. The app registration needs the Channel.Create application permission. See https://learn.microsoft.com/en-us/graph/api/channel-post
create-teams-channeltemplateParameters
| Label | Name | Type | Required | Default | Helper text |
|---|---|---|---|---|---|
| Tenant ID | tenantId |
Text | Yes | $(workspace.params.microsoft-tenant-id) |
Defaults to the tenant ID the workspace's Microsoft integration shares; or enter the Directory (tenant) ID of an Entra app registration |
| Client ID | clientId |
Text | Yes | $(workspace.params.microsoft-client-id) |
Defaults to the client ID the workspace's Microsoft integration shares; or enter the app registration's Application (client) ID |
| Client Secret | clientSecret |
Secured | Yes | $(workspace.params.microsoft-client-secret) |
Defaults to the client secret the workspace's Microsoft integration shares; or enter one of the app registration's. The task gets its own app-only Microsoft Graph token with it |
| Team ID | teamId |
Text | Yes | The team's ID (its Microsoft 365 group ID) | |
| Channel Name | displayName |
Text | Yes | Up to 50 characters | |
| Description | description |
Text Area | No | ||
| Membership | membershipType |
Select | No | standard |
A standard channel is open to the whole team; a private one to its members |
| Owner | owner |
Text | No | Required for a private channel: the owner's user principal name (e.g. jo@contoso.com) or object ID |
Results
| Name | Description |
|---|---|
channelId |
The new channel's ID |
channelUrl |
The channel's link in Teams |
Posts a message to a Teams channel or chat through a Teams Workflows webhook (the 'Post to a channel when a webhook request is received' template), as an Adaptive Card. The retired Office 365 connector webhooks are not supported.
send-teams-messagetemplateParameters
| Label | Name | Type | Required | Default | Helper text |
|---|---|---|---|---|---|
| Webhook URL | webhookUrl |
Secured | Yes | The workflow's HTTP POST URL. It carries the webhook's signature, so it is kept like a password | |
| Title | title |
Text | No | Shown large and bold above the message | |
| Message | message |
Text Area | No | The message text; Teams renders a subset of Markdown | |
| Adaptive Card | card |
json |
No | A whole Adaptive Card (type AdaptiveCard), or a whole webhook message (type message), sent instead of Title and Message |
No results.