Tools management
🪄 Tools enable users to enhance an agent with various abilities, allowing it to efficiently tackle complex scenarios by simultaneously carrying out multiple tasks.
The Spaces > Tools menu allows admins to view, add , remove and configure tools available to Dust users
Adding new tools
Clicking the Add Tool button will open a list of Dust-built tools
The interface to add a tool
The following tools are available by default for the admin to configure without further configuration
Check the changelog (or the Add Tools menu) regularly as more tools are added regularly
- Asana
- Canva
- Confluence
- Freshservice
- GitHub
- Gmail
- Google Calendar
- Google Drive
- Google Sheets
- Guru
- HubSpot
- Jira
- Linear
- Microsoft Drive
- Microsoft Excel
- Microsoft Teams
- Monday
- Notion
- Outlook
- Outlook Calendar
- Salesforce
- Slack
- Sound Studio
- Stripe
- Supabase
- Val Town
- Zendesk
- ...
Unlike connections, it is possible to add the same tool multiple times. This can be convenient when multiple teams use the same tool, with different configurations.
Configuring tools
Tools are customisable: you can change their name, and description. Those are only for organisation purposes, to help member of your workspaces distinguish the toolsets they have access to.
Access
User access is managed with the Sharing panel of a tool. Tools access can be granted to the whole workspace, or to specific Private Spaces by unchecking this toggle
User Approval Settings (Tool stakes)
Tools can give a lot of different capabilities to your agents, and we feel like your users needs to realise what is happening under the hood.
That's why we implemented a "Stake" level for every action of every tool, User Approval Settings.
- High stake tools need explicit user approval, every time the agent uses the tool, and it can not be skipped. This setting is recommended for any tool that can edit sensitive data or trigger important workflows (eg. "Send an email", "update CRM entry")
- Users can disable confirmations for low stake tools. This setting is recommended for non-impactful actions (eg. "read a website content" or "get Jira ticket")
- Never ask tools run automatically without user confirmation.
A list of tools, with drop-downs to select the stake of each action
Example of a Low-stake validation pop-up for the user.
Authentication
Depending on the nature of the tool to connect in Dust, the authentication flow might be different. Whenever possible, Dust supports OAuth authentication, and is the preferred authentication method.
When adding a tool that requires authentication, the OAuth flow will automatically be triggered to set up the connection. This allows you to securely connect to MCP servers that implement authentication requirements.
OAuth flow on the Asana tool
Personal vs Workspace credentials
When adding a tool that support OAuth authentication, you have the choice between Personal or Workspace credentials. Pick the one that is the most suitable for your use case.
- Workspace level credentials.
The authentication credentials you provide during setup will be shared by all users in this workspace when using these tools. - Personal level credentials.
Once setup for the workspace, each user will have to connect their own credentials to interact with these tools.
More information on Personal vs Workspace credentials
Updated 1 day ago