🎯 What is it?

Dust agents can now create and modify Google Drive files directly. This means your agents can generate new Google Docs, Sheets, and Slides from scratch, edit existing documents, add comments, format content, and even insert tables—all without you having to do it manually.

💡 Why is it useful?

Until now, agents could only read your Google Drive files. This limitation meant that after analyzing data or processing information, you still had to manually create documents or update spreadsheets with the results. This new capability removes that friction entirely, allowing your agents to complete the full workflow: from analysis to documentation to sharing.

⚙ How does it work?

When you connect your Google Drive to Dust using the enhanced OAuth permissions (drive.file scope), your agents gain the ability to perform write operations on Google Docs, Sheets, and Slides. They can create new files, clone templates, edit content, format text, and manage comments.

✨ Concrete Use Cases

Here's how you could use it:

Weekly Report Generation: Your agent analyzes your team's project management data, identifies key metrics and blockers, then automatically creates a formatted Google Doc with action items—ready to share with stakeholders.

Meeting Notes & Follow-ups: After a meeting transcription is processed, your agent creates a Google Doc with structured notes, extracts action items into a tracking spreadsheet, and adds comments tagging relevant team members.

Data Pipeline to Spreadsheet: Your agent pulls sales data from multiple sources, performs analysis, then updates a Google Sheet with the latest figures for your monthly review.

Project Status Updates: Your agent monitors project channels, synthesizes updates, and automatically updates your project status document in Google Docs with formatted sections and tables.

📈 Benefits for you

• Save hours of manual work: Eliminate the copy-paste cycle between analysis and documentation

• Maintain consistency: Agents follow your templates and formatting standards every time

• Enable end-to-end automation: Complete workflows from data gathering to polished deliverables

• Improve collaboration: Agents can comment and tag team members directly in documents

🚀 How to access it?

If you already have Google Drive connected to Dust, you'll be prompted to re-authenticate with the updated permissions the next time an agent attempts a write operation. If you're new to this integration, simply connect Google Drive from your Dust connections settings, and all write capabilities will be available immediately to your agents.

🎯 What is it?

You can now react to messages with emojis and share direct links to specific messages within Dust conversations. This enhancement makes it easier to reference important points, navigate through discussions, and express quick feedback without writing a full response.

💡 Why is it useful?

As conversations grow longer and more collaborative, it becomes harder to track key decisions, highlight important information, or quickly acknowledge messages. Emoji reactions provide a lightweight way to respond, while message links allow you to jump directly to or reference specific points in a conversation—no more endless scrolling to find "that one message."

⚙ How does it work?

Simply hover over any message in a conversation to reveal the reaction and link options. Click to add an emoji reaction, or copy the message link to share it with your team or bookmark it for later reference.

✨ Concrete Use Cases

Here's how you could use it:

Team alignment: React with a ✅ to show agreement on a decision without cluttering the conversation with "+1" messages, helping your team quickly see consensus.

Knowledge sharing: Copy a direct link to a valuable assistant response (like a complex analysis or summary) and share it in your team channel or documentation, making it easy for colleagues to find exactly what they need.

Follow-up tracking: Use 👀 reactions to show you've seen an important update, or react with ❓ to flag messages that need clarification, creating visual cues for what requires attention.

📈 Benefits for you

• Save time: No need to write short acknowledgment messages—a quick emoji does the job

• Better navigation: Jump directly to key messages instead of searching through long conversations

• Clearer communication: Visual reactions help the whole team understand what's important, what's been addressed, and what needs attention

• Enhanced collaboration: Make conversations more dynamic and easier to follow for everyone involved

🚀 How to access it?

This feature is now available to all Dust users in all conversations—no setup required! Just hover over any message to start using reactions and message links right away.

🎯 What is it?

Granola's official MCP (Model Context Protocol) server is now directly configurable within Dust. This native integration allows your Dust assistants to seamlessly access and interact with your Granola meeting data.

💡 Why is it useful?

If you use Granola to record and manage your meetings, you can now leverage that valuable meeting information directly within your Dust workflows. No more switching between tools or manually copying meeting notes—your assistants can automatically retrieve and work with your meeting data.

⚙️ How does it work?

Once configured, the Granola MCP server connects your Granola account to Dust, enabling your assistants to query meetings, retrieve specific meeting details, and list your meeting history.

✨ Concrete Use Cases

Here's how you could use it:

Meeting Follow-up Assistant: Create an assistant that automatically pulls action items from recent Granola meetings and drafts follow-up emails to participants.

Weekly Meeting Digest: Build a workflow that compiles summaries of all your team meetings from the past week, highlighting key decisions and next steps.

Meeting Prep Assistant: Set up an assistant that retrieves notes from previous meetings with a specific client or on a particular topic to help you prepare for upcoming discussions.

📈 Benefits for you

• Save time: No more manual copying of meeting notes into other tools

• Better context: Your assistants have full access to meeting history and insights

• Streamlined workflows: Combine meeting data with other information sources in Dust for more powerful automation

🚀 How to access it?

If you're a Granola user, head to your Dust workspace settings, navigate to the MCP servers configuration section, and add the Granola official MCP server. Once connected, your assistants will be able to access your Granola meetings data.

CSV Export for Programmatic Cost Chart

🎯 What is it?

You can now export your programmatic cost chart data as a CSV file directly from the Credits & Usage page. A simple export button has been added to make downloading your usage data quick and easy.

💡 Why is it useful?

Until now, analyzing usage trends or sharing cost data with your team required manual copying or screenshots. This export feature gives you direct access to the raw data, making it easier to perform custom analysis, create reports, or integrate usage information into your own tracking systems.

✨ Concrete Use Cases

Here's how you could use it:

Finance & Budget Tracking: Export monthly cost data to build custom dashboards in Excel or Google Sheets, compare usage across time periods, or create budget forecasts based on historical trends.

Team Reporting: Download usage data to share with leadership or finance teams in a format they can easily work with, without requiring them to access Dust directly.

📈 Benefits for you

• Better visibility: Analyze your AI usage patterns with your preferred tools

• Time savings: No more manual data collection or screenshot sharing

• Flexibility: Create custom reports and charts tailored to your specific needs

• Transparency: Share detailed usage information with stakeholders in a familiar format

🚀 How to access it?

Head to your Credits & Usage page—the CSV export button is already available for all users. Simply click the export button on the programmatic cost chart to download your data.

🎯 What is it?

Dust now integrates with Atlassian Statuspage through a dedicated MCP (Model Context Protocol) server. Your agents can now directly interact with your Statuspage infrastructure to manage incidents, update component statuses, and monitor your system's health—all through natural conversation.

💡 Why is it useful?

When an incident occurs, speed and coordination are critical. This integration eliminates context-switching between tools and enables your DevOps teams and SREs to manage incident communication workflows without leaving Dust. Instead of manually logging into Statuspage to update statuses or create incident reports, your agents can handle these tasks instantly based on your instructions or automated triggers.

⚙️ How does it work?

Admins configure the integration by adding their Statuspage API key to Dust. Once set up, agents can access Statuspage on-demand to perform key operations: listing pages and components, checking ongoing incidents, creating new incidents, updating incident details, and marking components as experiencing outages.

✨ Concrete Use Cases

Here's how you could use it:

Automated Incident Response: Ask an agent "Create a Statuspage incident for the API outage we're experiencing" and it instantly creates the incident, sets the appropriate component status, and can even draft customer-facing updates based on your internal incident notes.

Status Monitoring Dashboard: Configure an agent to regularly check your Statuspage for ongoing incidents and provide morning briefings to your on-call team, summarizing what's currently under maintenance or experiencing issues.

Coordinated Communication: During an incident, ask your agent to "Update the database incident with investigating status and ETA of 30 minutes" while you focus on actually resolving the technical issue.

📈 Benefits for you

• Faster incident response: Reduce the time between detection and public communication

• Reduced cognitive load: Let agents handle status updates while your team focuses on resolution

• Consistent communication: Ensure incident updates follow your established workflows and templates

• Centralized operations: Manage incident communication alongside your other operational tasks in Dust

🚀 How to access it?

This integration is available on-demand for all Dust users with a Statuspage account. Workspace admins need to configure the Statuspage API key in your Dust workspace settings. Once configured, simply enable the Statuspage capability for any agent that needs incident management access.

🎯 What is it?

The Agent Builder now features a comprehensive observability dashboard that gives you real-time visibility into how your agents are performing. You can track usage trends, monitor which tools are being executed, analyze user feedback, measure response times, and understand how your retrieval systems are behaving—all linked to specific versions of your agents.

💡 Why is it useful?

AI agents often fail quietly in production. A prompt change might slow down responses, a tool update could break a workflow, or retrieval quality might degrade—and you won't know until frustrated users report it. This dashboard shifts you from reactive troubleshooting to proactive monitoring, letting you catch issues before they impact your team and understand the real-world impact of every change you make.

⚙ How does it work?

The dashboard automatically collects performance data from your agents in real-time. Every conversation, tool execution, and retrieval query is tracked and visualized, with metrics tied to specific agent versions so you can compare performance before and after changes.

✨ Concrete Use Cases

Here's how you could use it:

Validate prompt improvements: You updated an agent's instructions to be more concise. Check the dashboard to see if average latency decreased and if user feedback scores improved compared to the previous version.

Debug tool execution issues: Users mention an agent isn't providing complete answers. The dashboard reveals that a specific API tool is timing out 40% of the time, pointing you directly to the problem.

Optimize retrieval quality: After adding new documents to your knowledge base, monitor RAG behavior metrics to ensure the agent is retrieving relevant information and not getting overwhelmed by irrelevant context.

Track adoption and impact: See which agents are being used most frequently, during what times, and by which teams—helping you prioritize maintenance and development efforts.

📈 Benefits for you

• Catch problems early: Identify performance degradation or failures before they become widespread issues

• Make data-driven decisions: Understand the real impact of configuration changes instead of guessing

• Save troubleshooting time: Pinpoint the exact version and component causing issues

• Build confidence: Deploy agent updates knowing you can monitor their real-world performance immediately

🚀 How to access it?

Open any agent in the Agent Builder. You'll find the new Insights tab alongside your existing configuration options. The dashboard is available immediately for all users—no setup or activation required.

📌 Context

To help you maintain better control over your costs and protect against unexpected spending spikes, we've introduced a daily spending cap for all API (programmatic) usage on Dust.

This safeguard automatically monitors your API consumption and prevents runaway costs from accidental loops, misconfigured scripts, or unexpected usage patterns.

🔄 Impact on Dust

We've implemented real-time tracking that:

• Monitors your API spending throughout the day

• Automatically resets at midnight UTC each day

• Uses a fail-safe approach: if our tracking system encounters any issues, API calls are temporarily blocked to ensure you're never surprised by unexpected charges

👤 Impact for you

Default limits:

• Standard workspaces: $1,000 per day

• Pay-as-you-go workspaces: The greater of $1,000 or 20% of your monthly spending cap, per day

What this means:

• For most customers, daily API usage will continue without any interruption

• If you approach your daily cap, API calls will be blocked until the next day (midnight UTC)

• You'll have full visibility into your spending and won't encounter surprise bills from runaway usage

Need a different limit?

If your typical API usage requires a higher daily cap, you can request a custom limit between $100 and $10,000 through your account settings or by contacting your Customer Success Manager.

✅ Actions required

No immediate action required for most customers. Your existing API integrations will continue to work within the default daily limits.

Optional: If you regularly use the API extensively, we recommend:

1. Reviewing your typical daily API spending patterns

2. Contacting us if you need to adjust your daily cap to match your usage

3. Implementing monitoring in your applications to track daily usage

This change is live for all workspaces starting today.

🎯 What is it?

You can now export any Frame as a PDF document directly from Dust. When exporting, you can choose between portrait or landscape orientation to best fit your content. Enterprise plans receive clean PDFs without any branding, while other plans include a discreet "Created with Dust" footer.

💡 Why is it useful?

Frames are powerful visual tools for data analysis, reports, and presentations within Dust. However, many of you needed to share these insights outside the platform—whether for compliance documentation, distribution to external vendors, or integration into company repositories like SharePoint. This was one of your most requested features, and we're excited to make sharing your work effortless.

⚙ How does it work?

Simply open any Frame and select the export option. Choose your preferred orientation (portrait or landscape), and Dust will generate a PDF version of your Frame in seconds. The export handles most Frame layouts automatically.

✨ Concrete Use Cases

Here's how you could use it:

Compliance & Documentation: Export weekly analytics Frames as PDFs for compliance archives or audit trails in your document management system.

External Reporting: Share performance dashboards or project status Frames with external partners, vendors, or clients who don't have Dust access.

Executive Presentations: Convert data visualizations into PDFs for inclusion in board presentations, SharePoint libraries, or email distributions.

Offline Access: Create PDF versions of critical Frames for offline reference during travel or in low-connectivity environments.

📈 Benefits for you

• One-click sharing: Transform interactive Frames into universally accessible PDF documents instantly

• Professional output: Clean, presentation-ready documents suitable for any audience

• Flexibility: Choose the orientation that best showcases your content

• Broader reach: Share your Dust insights with anyone, regardless of their access to the platform

🚀 How to access it?

The feature is already live for all users! Simply navigate to any Frame you've created or have access to, and look for the export/PDF option. No setup or activation required—start exporting today.

Note: While PDF export is designed to handle a wide variety of Frame layouts—from standard reports to advanced visualizations—we're continuously improving the feature to support even the most creative Frame designs. If you encounter any issues with specific layouts, please let us know so we can refine the experience.

🎯 What is it?

Admins can now set a spending limit on individual API keys. Each key can have its own maximum dollar amount for API usage, calculated on a 30-day rolling basis. This gives you precise control over how much each API integration or user can spend.

💡 Why is it useful?

As your team scales and more people use Dust programmatically, it becomes harder to track and control costs at a granular level. Until now, your only option was a workspace-wide limit. This new feature helps you prevent budget overruns, test new integrations safely, and allocate resources more strategically across different projects or teams.

⚙️ How does it work?

Simply set a dollar cap when creating or editing an API key. Once the key reaches that spending limit within any 30-day period, it will stop working until the rolling window resets. Keys without a cap continue to use the workspace's overall limit.

✨ Concrete Use Cases

Here's how you could use it:

Testing environment: Set a $50 cap on API keys used for development and testing to avoid unexpected costs from runaway scripts or experiments.

Team allocation: Give your marketing team an API key with a $500 monthly cap and your engineering team a separate key with a $2,000 cap, matching each team's actual needs and budget.

Third-party integrations: When connecting Dust to external tools or contractors, set conservative limits to control costs while you evaluate usage patterns.

📈 Benefits for you

• Better budget control: Prevent individual integrations or users from consuming your entire workspace credit unexpectedly

• Safe experimentation: Test new use cases without risking your full budget

• Clearer accountability: Track and manage costs at the team or project level

• Flexible scaling: Adjust limits as needs change without affecting your entire workspace

🚀 How to access it?

Admins can access this feature in the Dust workspace settings, under the API Keys section. When creating a new API key or editing an existing one, you'll find the option to set a usage cap. No action is required if you prefer to keep your current setup—API keys without a cap will continue to work as before, limited only by your workspace's overall limit.

🎯 What is it?

Your Dust notification emails now include an AI-generated summary of unread messages. Instead of just being notified that you have new activity, you'll see a concise overview of what's been discussed directly in your inbox.

💡 Why is it useful?

We know your inbox is busy, and context switching takes time. With this update, you can quickly assess what's happening in your Dust conversations without needing to immediately open the app. This helps you prioritize which conversations need your immediate attention and which can wait.

⚙ How does it work?

When you have unread messages in a Dust conversation, the notification email you receive will automatically include a brief summary of the key points discussed. This summary is generated to give you the essential context at a glance.

✨ Concrete Use Cases

Here's how you could use it:

Prioritizing your morning: Scan your email summaries over coffee to decide which conversations need your immediate input and which can be reviewed later in the day.

Staying informed on-the-go: Quickly catch up on team discussions from your mobile email app while commuting, without needing to switch apps or log into Dust.

📈 Benefits for you

• Save time: Get context without opening multiple apps

• Stay informed: Keep up with important conversations even when you're away from Dust

• Better prioritization: Quickly identify which messages need your urgent attention

🚀 How to access it?

This feature is already active for all users. No setup required—your next notification email will automatically include summaries when you have unread messages.