Microsoft Teams n8n integrationAutomate Microsoft Teams with n8n.

Adds a channel to an existing team, so the next node has somewhere to post.

• Team: pick from the list, by URL, or by ID, where the ID is the groupId parameter in the URL you get from Get a link to the team.
• New Channel Name: the name of the channel to create.
• Type (in Options): Standard is accessible to everyone on the team, Private only to a specific group of people within it.

Two pointers are enough to remove a channel: the team it belongs to, and the channel itself.

• Team: the team that owns the channel, selected from the list, by URL or by ID.
• Channel: the channel to delete, where the ID is the threadId in the channel URL. Coming from a previous node, this is usually an expression such as {{ $json.id }}.

Returns one channel, which is what you want before acting on it or to resolve a name into usable data.

• Team: the team the channel belongs to.
• Channel: the channel to read, from the list, by URL or by ID (the threadId in the URL).

Lists the channels of a team as separate items, one per channel, ready to loop over.

• Team: the only required field, since channels are always read inside one team.
• Return All: on, n8n walks through the pages of the API and brings back every channel; off, Limit caps how many come back.

Renames a channel or rewrites what it is for, without touching the messages inside it.

• Team and Channel: the channel to edit, both resolved from the list, an URL or an ID.
• Name: the new channel name, left empty if only the description changes.
• Description (in Options): the text that explains the channel to whoever joins it.

Posts a message into a channel, which is how most workflows end.

• Content Type: Text for a plain line, HTML when the message needs bold text, a list or a link.
• Message: the content itself, usually assembled with an expression such as {{ $json.summary }}.
• Reply to ID (in Options): posts inside an existing thread; the message ID is the number before ?tenantId in the message URL, for example 1673348720590.
• Include Link to Workflow (in Options): appends a link to the workflow, useful once many of them post.

Reads messages from one channel so the workflow can count, filter or summarize them.

• Team and Channel: the channel to read from.
• Return All: on, every message comes back page after page; off, Limit stops at a fixed number, which is what you want while testing.

Same idea as a channel post, aimed at a private conversation instead, so there is no team to select.

• Chat: the conversation, picked from the list, by URL, or by ID, which you find after conversations/ in the chat URL.
• Content Type: Text or HTML, same choice as in a channel.
• Message: the content to send.
• Include Link to Workflow (in Options): adds a link back to the workflow that sent it.

One message, fetched by its identifier, with its content and metadata.

• Chat: the conversation that holds the message, the ID being what follows conversations/ in the URL.
• Message ID: the identifier of the message to retrieve, for example 1673355049064, often taken from an earlier node with {{ $json.id }}.

When the whole conversation matters, this brings its messages back as items.

• Chat: the only required field, resolved from the list, an URL or an ID.
• Return All: on, the node pages through the full history; off, Limit caps the number of messages returned.

Execution pauses here. The node posts the message in a chat and the workflow resumes only once a human has answered, which is how you put a validation step inside an automation.

• Chat and Message: where to ask, and what to ask.
• Response Type: Approval for a decision taken from the message itself, Free Text for an answer through a form, Custom Form for a form you define.
• Type of Approval (in Approval Options): Approve Only, or Approve and Disapprove for two buttons.
• Limit Wait Time: caps how long the node waits before execution resumes.

A task needs a home before it needs a name: a team, a plan and a bucket, then a title.

• Team, Plan and Bucket: where the task lands, each picked from a list.
• Title: what the task says.
• Due Date Time (in Options): the deadline, in ISO 8601 format and always in UTC.
• Assigned To (in Options): who owns it.

Removes a task outright, and the identifier is the only thing it asks for.

• Task ID: the identifier of the task to delete, most often {{ $json.id }} from the node that listed or created it.

Before changing anything, a workflow usually reads the task first. This returns it in full.

• Task ID: the identifier of the task to retrieve, taken from a list operation or from whatever system stored it.

Two angles on the same data, chosen in one field: what a person has on their plate, or what a plan contains.

• Tasks For: Group Member for the tasks assigned to a member, Plan for the tasks in a group plan.
• Team and Plan: the scope of the read.
• Return All: on, every task comes back; off, Limit caps the result.

Progress moves, the task follows. Only the fields you fill are changed, the rest stays as it is.

• Task ID: the task to update.
• Percent Complete (in Update Fields): set it to 100 and the task counts as completed.
• Bucket or Plan (in Update Fields): move the task to another stage or another plan.
• Assigned To (in Update Fields): hand it to someone else, after selecting Team in the options.