Resources · Zapier integration

Dust Zapier integrationAutomate Dust with Zapier.

The Dust Zapier integration gives you 2 actions, 0 triggers and 0 searches. Dust never starts the automation by itself: another app always does, then Zapier hands Dust a document to store or a question for one of your agents.

See the 2 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Dust Zapier integration actually does

The integration links your Dust workspace to the other apps you use, through Zapier. Something happens in one of those apps, and Zapier either drops a piece of text into a Dust folder or sends a message to a Dust agent and collects the reply. Dust is the place where your custom AI assistants read your company data; Zapier keeps that data fed.

Three results people build with it. First, a knowledge base that grows on its own: every new support ticket lands in a Dust folder through Upload Document, with the ticket ID as its document ID, so agents can quote past cases. Second, a first draft waiting before anyone opens the request: Talk to an Agent sends the incoming text to an agent and brings back its answer, ready for the next step. Third, documents you can trace back: the document ID is yours to choose, so the ticket ID or the thread subject tells you later where each piece of text came from.

Now the limits. Zapier offers no Dust trigger, so nothing that happens inside Dust (a new conversation, a new agent) can start a Zap. There is no search step either: Zapier cannot look up an existing Dust document before writing. And the agent action waits a set time for the answer, which matters on long questions (more on that below).

If you are weighing tools, the Dust Make integration page covers the same app on Make, and the Make vs Zapier comparison is the next stop.

Vocabulary

Zapier vocabulary in one minute

Seven words come back on every line of this page. Here they are in plain English.

Zap
A Zap is a recipe that runs by itself: something happens in one app, and Zapier carries out the steps you lined up, for example a call to a Dust agent.
Trigger
The starting event of a Zap, such as a new ticket or a form reply. Dust offers none, so this slot always belongs to another app.
Action
A step Zapier performs after the start. With Dust it is one of two moves: file a text in a folder, or put a question to an agent.
Task
Zapier's billing unit. Each Dust upload or agent call that goes through counts as one, and your monthly allowance is a count of those.
Polling vs instant
Polling means Zapier asks the starting app for news on a timer. Instant means that app pings Zapier itself, so no check is awaited.
Filter
A checkpoint between steps: the Zap reaches Dust only if the incoming data passes your condition, otherwise that run ends there.
Connection
The link between Zapier and your Dust account, set up once. Every Dust step of every Zap then picks it from a list.
Cost

What a Dust Zap really costs

Dust is not a premium app, so it works on the free plan. The catch sits elsewhere.

  • Free plan100 tasks a month, unlimited Zaps
  • Zap size on Free2 steps: one trigger, one action
  • Premium appNo, Dust works on Free
  • BilledEach successful action, never the trigger

Only a completed action costs a task. The trigger is free, and so is every check Zapier runs to look for new items. A failed Dust upload is not counted. On the free plan you get 100 tasks a month, but only two-step Zaps: one trigger, one Dust action. Add a filter, or chain Talk to an Agent into a second action, and the Zap becomes multi-step, which needs a paid plan. Since Dust has no trigger, the check interval depends on the app that starts your Zap.

Connect

Connect Dust to Zapier in 3 steps

  1. 01

    Open your connections

    In your Zapier account, go to Apps and click + Add connection. You need a Dust account first, plus access to any folder or agent you did not create yourself but want the Zap to use.

  2. 02

    Pick Dust

    Type Dust in the search box of the dialog, select it, then click Add connection. A new tab opens on the Dust side so you can sign in with the account the Zap will act for.

  3. 03

    Grant access

    Sign in to Dust and allow Zapier into the account. The connection is saved once, and every later step that uses Dust picks it from a list, so you never repeat this part for a second Zap.

First Zap

Your first Zap: file urgent Zendesk tickets in Dust

GoalEach new Zendesk ticket that matches your rule becomes a document in a Dust folder, keyed by its ticket ID.

  1. 01

    Start with Zendesk

    Create a Zap and pick Zendesk with its new-ticket event as the trigger. Dust cannot open a Zap, so the starting point always belongs to another app.

  2. 02

    Test the trigger

    Run the test. Zapier brings back the three most recent tickets from your account, so you map fields on a real one instead of guessing what arrives.

  3. 03

    Add a filter

    From the plus icon, add Filter on the ticket priority, using the exact value you saw in the test sample. Pick a text rule for text and a number rule for numbers, or the filter never passes.

  4. 04

    Add the Dust action

    Choose Dust, then Upload Document. Type the folder name, map the ticket ID into Document ID, and the ticket text into Document Content.

  5. 05

    Test, then publish

    Test the Dust step and check the document in your folder. Then click Publish. With a filter, this is a three-step Zap, so it needs a paid plan.

Actions

Dust actions on Zapier

Dust gives you 2 actions. For each one: what it does for you, when to reach for it, and what to watch out for.

1

Talk to an Agent

Action

In Zapier“Send a message to a Dust agent and retrieve the answer”

Sends a message to one of your Dust agents and returns its reply to the Zap, so the next step can reuse it. You set the agent, the message, a timezone, plus the name and email shown in the conversation.

When to use it
a lead form arrives and you want an agent to draft the first answer from your internal docs.
Watch out
by default the step waits 30 seconds for the answer; switch Blocking off and you get a conversation ID instead.
2

Upload Document

Action

In Zapier“Upload a document to a Dust Data Source / Folder”

Writes plain text into a Dust folder under an ID you choose, which turns any app event into material your agents can read.

When to use it
store each closed ticket or email thread, with its ticket ID or subject as the document ID.
Watch out
the folder must exist in Dust before the Zap runs, and the content field only takes plain text.
When it breaks

When a Dust Zap breaks

Zapier links no help article to Dust, so the traps below are the general ones. They still bite.

Most failures here come from what the Zap expects to see, not from Dust. Four cases to keep in mind. If one shows up anyway, the Zapier troubleshooting page walks through a broken Zap step by step.

  • Old items never arrive

    A Zap only reacts to what happens after you publish it. Tickets already closed stay out of the Dust folder; loading that archive is a separate job.

  • The Zap feeds itself

    Post an agent reply back into the same helpdesk view the trigger watches, and each reply can start the Zap again, eating tasks on every lap.

  • A migration floods the folder

    Bulk-importing old tickets into the starting app can send Zapier a sudden wave of items, and its flood protection may hold that wave back.

  • Each ticket runs once

    On a polling trigger, Zapier remembers what it has already seen, so one ticket never starts the Zap twice nor sends Dust a second upload.
Need help

Need help automating Dust with Zapier?

A person reads every message.

FAQ

Dust Zapier integration: questions people ask

01Is the Dust Zapier integration free?
Yes, as long as the Zap stays at two steps. Dust is not a premium app, so the free plan accepts it, with 100 tasks a month and unlimited Zaps. The catch is size: on the free plan, a Zap holds one trigger and one action, nothing more. Since Dust has no trigger, your trigger comes from another app, and Dust takes the single action slot. As soon as you add a filter or a second action, for example to post the agent reply somewhere, you need a paid plan. No price is quoted here because plan grids change too often.
02How many tasks does a Dust Zap use?
One task per Dust action that completes successfully. The trigger costs nothing, and neither does any check Zapier runs to look for new items, however often it happens. If the Dust step fails, that run is not counted against your plan. In a Zap with several actions, each successful action counts on its own: a Zap that uploads a document and then asks an agent about it uses two tasks per run. On the free plan, that gives you 100 successful Dust actions a month to spend.
03Does the Dust integration run in real time?
It depends on the app that starts the Zap, because Dust has no trigger of its own. If that app offers an instant trigger, it calls Zapier the moment the event happens and the Dust action follows straight away, whatever your plan. If its trigger is polling, Zapier checks for new items on a timer: every 15 minutes on Free, every 2 minutes on Professional, every minute on Team and Enterprise. The editor marks instant triggers with a lightning bolt, so you can check before you build anything.
04What do you need to connect Dust to Zapier?
A Dust account, and access to whatever the Zap will touch. If an agent or a folder was set up by a colleague, your account needs read or write access to it. The connection itself goes through the Apps page of Zapier: add a connection, pick Dust, sign in on the tab that opens, and allow access. Before building an upload, create the destination folder in Dust, since the folder name is a required field and the step cannot invent one for you.
05Why does Talk to an Agent come back without an answer?
Usually because the agent took longer than the step was willing to wait. By default, the action waits 30 seconds for the agent's reply. With Blocking switched off, it does not wait at all and returns a conversation ID instead of the answer. So if your next step expects the reply text, keep Blocking on and give the agent questions it can handle within that window. Also check the required fields: agent, message, timezone, username and email must all be filled for the step to run.
06What if the Dust operation you want is not on Zapier?
Then Zapier cannot do it with this app today. The Dust app on Zapier exposes exactly two actions, Talk to an Agent and Upload Document, with no trigger and no search step. Anything else, such as reacting to an event inside Dust or reading an existing document before writing, falls outside what the editor offers. The practical route is to rethink the flow around those two actions, or to check whether another platform's Dust app covers the missing piece before you commit.
07Zapier, Make or n8n for Dust?
Judge by your scenario, not by brand. On Zapier, Dust gives you two actions and no trigger, so the flow always starts in another app. That suits pushing documents or questions into Dust. Check three things: whether the operation you need appears in the list, whether your Zap fits in two steps for the free plan, and whether the app starting the flow has an instant trigger. Then open the operation list of the same app on the other platform and compare it against the same three criteria.
Same platform

Other docs you might need on this stack.

Browse all integrations