Dropbox
Paste an API keyFile generated documents into any Dropbox folder.
What you can do
- Save to Dropbox — uploads the flow's documents into a folder path you choose
No false success: every send/create in Dropbox is verified — ASHDOCS reads the item back from Dropbox's API before the step turns green. If it can't be found, the run fails honestly instead of pretending.
Get your Dropbox credentials
- 1Go to dropbox.com/developers/apps and click Create app.
- 2Choose Scoped access, then Full Dropbox (or App folder for a sandboxed folder).
- 3On the Permissions tab tick files.content.write and files.content.read, then Submit.
- 4Back on the Settings tab, click Generate under “Generated access token” and copy it.
Add the connection in ASHDOCS
- 1Open the Connections page in the flows console.
- 2Click “Connect with a key” and pick Dropbox.
- 3Paste: Access token. ASHDOCS validates the credentials against Dropbox before saving — a bad key is rejected with a plain-English reason, never stored.
Use it in a flow
In the flow builder, add the Dropbox step, pick your connection, and fill the fields — values from earlier steps drop in as {{s1.field}} placeholders. Then hit Test this step in the step's panel to run it on its own before switching the flow on.
Troubleshooting
401 after a few hours
Default Dropbox tokens are short-lived. In the app console set “Access token expiration” to No expiration, generate a new token and re-add the connection.
“refused the upload (409)”
The folder path doesn't exist — create it in Dropbox first or leave the folder blank for the root.
FAQ
Is the upload verified?
Yes — each file's metadata is read back from Dropbox before the step turns green.
Which folder do files go to?
The Folder field in the step (e.g. invoices/2026). Blank = your Dropbox root (or the app folder).