RecordX + Dropbox
What it does today
The watch-folder sync isn't shipped. Today the flow is manual: download the audio or video from Dropbox, upload it to RecordX, then export the transcript and drop it back into the same Dropbox folder. The planned integration will watch a folder you nominate, pick up new audio / video files automatically, and write transcript, summary and action-item files back as siblings.
Setup today
- Create your RecordX account at recordx.io/register.html.
- Right-click the audio / video in Dropbox and choose Download.
- Drop the file into the RecordX web-app uploader.
- Wait for transcript, summary and action items (typically under a minute per 10 minutes of media).
- Export the transcript (TXT, VTT, SRT or DOCX) and upload it back to the same Dropbox folder.
Setup (once the watch-folder ships)
- Open settings in the RecordX web app and click Connect Dropbox.
- Sign in and pick the folders RecordX may watch.
- Set output preferences: same folder as source (default) or a dedicated /Transcripts subfolder.
- Choose which formats to write: TXT, VTT, SRT, DOCX, JSON.
- Drop new audio / video into the folder and check the sibling files appear.
Data sync (planned)
| Data | Direction | Notes |
|---|---|---|
| Audio / video files | Dropbox → RecordX | New files in watched folders trigger transcription. |
| Transcript | RecordX → Dropbox | Sibling file next to the source: recording.transcript.txt. |
| Summary | RecordX → Dropbox | Sibling Markdown file: recording.summary.md. |
| Action items | RecordX → Dropbox | Included in the summary file. |
| Speaker labels | RecordX → Dropbox | Embedded in the transcript output when detected. |
| Source file | Not modified | Original media file left untouched. |
| Dropbox comments | Not synced | Kept in Dropbox; RecordX doesn't read them. |
Permissions and scopes
Connect uses Dropbox's OAuth 2.0 scoped access. The planned scope set is files.content.read on the
folders you nominate (fetch new media files) and files.content.write on those same folders (write
transcript / summary siblings). RecordX doesn't request team-admin scopes or ask for account-wide access.
Pricing and limits
RecordX doesn't charge for Dropbox transcription - files consume your normal monthly minutes. Dropbox API calls are free on every plan; storage is your own Dropbox quota. Dropbox has per-app rate limits (a few hundred writes per second) that typical practice archives won't approach. Files over 4 GB use the upload-session API automatically.
Common gotchas
- Deleted-file events count toward the app's event budget; watched folders should not receive rapid deletes.
- Very deep folder hierarchies may be slow to scan on first connect - narrow the watch to specific paths.
- Dropbox Paper is a separate product and is not covered.
- If you rename the source, the sibling transcript keeps the original filename - re-run to refresh.
Alternatives while you wait
- Zapier or Make: Dropbox "New file" trigger → RecordX "Transcribe file".
- Dropbox's own transcription in Dropbox Business - fine if you don't need Hebrew or 50+ languages.
- Manual upload from Dropbox to RecordX, manual download back.
- Google Drive - same roadmap shape.
FAQ
- Is the Dropbox integration live?
- Watch-folder automation is on the roadmap. Today you download files from Dropbox and upload them to RecordX yourself; then export the transcript and drop it back into the same Dropbox folder.
- Which Dropbox plan is needed?
- Any Dropbox plan including Basic works with the API. Team plans get the added benefit of team-space folders that RecordX can watch, but personal folders work too.
- Which file formats?
- RecordX handles MP3, WAV, M4A, MP4, MOV, WebM up to the per-file limit on your plan. Non-audio-video files in the same folder are ignored by the planned watch.
- Where do the outputs land?
- The planned behaviour is siblings in the same folder: recording.mp3 gets recording.transcript.txt and recording.summary.md next to it, so your case / client / project folder stays one folder.
- Is Dropbox Paper supported?
- Not planned - Dropbox Paper's API is separate and the sync is targeted at file storage rather than doc creation.
Setup checklist
- RecordX account created.
- Dropbox folders identified for the watch (client folders, case folders, interview archives).
- Naming convention decided (source.transcript.txt vs /Transcripts/source.txt).
- Retention rules aligned - RecordX transcripts should follow the same as the source media.
Related integrations
- Google Drive - same shape.
- Notion - if the summary belongs in a doc, not a file.
- Slack - post the transcript link to the team.
- Zapier - build the pipe today.
- See all integrations.
Sign up free, start transcribing. No credit card required.
Start for free