Key Benefits of Transkriptor + Dust Integration
Your Agents Learn From Every Meeting: Transkriptor writes each finished transcription into a Dust folder, and Dust indexes it the moment it lands. From then on, any agent with access to that space can answer questions that span months of conversations — what a client objected to, which commitments were made on a call, where a decision was first raised.
Nothing to Build in Dust: You pick a folder and you're done. Transkriptor formats each transcription as a clean markdown document with the title, date, summary, and transcript already structured — no templates to design, no fields to configure, no automation to wire up.
Summary and Full Transcript Together: Each document carries the AI-generated summary at the top and the complete transcript below it. Your agents can give a one-line answer or pull an exact quote, because both live in the same document.
Meetings and Uploads in One Folder: Live meetings captured by the Transkriptor meeting bot and files you upload or record yourself both flow into the same place, so your agents see the complete picture.
No Duplicates, Ever: Each transcription maps to a single document. If a recording is processed again, Transkriptor updates the existing document instead of creating a second one.
Works With Both Dust Regions: Transkriptor supports Dust's US and EU workspaces. Your transcripts stay in the region your Dust workspace already lives in.
How to Connect Dust to Transkriptor
Three short steps — one in Dust, one copying a key, one in Transkriptor.
Step 1: Create a Folder in Dust
In Dust, open Spaces, choose the space you want to use, and go to Folders → Add folder. Give it a name like "Meeting Transcripts" and save.
Important: This step is required and must happen first. Dust folders can only be created inside Dust — Transkriptor can't create one for you. If you connect before creating a folder, the Target Folder dropdown will be empty. Come back here, create the folder, then reopen the Transkriptor settings.
Step 2: Get Your Dust API Key
In Dust, go to Admin → Developers → API Keys and click + Create API key. Give it a name such as Transkriptor and make sure the space containing your new folder is included in the key's scope.
Dust then shows you four values: Name, Domain, Workspace ID, and the API Key. Copy the last three now — the API key is only displayed once and disappears when you close the panel.
Step 3: Connect Dust in Transkriptor
Open the Integrations tab in your Transkriptor dashboard, find Dust, and click Connect.
In the “Connect Your Dust” modal, enter the two values below:
API Key: the key you created in the previous step (starts with
sk-).Workspace URL: while you’re still on the Developers page in Dust, copy the full URL from your browser’s address bar, as highlighted below. It should look like
https://app.dust.tt/w/your-workspace-id/developers.
Important: Copy the entire URL, not just the domain. Entering only
dust.ttorapp.dust.ttwon’t work, because the URL also contains your workspace ID.
2. Click Connect.
Transkriptor verifies the key against your Dust workspace immediately. If the values are correct, you're taken straight to the settings screen with your folders already loaded.
Step 4: Configure Your Dust Settings
Once connected, the Dust Settings modal will open. Configure the following:
Target Folder — Choose the Dust folder where Transkriptor should write your documents. The dropdown lists every folder your API key can reach, shown as Space / Folder. If the dropdown is empty, either no folder exists in your workspace yet, or the API key is scoped to spaces that don't contain your folder — create the folder or a new key with broader scope, then close and reopen the settings.
Include Summary (on by default) — Writes the AI-generated summary into a Summary section at the top of the document, converted to clean readable text.
Include Transcript (on by default) — Adds the complete transcription beneath the summary, with timestamps and speaker labels.
Include Audio Link (on by default) — Adds a link to the original audio or video file at the end of the document.
Click Save to apply your settings.
Note: At least one of these needs to be on. If you turn all three off, Transkriptor will skip the transcription rather than create an empty document.
Step 5: Done — Documents Are Created Automatically
Your integration is now live. Every meeting you transcribe from now on will appear as a new document in your Dust folder, ready for your agents.
What Each Document Contains
Every transcription becomes one markdown document, structured like this:
| Part | Contents |
|---|---|
| Title | The meeting title, or the uploaded file's name with the extension removed |
| Date | When the document was created, in UTC |
| Type | Whether the record came from a live meeting or an uploaded file |
| Summary | The AI-generated summary, converted to clean plain text |
| Transcript | The full transcription with timestamps and speaker labels |
| Recording | A link to the original audio or video file |
Each document also carries tags your agents and Dust's search can filter on: transkriptor on every document, type:meeting or type:upload depending on the source, and order_id: followed by the transcription's unique ID. The document's Associated URL points to the exported transcript so you can jump from Dust to the full text in one click.
How to Disconnect from the Integration
Click the three-dot icon next to the Dust integration in Transkriptor to change your settings or disconnect.
Disconnecting stops Transkriptor from writing any new documents. Everything already in your Dust folder stays exactly where it is, and your agents keep using it.
One extra step worth taking: Dust doesn't offer a way for external apps to revoke their own keys, so the API key you created stays valid until you delete it. To fully close the loop, go to Admin → Developers → API Keys in Dust and remove the key you made for Transkriptor.
Troubleshooting
| Issue | What to Do |
|---|---|
| Target Folder dropdown is empty | Either no folder exists in your Dust workspace yet, or the API key is scoped to a space that doesn't contain your folder. Create the folder in Dust first, or create a new key with the correct scope, then close and reopen the settings. |
| Connection fails after pasting credentials | Make sure you copied all three values — API Key, Workspace ID, and Domain — correctly from the Dust API key panel before it closed. Generate a new key if needed. |
| API key panel closed before copying | Go back to Dust → Admin → Developers → API Keys and create a new key. The previous key remains active but its value can no longer be retrieved. |
| Notes aren't appearing in Dust | Confirm the Target Folder is correctly set and that at least one content toggle (Summary, Transcript, or Audio Link) is enabled. |
| EU workspace not connecting | Make sure the Domain field contains https://eu.dust.tt, not https://dust.tt. |
Still stuck? Contact support.
