Resources · Make integration

Dust Make integrationAutomate Dust with Make.

Can Make talk to your Dust agents without any code? Yes. The Dust Make integration gives you 3 action modules: message an agent, upload a document to a datasource, or call the Dust API directly. This guide walks you from the connection to a working first scenario.

Try the Dust integration on MakeSee the 3 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Dust Make integration do for your team?

The Dust Make integration links your Dust workspace to Make, a no-code tool where you build a scenario: an automation made of modules, each one a single step such as sending a message or uploading a file. Dust brings 3 action modules and no trigger, so another app or a schedule starts the scenario.

Feed your agents fresh knowledge. When a new document lands in another tool, Upload a Document pushes it into a Dust datasource, so the content your agents draw on stays current without anyone copying files by hand.

Put an agent to work on incoming requests. A support team can pass each new ticket text to Talk to an Agent, so the agent chosen for support sees every request as soon as the scenario runs. Make carries the message; the agent itself lives in Dust.

Reach what the modules leave out. Make an API call sends any request to the Dust API with the same connection, which covers endpoints the two other modules do not touch.

Dust has no trigger in Make: nothing in Dust can start a scenario by itself. You begin with a module from another app, or with the scenario schedule, every 15 minutes by default. For the basics of the editor, the Make training starts from zero, and the n8n vs Make comparison helps if you are still choosing a tool.

Connect

How do you connect your Dust account to Make?

  1. 01

    Create an API key in Dust

    In the Dust web interface, open the Admin section, click API Keys, then Create an API Key. Copy the key shown on screen and keep it at hand, since Make will ask for it in the next step.

  2. 02

    Copy your workspace ID

    While you view your Dust workspace, look at the address bar: the workspace ID is the part that follows /w/. Copy it too. Make needs both the key and this ID to reach the right workspace.

  3. 03

    Create the connection in Make

    Add any Dust module to your scenario and click Create a connection. A connection is your Dust account linked to Make once, then reused by every Dust module. Name it in Connection name if you like, paste the key and the ID, and save.

First scenario

Your first scenario with Dust

GoalWhen a new document shows up in another app, Make uploads it to a Dust datasource, then sends a message about it to one of your agents.

  1. 01

    Create the scenario

    Go to the Scenarios page, create a new scenario and click the +. Pick the app where your documents appear first, since Dust cannot start the flow on its own.

  2. 02

    Add Upload a Document

    Click the + on the right of that first module, search for Dust and choose Upload a Document. Select your connection, or create it with the API key and workspace ID.

  3. 03

    Map the document

    Fill the module fields: once the connection exists, Make lists what it can read in your workspace. Map the content from the first module so each bundle, one item passing between modules, becomes one document.

  4. 04

    Ask an agent

    Add Talk to an Agent after the upload, pick the agent and write the message, mapping values from the earlier modules. Each module run on one bundle counts as one operation on your plan.

  5. 05

    Test with Run once

    Click Run once to execute the scenario a single time. Then read the bundles each module received and confirm the document and the message look right.

  6. 06

    Schedule and switch on

    Open the clock on the first module to set Scheduling. A new scenario runs every 15 minutes by default. Keep that or pick another interval, then turn the scenario on.

Modules

What each Dust module does

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

Dust1

Make an API call

Action

In Make“Send an arbitrary request to the Dust API.”

This module lets you send any request you need to the Dust API, reusing the connection you already set up, so nothing is out of reach when the two named modules fall short.

When to use it
you need a Dust endpoint that neither Talk to an Agent nor Upload a Document covers.
Watch out
you write the request yourself, so keep the Dust API reference open while you fill it in.
Dust2

Talk to an Agent

Action

In Make“Send a message to one of your Dust agents.”

You get one of your Dust agents working inside a scenario: Make hands it a message built from earlier modules, and the agent you chose receives it.

When to use it
a form reply, a ticket or an email arrives in another app and you want the right agent to read it without anyone pasting the text by hand.
Watch out
Make only delivers the message, so any change to how the agent works happens in Dust, not in the scenario.
Dust3

Upload a Document

Action

In Make“Upload a document to a Dust datasource.”

Your Dust datasource grows by itself: this module sends a document into it from whatever app produced the content, so new content reaches Dust without a manual upload.

When to use it
a new meeting note, product sheet or policy lands in another tool and belongs in the knowledge Dust holds.
Watch out
each bundle becomes one upload and one operation, so keep an eye on how many items the source sends.
Need help

Need help automating Dust with Make?

A person reads every message.

FAQ

Questions about the Dust Make integration

01Is the Dust Make integration free?
Yes, on the Make side. Dust is a standard app, so it works on the Free plan. That plan allows 2 active scenarios, runs no more often than every 15 minutes, stops each run after 5 minutes, accepts files up to 5 MB and includes 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) lower the interval to 1 minute, remove the cap on active scenarios and allow 40 minutes per run. Usage is counted in credits each month. Dust itself needs an active account of its own, and its pricing page explains that part.
02What do you need to connect Dust to Make?
Two things from Dust: an API key and your workspace ID. Create the key in the Admin section of Dust, under API Keys, with the Create an API Key button, and copy it straight away. The workspace ID sits in the browser address bar, right after /w/, when you open your workspace. In Make, add a Dust module, click Create a connection, give it a name if you want, and paste both values. Your Dust account must be active for the connection to work.
03Does the Dust Make integration have a real-time trigger?
No. Dust has no trigger in Make, so no Dust event can start a scenario on its own. There are two ways around it. You can open the scenario with a module from another app, such as the tool where your tickets or documents appear, and let Dust act after it. Or you can rely on the schedule of the scenario, which runs every 15 minutes by default and can go down to 1 minute on a paid plan. In both cases the Dust modules act as steps inside the flow.
04What if a Dust module you need is missing in Make?
Use Make an API call. It sends a request to any endpoint of the Dust API through the connection you already have, so you are not limited to Talk to an Agent and Upload a Document. You build the request yourself, which takes a bit more care than a ready-made module. Keep in mind that the Make documentation for Dust is flagged as generated from the official Dust docs and may contain mistakes, so check important details with Dust directly before you rely on them.
05Should you use Make or n8n for Dust?
It depends on the tool your team already knows. In Make, Dust brings 3 action modules plus the API call, and no trigger, which is enough to feed a datasource and message agents from other apps. The same app often exists as an n8n node too, so check what that node offers before you decide. Pick the tool where the rest of your automations already live: keeping every flow in one place makes maintenance easier than splitting it across two platforms.
Same platform

Other docs you might need on this stack.

Browse all integrations