How to automate your Dust agents with workflow tools (2026)
Davis Christenhuis
Dust agents understand your company. They search your knowledge sources, reason about context, and produce answers grounded in what your business actually knows.
But most agents wait passively until someone asks them a question.
That changes with Triggers. Dust now lets your agents run automatically, via schedules or webhooks, and write results directly back to your tools. No third-party workflow platform required for the most common automation patterns.
For more complex orchestration across your stack, platforms like Zapier, Make, n8n, Power Automate, and viaSocket extend what your agents can do. This article covers both paths.
📌 TL;DR
Short on time? Here's what this article covers:
- Two ways to automate: Use native Triggers (built into Dust) to schedule agents or fire them via webhooks, or connect automation platforms like Zapier, Make, and n8n for complex multi-step workflows.
- How to set it up: Open the Triggers section in your agent builder, set a schedule or webhook, then configure where results get written — or connect through the Conversation API if you're using an external platform.
- What you can automate: Lead enrichment, support ticket routing, meeting follow-up, document processing, and outreach drafting all work without manual intervention.
- When to use each approach: Native Triggers for straightforward workflows within Dust-connected tools; automation platforms when you need conditional logic or write-back to unsupported tools.
- Key benefit: The same agent you query manually can run on autopilot using identical instructions, permissions, and knowledge sources.
How automation works in Dust
Automating a Dust agent means configuring it to run without manual input — either on a schedule you set or when triggered by an event in your tools.
Native Triggers (built in, no extra tools needed)
Triggers are built directly into the agent builder. You can set an agent to:
- Run on a schedule: Describe it in plain language ("every Monday at 9 AM," "first Friday of each month") and Dust handles the rest.
Once triggered, agents can write results back to your tools directly through Dust's connected platforms: Slack, Notion, HubSpot, GitHub, and more. For tools without native write-back, use an automation platform to bridge the gap.
Automation platforms (for complex multi-step workflows)
When you need logic that spans multiple tools, conditional branching, or write-back to a destination Dust doesn't natively support, platforms like Zapier, Make, n8n, Power Automate, and viaSocket connect to Dust through the Conversation API. The same agent handles requests from any platform using the same instructions, knowledge sources, and permissions.
The patterns below work with either approach. Use native Triggers when the workflow is straightforward. Bring in an automation platform when the orchestration gets complex.
1. Enrich new leads with company context
Lead enrichment automation means researching prospects the moment they enter your CRM and writing summaries back without manual lookup.
What happens:
- A new contact or company record is created in HubSpot or Salesforce
- A Dust agent receives the lead's details via webhook or automation trigger
- The agent searches your product docs, sales playbooks, and past deal notes
- A structured enrichment summary is written back to the CRM record
When the rep opens it, the homework is done.
Works with: HubSpot and Salesforce (native integrations), or CRMs like Pipedrive via an automation platform.
2. Route and respond to support tickets
Support ticket routing uses AI to draft responses for simple questions and route complex issues to the right team member with full context.
What happens:
- A new ticket is created in Zendesk, Intercom (US-hosted workspaces only), or your helpdesk
- A Dust agent receives the ticket subject, description, and customer metadata
- The agent searches your help center, internal docs, and past resolutions
- Simple tickets get a drafted response; complex tickets get a summary with routing guidance
Your support team still owns the relationship. The agent handles the repetitive lookup work.
Works with: Zendesk and Intercom (native integrations; Intercom is available for US-hosted workspaces only), Freshservice, or helpdesks like Freshdesk via an automation platform.
3. Send outreach when intent is highest
Outreach automation means drafting personalized messages based on high-intent signals and your team's existing knowledge about the account.
What happens:
- Your CRM flags a behavioral signal or deal stage change
- A Dust agent receives the prospect's context
- The agent reviews past interactions, relevant case studies, and product-fit notes from your connected data
- A personalized draft is returned for the rep to review and send
The agent handles research and first drafts. The rep edits and sends.
Works with: HubSpot, Salesforce, and Gmail (native integrations), or tools like Apollo via an automation platform.
4. Turn meeting transcripts into next steps
Meeting automation extracts action items from transcripts, assigns owners, sets due dates, and writes tasks to your project management tool automatically.
What happens:
- A meeting transcript becomes available
- A Dust agent receives the full transcript
- The agent identifies decisions, action items, objections, and follow-ups, structured by owner
- Output is written to the CRM record, Notion, Linear, or Slack
Every conversation contributes to shared knowledge without manual follow-up.
Works with: Gong (native integration), or transcription tools like Grain, Fireflies, and Otter by uploading transcripts or connecting via an automation platform.
5. Process documents without the busywork
Document processing automation summarizes uploaded files, flags key clauses, and routes them to the right reviewer automatically.
What happens:
- A new file is uploaded to Google Drive, Dropbox, or a shared folder
- A Dust agent receives the document content
- The agent extracts key clauses, flags potential risks, and produces a structured summary
- The summary is posted to Slack, saved to your knowledge base, or both
Legal and ops teams focus on clauses that require judgment rather than reading every line.
Works with: Google Drive and OneDrive, or storage tools like Dropbox via an automation platform or manual import.
How Malt automated support ticket routing with Make and Dust
Malt, a freelance marketplace operating across Europe, faced a common support challenge: their team handled thousands of tickets across multiple countries, each requiring different expertise (legal compliance, payment issues, profile optimization). Support agents spent significant time manually researching answers and routing complex tickets.
The team built an automated workflow using Make and Dust that handles ticket routing and response drafting:
The workflow:
- Support agent adds a specific tag to a ticket in FrontApp
- Make automatically fetches the ticket content
- A Dust dispatcher agent analyzes the ticket and routes it to specialized agents:
- Legal and Compliance Agent for documentation requirements across countries
- Profile Visibility Agent for freelancer profile optimization guidance
- Payments Agent for transaction history and payment queries
- The appropriate agent drafts a response using templates and Malt's knowledge base
- The draft appears back in FrontApp for the support agent to review and send
Results: Malt cut ticket closing time by 50%. Support agents now handle tickets faster and more accurately, and the workflow was quickly adopted in newly launched territories, where support teams found the most value because of the size of Malt’s knowledge base.
The workflow uses Make to connect FrontApp to Dust, but the pattern works with any automation platform and ticketing system. The key was creating specialized agents for different ticket types rather than one generic agent trying to handle everything.
💡 Want to see how other teams automate their workflows? Read more customer stories →
Getting started with Dust
You don't need to automate every agent at once. Start with a single workflow that solves a problem your team already has, then expand from there.
To use native Triggers:
- Open the agent builder and go to the Triggers section
- Set a schedule or configure a webhook
- Your agent starts running automatically from there
- No additional tools required
To connect an automation platform: Use whichever one your team already runs:
- Zapier and Make are the simplest starting points with visual builders
- n8n is required to be self-hosted to use the Dust node (it's not yet available on n8n Cloud), making it best suited for teams already running self-hosted infrastructure
- Power Automate (requires a Premium license) is the native choice for Microsoft-heavy environments
- viaSocket is a good option for broad SaaS connectivity
All platforms connect to Dust through the Conversation API using the same agent instructions, permissions, and knowledge sources.
Start with one workflow. Pick the pattern closest to a problem your team already has, build it, and see what changes.
💡 Ready to set up your first scheduled agent or webhook trigger? Try Dust 14 days free →
Frequently asked questions (FAQs)
Can I automate Dust agents without using Zapier or Make?
Yes. Dust's native Triggers let you schedule agents or fire them via webhooks without any third-party platform. You can set an agent to run every Monday at 9 AM or react to events from GitHub, Jira, and Zendesk. For workflows that stay within Dust-supported tools, you don't need external automation. Zapier and similar platforms are only necessary when you need complex branching logic or write-back to tools Dust doesn't natively support.
What's the difference between a scheduled trigger and a webhook trigger?
A scheduled trigger runs your agent at specific times you define in plain language — "every Friday at 3 PM" or "first Monday of each month." A webhook trigger fires your agent the moment an event happens in an external system, like when a new ticket is created or a lead fills out a form. Scheduled triggers work for recurring reports or cleanup tasks. Webhook triggers are better for real-time responses to external events.
Can a Dust agent write directly to my CRM or project management tool?
Yes, if your tool is connected to your Dust workspace. Dust agents can write results back to HubSpot, Notion, Slack, GitHub, and other supported platforms natively. For tools Dust doesn't support directly, use an automation platform to receive the agent's response and write it wherever you need.
Do I need to create a separate agent for each automated workflow?
Not necessarily, but it often helps. One agent can handle a range of related tasks, but specialized agents tend to perform better on specific workflows. A focused agent with a clear purpose is easier to tune and more reliable than a general-purpose one.