App Logo
dust.tt

Send a Dust message

Send a follow-up message into an existing Dust conversation and wait for the agent's reply (up to 3 minutes). Takes the conversationId from list_conversations, search_conversations or ask. Returns the reply text, the ids of both the sent message and the reply, the agent that answered, and whether generation completed. The agent defaults to "dust"; pass agent to address another one (list_agents). Like ask, this polls rather than streaming, and completed=false means the wait ran out while the agent was still working — the partial reply is returned and the rest can be read later with get_conversation_messages. Only the new reply is returned, not the whole thread: use get_conversation_messages for that.

Input

message required

The message to send.

conversationId required

Conversation sId to post into, e.g. "P35s1dnqSr".

agent optional

Agent sId to address, e.g. "dust". Defaults to "dust".

Default: "dust"
workspaceId optional

Workspace sId. Omit to use the first workspace on the account.

timeoutSeconds optional

How long to wait for the reply (default 180).

Default: 180

Output

url required
agent required
reply required

The agent's reply as markdown. Null when the agent produced no text (tool-only or errored turn) — a real outcome, not a parse failure.

completed required

False means the wait expired while the agent was still working; the reply is partial.

sentMessageId required

sId Dust gave the message that was sent.

waitedSeconds required
conversationId required
replyMessageId required

sId of the agent's reply.

FAQ

Send a follow-up message into an existing Dust conversation and wait for the agent's reply (up to 3 minutes). Takes the conversationId from list_conversations, search_conversations or ask. Returns the reply text, the ids of both the sent message and the reply, the agent that answered, and whether generation completed. The agent defaults to "dust"; pass agent to address another one (list_agents). Like ask, this polls rather than streaming, and completed=false means the wait ran out while the agent was still working — the partial reply is returned and the rest can be read later with get_conversation_messages. Only the new reply is returned, not the whole thread: use get_conversation_messages for that.
Required: conversationId, message. Optional: agent, workspaceId, timeoutSeconds.
It returns url, agent, reply, completed, sentMessageId, waitedSeconds, conversationId, replyMessageId.
Yes. It acts as you on dust.tt: on your own Chrome it reuses your session, and on a Reduck-hosted browser it loads the dust.tt cookies saved by the Reduck extension.
It makes changes on dust.tt, like sending, posting or booking something.
Ask an AI agent connected to Reduck to run reduck/dust.tt/send_message, or run it from a terminal with the Reduck CLI: npx @reduck-ai/cli@latest run --script reduck/dust.tt/send_message
It is part of Reduck's official curated catalogue.

Start building not clicking