Skip to content
Dust logo

Dust integration

Secure messaging and collaboration

Actions
7
Triggers
0
Auth
Custom auth
License
MIT, open source
Updated
September 2026

About the Dust integration

Add the Dust piece to a flow, connect your account once, and the rest of the builder can read from it and write to it. Because the piece is open source you can run it on our cloud or self-host it, and combine Dust with 760+ other apps in the same flow.

Actions

Everything Activepieces can do in Dust

Drop any of these into a flow and fill in the fields. No code is required.

  • Create conversation

    Create a new conversation with a specific Dust assistant

    9 fields

  • Get existing conversation

    Get an existing conversation

    2 fields

  • Reply to conversation

    Send reply to existing conversation

    6 fields

  • Add fragment to conversation

    Create a new content fragment in a conversation. Content fragments are pieces of information that can be inserted in conversations and are passed as context to assistants to when they generate an answer.

    3 fields

  • Add or update document

    Insert a new document to a Data Source (or update an existing one)

    6 fields

  • Upload file

    Upload file to be used in conversation

    1 field

  • Custom API Call

    Make a custom API call to a specific endpoint

    10 fields

Use Dust in a flow

Connect Dust once and every trigger and action above is yours to drop into the builder, alongside 760+ other apps. Free to start, on our cloud or your own servers.

Dust, answered.

Yes. Activepieces is open source and free to start, and the Dust piece is included on every plan, from the free cloud tier to any self-hosted deployment.

Add the Dust piece to a flow, then authenticate with Custom auth. Once connected, its 0 triggers and 7 actions are available anywhere in the builder.

Connect Dust to any of 760+ other apps and AI steps, then automate the work in between without writing code.

Yes. Activepieces is fully self-hostable, so you can run the Dust piece on your own infrastructure with your connections and your data staying in your environment.

Yes. Every piece you connect can be exposed over one Activepieces MCP server, so Claude, Cursor, Windsurf or any MCP client can call Dust actions as tools.