Integrations
Use Microsoft Agent 365 Trigger in Duaer
In Duaer, Microsoft Agent 365 Trigger starts a workflow when Microsoft Agent 365 sends an event.
Start a Duaer workflow with Microsoft Agent 365 Trigger
- On the Duaer canvas, open the node panel, search for Microsoft Agent 365 Trigger, and add it as the first node.
- Connect the sub-nodes it needs to the inputs under Microsoft Agent 365 Trigger (Chat Model, Memory, Tool, and Output Parser), starting with a Chat Model.
- In Credential to connect with, pick or create a Microsoft 365 Agent API credential.
- Check System Prompt, Enable Microsoft Work IQ Tools for A365, and Require Specific Output Format on the node.
- If needed, select Add Option for the optional settings listed below.
- Select Execute step, then cause a real event in Microsoft Agent 365 to capture a sample. Publish the workflow so Duaer registers the webhook and starts a run for every event.
Microsoft Agent 365 Trigger parameters in Duaer
- System Prompt
- Enable Microsoft Work IQ Tools for A365: Whether to allow the agent to use Microsoft MCP tools like Calendar, Email, and OneDrive to assist in completing tasks.
- Require Specific Output Format
Microsoft Agent 365 Trigger options in Duaer
Under Add Option, Microsoft Agent 365 Trigger offers Max Iterations and Welcome Message.
Sub-nodes Microsoft Agent 365 Trigger takes in Duaer
Connect sub-nodes to the inputs under Microsoft Agent 365 Trigger: Chat Model, Memory, Tool, and Output Parser. Each sub-node keeps its own credential and settings.
Questions
What do you set on Microsoft Agent 365 Trigger in Duaer?
In Duaer, Microsoft Agent 365 Trigger mainly takes System Prompt, Enable Microsoft Work IQ Tools for A365, and Require Specific Output Format.
Does Microsoft Agent 365 Trigger run before the Duaer workflow is published?
Only while you test with Execute step. Duaer registers the Microsoft Agent 365 Trigger webhook for production runs after you publish.
Which credential does Microsoft Agent 365 Trigger use in Duaer?
Duaer's Microsoft Agent 365 Trigger uses a Microsoft 365 Agent API credential. The secret stays in the credential, not in node parameters.
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.