New Dropbox file shared in Slack
When a file lands in a Dropbox folder, the team gets a link to it in Slack.
Dropbox → Dropbox → SlackFiles arrive everywhere — email attachments, form uploads, invoices your own workflows make — and someone still has to put them in the right folder. Bizomate files them in Dropbox as they arrive, moves, renames and shares them, and starts a workflow when a file is added to a folder or changed. Every run leaves a record of which file went where.
| Label | Value |
|---|---|
| Plans | Every plan |
| Connect | An access token from your own Dropbox app — signing in with Dropbox comes later |
| Starts runs | Every 5 minutes (15 on Free) |
| Kind | Connected app · Files |
Choose the folder, Include subfolders and a Type; turn on Download it to bring the file into the run, up to 250 MB. Files already in the folder never start a run; up to 100 new files start runs in one check.
A file saved several times between checks starts one run, with its latest version.
If a file has that name: rename the new one, replace it with a new version, or fail the step.
By name, type and Changed since, in the folder and its subfolders. Left empty, Folder searches all of Dropbox.
A folder goes with everything in it. Dropbox keeps deleted files for 30, 180 or 365 days, by Dropbox plan, under Deleted files.
Who can open it, what they can do and when it stops working, each listing only what your Dropbox plan allows. End dates need Dropbox Professional, Essentials or a team plan.
Dropbox fetches the file straight into the folder. A large one still fetching after a minute comes back in progress; add a Wait, then Get file details.
A token generated in Dropbox's App Console stops working within four hours of being made, and Test says so when you connect. When it stops, steps fail with "expired_access_token" and the triggers show Not checking since; generate a new token and replace it on the connection. It suits building and trying workflows. Signing in with Dropbox, which keeps a connection working without a new token, comes later.
It sees what the token's app allows. An app made with Full Dropbox reaches everything the account can see, team folders included; an app made with App folder reaches only its own folder under Apps, and the pickers start there. To stop Bizomate reaching Dropbox, revoke the connection in Bizomate or delete the app in the App Console.
No. They check the folder every 5 minutes on paid plans and every 15 on Free, and each new or changed file starts one run. Files already in the folder when you publish never start a run, and a check that finds nothing costs nothing.
Yes. Create a share link gives back the link for the next step — an email, a Slack message or a row in a sheet — with who can open it, whether they can view or edit, and the date it stops working, where your Dropbox plan offers each.
When a file lands in a Dropbox folder, the team gets a link to it in Slack.
Dropbox → Dropbox → Slack