Hi Dust team,
We are building an external front-end application for one of our clients that calls the Dust API to run agents. We have run into a behavior that is not documented and would love some clarification.
Setup
We have configured three Outlook tool connections in our Dust workspace:
Admin DSA ā configured as Personal account
Wensheila ā configured as Personal account
Hugo's mailbox ā configured as Shared account
Observed behavior
When agents are called directly from the Dust interface, all three connections work as expected.
When the same agents are called via the Dust API from our external front-end, only the Shared connection (Hugo's mailbox) is accessible. The Personal connections (Admin DSA and Wensheila) appear to be unavailable or silently fall back to Hugo's mailbox.
What we have tried
We identified that the front-end was incorrectly sending a sharedMailboxAddress parameter for Personal account connections, which caused 404 - Default folder AllItems not found errors. We corrected that on the front-end side. However, the routing issue between Personal and Shared connections persists when calling via API.
Questions
- 1.
Is there a known difference in how Personal vs Shared Outlook connections behave when accessed via the Dust API from an external application?
- 2.
Is there a recommended way to configure Outlook connections intended for use via the API, rather than directly from the Dust interface?
- 3.
Should Personal account connections always be converted to Shared account connections for API-based use cases?
This behavior is not covered in the current documentation (docs.dust.tt/docs/ā¦/microsoft-outlook), and we think it would be worth documenting for teams building on top of the Dust API.
Thanks a lot for your help.
