Integrations
Set up Microsoft 365 Agent credentials in Duaer
Store Microsoft 365 Agent connection details in Duaer for digital-organization nodes to use at runtime. Secrets are protected by the instance encryption key and are not written into node parameters.
Register an app for Microsoft Agent 365
The Duaer Microsoft 365 Agent API credential is used by Microsoft Agent 365 Trigger:
- In the Microsoft Entra admin center, create an app registration and put its Directory (tenant) ID and Application (client) ID in Tenant ID and Client ID.
- Create a client secret under Certificates & secrets and put it in Client Secret.
- Set up the agent for this app in Microsoft 365 and use the webhook URL shown in Microsoft Agent 365 Trigger as the messaging endpoint.
Microsoft Agent 365 Trigger registers a webhook with the service, so Duaer must be reachable from the internet.
Microsoft 365 Agent API fields in Duaer
In Duaer, choose Microsoft 365 Agent API when you create a credential, then fill in these fields:
- Tenant ID (required)
- Client ID (required)
- Client Secret (required, secret)
Duaer nodes that use it: Microsoft Agent 365 Trigger.
Save the connection in Duaer
Open Credentials and create Microsoft 365 Agent. Fill in the key, OAuth, or server fields. After you save, digital-organization nodes reference this credential instead of putting the secret in a parameter.
Credential values are protected by the instance encryption key. If you change or lose that key, stored credentials cannot be decrypted. See the hosting notes on encryption keys.
Who can use this credential
Who can see or edit it follows projects and roles. Do not paste secrets into chat or variables. External vaults are covered under external secrets.
Questions
Do Microsoft 365 Agent secret values appear in Duaer node parameters?
No. In Duaer, Microsoft 365 Agent secrets stay in the credential. Nodes only reference the credential. Execution records should not show the plaintext secret either.
What usually stops a Microsoft 365 Agent credential from saving in Duaer?
Wrong fields, an OAuth callback that does not match the instance URL, or a role that cannot create credentials. Check the fields Microsoft 365 Agent expects, then confirm you can create credentials in that project.
In this section
Built-in integrations in Duaer
Built-in triggers, actions, and credentials in Duaer. Triggers start a digital organization. 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.