Pipedream Microsoft Teams → n8n
3 Pipedream Microsoft Teams actions and 2 event sources, and the n8n nodes they become. Converted nodes keep your configured values; expressions like {{steps.x.$return_value}} are rewritten to n8n expressions. Pipedream app slug: microsoft_teams.
Actions
| Pipedream action | n8n | Fit |
|---|---|---|
| microsoft_teams-send-channel-message | Microsoft Teams channelMessage → create | Direct |
| microsoft_teams-send-chat-message | Microsoft Teams chatMessage → create | Direct |
| microsoft_teams-create-channel | Microsoft Teams channel → create | Direct |
Triggers (event sources)
| Pipedream trigger | n8n | Fit |
|---|---|---|
| microsoft_teams-new-channel-message | Microsoft Teams Trigger newChannelMessage | Check output |
| microsoft_teams-new-chat-message | Microsoft Teams Trigger newChatMessage | Check output |
Credentials
Create a Microsoft Teams credential in n8n (type microsoftTeamsOAuth2Api). Converted nodes reference it by name, so n8n links it on import when the names match. Pipedream connected accounts can't be exported and are deleted by April 30, 2027.
What "Fit" means
Direct: same operation, same inputs. Check output: the n8n node returns a different JSON shape, so later steps that read its result need a look. Partial: some options have no n8n equivalent. Mappings verified on 2026-10-13 against the Pipedream registry and n8n source.
Questions
Does n8n have a Microsoft Teams node?+
Yes. 3 of the 3 Pipedream Microsoft Teams actions listed here map to a native n8n node.
Will my Pipedream Microsoft Teams connection move to n8n?+
No. Pipedream exports only an account ID, never the token, and deletes connected accounts by April 30, 2027. Create a Microsoft Teams credential in n8n (type microsoftTeamsOAuth2Api) and select it on the converted nodes.
Are Pipedream Microsoft Teams triggers supported in n8n?+
2 of the 2 Pipedream Microsoft Teams event sources listed here have an n8n trigger node. The rest are rebuilt with a Schedule Trigger that polls the API, or a Webhook node.
What happens to code steps that call the Microsoft Teams API?+
Code steps keep working through a compatibility layer, and tokens read via this.<app>.$auth move to a secrets block in the Code node. Steps that use an npm SDK are rewritten to plain HTTP calls so they run on n8n Cloud.