Integrations
Start a Duaer workflow with Microsoft Teams Trigger
In Duaer, Microsoft Teams Trigger starts a workflow when Microsoft Teams sends an event. It can listen for 5 events, such as New Channel, New Channel Message, New Chat, and 2 more.
Start a Duaer workflow with Microsoft Teams Trigger
- On the Duaer canvas, open the node panel, search for Microsoft Teams Trigger, and add it as the first node.
- Under Authentication, choose Teams OAuth2, Microsoft OAuth2 (Graph), or Service Principal (App-Only), then pick or create the matching credential (Microsoft Teams OAuth2 API, Microsoft OAuth2 API, or Microsoft Entra Service Principal) in Credential to connect with.
- Pick the events that should start a run, for example New Channel or New Channel Message.
- Select Execute step, then cause a real event in Microsoft Teams to capture a sample. Publish the workflow so Duaer registers the webhook and starts a run for every event.
Events that start a Duaer workflow with Microsoft Teams Trigger
- New Channel: A new channel is created.
- New Channel Message: A message is posted to a channel.
- New Chat: A new chat is created.
- New Chat Message: A message is posted to a chat.
- New Team Member: A new member is added to a team.
Questions
Which Microsoft Teams Trigger events can start a Duaer workflow?
Duaer's Microsoft Teams Trigger can listen for 5 events, including New Channel, New Channel Message, New Chat, New Chat Message, and New Team Member. Pick one or more on the node.
Does Microsoft Teams Trigger run before the Duaer workflow is published?
Only while you test with Execute step. Duaer registers the Microsoft Teams Trigger webhook for production runs after you publish.
Which credential does Microsoft Teams Trigger use in Duaer?
Duaer's Microsoft Teams Trigger uses Microsoft Teams OAuth2 API, Microsoft OAuth2 API, or Microsoft Entra Service Principal, depending on the method you choose under Authentication.
In this section
Built-in integrations in Duaer
Built-in triggers, actions, and credentials in Duaer. Triggers start a workflow. Actions run a step after it has started.
IntegrationsRisks of community nodes in Duaer
Before you install a community node in Duaer, know the code comes from a source the instance admin trusts, and know what permissions it gets.
IntegrationsTroubleshoot community nodes in Duaer
When a Duaer community node will not install or run, check the version, permissions, and node docs, then the instance logs.
IntegrationsMake custom API calls for an app in Duaer
When a Duaer app node does not expose the API you need, use HTTP Request and reuse that app’s saved authentication.
IntegrationsIntegrations in Duaer
Built-in triggers, actions, and credentials in Duaer. Community nodes are extra packages. Custom operations reuse saved authentication with HTTP Request.
CredentialsBuilt-in credentials in Duaer
Per-service credential notes for Duaer built-ins. The create flow is in the credentials overview; node docs link to the matching service page.
Create nodesCreate a custom node for Duaer
Write a node package for Duaer when built-in nodes and custom operations are not enough and you will reuse the step.