Skip to content
Documentation
Contact
← Back to documentation
Technical Reference

Dust

Secure messaging and collaboration

CategoryOther
Authenticationcustom
Version0.3.0
Published scopes0 published scopes
Last updatedSeptember 19, 2026

Overview

Connect Dust with Flows360

Secure messaging and collaboration

Use the Dust connector to include its declared actions and events in Flows360 workflows without duplicating the integration logic inside each consuming system. This pinned connector version currently exposes 7 actions and no declared triggers.

Available actions

  • Create conversation
  • Get existing conversation
  • Reply to conversation
  • Add fragment to conversation
  • Add or update document
  • Upload file
  • Custom API Call

Available triggers

  • No triggers are declared in this pinned package.

The capability list above is generated from the exact reviewed connector package so the public description stays aligned with the version Flows360 operates.

Technical guide

Technical reference

Package identity

  • Connector: Dust
  • Package: @activepieces/piece-dust@0.3.0
  • Exact artifact digest: sha256:ebabb9d80608741224a15e4f7e12b0f1d6a9e157b79444f7d145fdc8e96b14a8
  • Runtime: Activepieces-compatible deterministic worker
  • Source: the exact reviewed Activepieces source

Authentication

CUSTOM AUTH. Connection values are tenant-specific and remain in the consuming Studio instance; CDK stores definitions and field metadata, not customer credential values.

Action contracts

  • Create conversation (createConversation), Create a new conversation with a specific Dust assistant Classification: read.
  • Get existing conversation (getConversation), Get an existing conversation Classification: read.
  • Reply to conversation (replyToConversation), Send reply to existing conversation Classification: read.
  • Add fragment to conversation (addFragmentToConversation), 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. Classification: read.
  • Add or update document (addDocument), Insert a new document to a Data Source (or update an existing one) Classification: read.
  • Upload file (uploadFile), Upload file to be used in conversation Classification: read.
  • Custom API Call (custom_api_call), Make a custom API call to a specific endpoint Classification: read.

Trigger contracts

  • No trigger delivery contracts are declared.

Verification

Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.

Capability summary

Authenticationcustom
Supported objects7
Supported actions7
TriggersNone published

Authentication

Authentication method: custom

Authentication profiles

connection · custom
  • API key Required · protected credential
  • Dust workspace ID Required
  • Region Optional

Supported objects

ObjectReadWriteNotes
Create conversation Yes No Create a new conversation with a specific Dust assistant
Get existing conversation Yes No Get an existing conversation
Reply to conversation Yes No Send reply to existing conversation
Add fragment to conversation Yes No 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.
Add or update document Yes No Insert a new document to a Data Source (or update an existing one)
Upload file Yes No Upload file to be used in conversation
Custom API Call Yes No Make a custom API call to a specific endpoint

Supported actions

Create conversation · Read

Create a new conversation with a specific Dust assistant

create_conversation · Risk: low · Retry: safe

Inputs

  • assistant · string · Required
  • username · string · Required
  • timezone · string · Required
  • title · string · Optional
  • query · string · Optional
  • fragment · object · Optional
  • fileId · string · Optional, ID of the file to be added to the conversation (takes precedence over Fragment)
  • fragmentName · string · Optional
  • timeout · number · Required
Get existing conversation · Read

Get an existing conversation

get_conversation · Risk: low · Retry: safe

Inputs

  • conversationSid · string · Required
  • timeout · number · Required
Reply to conversation · Read

Send reply to existing conversation

reply_to_conversation · Risk: low · Retry: safe

Inputs

  • conversationId · string · Required
  • assistant · string · Required
  • query · string · Required
  • username · string · Required
  • timezone · string · Required
  • timeout · number · Required
Add fragment to conversation · Read

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.

add_fragment_to_conversation · Risk: low · Retry: safe

Inputs

  • conversationId · string · Required
  • fragment · object · Required
  • fragmentName · string · Optional
Add or update document · Read

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

add_document · Risk: low · Retry: safe

Inputs

  • datasource · string · Required
  • documentId · string · Required, The ID of the document you want to insert or replace
  • content · string · Required, The text content of the document
  • sourceUrl · string · Optional, The source URL of the document (when cited)
  • title · string · Optional, User-friendly title of the document
  • tags · array · Optional
Upload file · Read

Upload file to be used in conversation

upload_file · Risk: low · Retry: safe

Inputs

  • file · object · Required
Custom API Call · Read

Make a custom API call to a specific endpoint

custom_api_call · Risk: low · Retry: safe

Inputs

  • url · object · Required
  • method · string · Required
  • headers · object · Optional, Authorization headers are injected automatically from your connection.
  • queryParams · object · Optional, Appended to the URL as ?key=value.
  • body_type · string · Optional
  • body · object · Optional
  • response_is_binary · boolean · Optional, Enable for files like PDFs, images, etc.
  • failsafe · boolean · Optional, On a failed request, output the error instead of failing the step.
  • timeout · number · Optional, Seconds to wait for a response. Empty: up to the flow limit (10 min).
  • followRedirects · boolean · Optional, Follow 3xx redirects instead of returning them as the response.

Setup

Setup

  1. Add the Dust connector to the workflow in the target Flows360 Studio instance.
  2. Create or select the tenant-specific connection required by the connector. Connection secrets remain in the Studio connection boundary and are not copied into CDK documentation.
  3. Provide the connection fields declared by the pinned package:
  • API key (apiKey), required; stored as a sensitive connection value.
  • Dust workspace ID (workspaceId), required.
  • Region (region), optional.
  1. Select the required action or trigger and complete its declared input fields. Required and optional inputs are defined by the exact package schema.
  2. Test the workflow in the appropriate environment before enabling production scheduling or event delivery.

Limitations

Limitations and operational notes

  • This content describes @activepieces/piece-dust@0.3.0; provider behaviour can change independently and should be revalidated when the provider or connector version changes.
  • Only the 7 actions and 0 triggers declared by this pinned package are represented here.
  • Tenant credentials and connection values are not stored in the public connector record.
  • Provider-side permissions, account entitlements, quotas and rate limits remain subject to the connected provider account and are not inferred when the package does not declare them.
  • Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.

Troubleshooting

Why canu2019t the connector authenticate?

Check the tenant connection in Studio and confirm every required Dust connection field is present. Re-authorise OAuth-based connections if the provider token or consent has expired. Do not place credential values in CDK content or logs.

Why is an action or trigger unavailable?

Confirm that the workflow is using @activepieces/piece-dust@0.3.0 and compare the requested capability with the declared action and trigger list for this version. A capability that is not declared by the pinned package should not be presented as supported.

What should I check after a provider-side change?

Revalidate authentication, required fields, action/trigger behaviour and provider documentation before publishing refreshed connector content or moving a new package version into production.

github.com