Dust icon

Dust

Interact with Dust API

Overview

This node integrates with the Dust API to enable conversational interactions with AI agents and document uploads within a workspace. The "Talk to an Agent" operation allows users to send messages to a configured AI assistant agent and receive responses, facilitating automated or semi-automated conversations. This is useful for scenarios such as customer support automation, virtual assistants, or any workflow requiring natural language interaction with an AI.

For example, you can use this node to:

  • Send a user query to a specific AI agent and get its reply.
  • Include contextual information like username, email, and timezone to personalize the conversation.
  • Retrieve a URL to the full conversation for reference or follow-up.

Properties

Name Meaning
Message The text message content to send to the AI agent.
Agent Name or ID Select or specify the target AI agent configuration by name or ID to which the message will be sent.
Additional Fields Optional extra context fields to include with the message:
- Username: The user's name sending the message.
- Email: The user's email address.
- Timezone: The user's timezone (defaults to "Europe/Paris" if not provided).

Output

The node outputs a JSON array where each item corresponds to one input item processed. Each output item contains:

  • agentMessage: The concatenated response(s) from the AI agent. If no message is returned, it shows "No message returned".
  • conversationUrl: A URL linking to the full conversation in the Dust workspace UI.
  • userMessage: The original user message sent to the agent.

This structure allows downstream nodes to access both the AI's reply and metadata about the conversation.

Dependencies

  • Requires an API key credential for authenticating with the Dust API.
  • The node dynamically selects the API base URL based on the region specified in credentials (EU or default).
  • The node uses HTTP requests to communicate with the Dust API endpoints.

Troubleshooting

  • Common issues:

    • Invalid or missing API key will cause authentication errors.
    • Incorrect agent ID or workspace ID may result in "not found" or authorization errors.
    • Network connectivity problems can cause request failures.
  • Error messages:

    • Authentication errors typically indicate invalid or expired API keys; verify and update credentials.
    • 404 errors suggest incorrect agent or workspace identifiers; confirm these values.
    • Rate limiting or server errors should be retried after some delay.

Links and References

Discussion