Connect, then browse your real tree.
One click authorizes Findest on your actual Dropbox: your personal folders or, on Dropbox Business, any team folder you belong to. It's not an app-only folder.
Connect your mailbox and every matching attachment is read, named and saved into the exact Dropbox folder your rule points to, personal or shared with your team. No downloading, renaming or dragging.
Findest never changes a folder's sharing: the file inherits it
files.content.*Read and write, which is what lets you browse your real folders.One click authorizes Findest on your actual Dropbox: your personal folders or, on Dropbox Business, any team folder you belong to. It's not an app-only folder.
Point a rule at a folder once, for example legal/contracts/signed. Change your mind later and repoint it in seconds; nothing already filed moves.
A matching attachment is read, renamed Type_Sender_Date and uploaded into that folder, usually within five minutes of arriving. The History links to the result.
Findest doesn't give you an app-only folder to live in. It shows the Dropbox you already use, so a rule can point wherever you'd have dropped the file yourself.
Browse your folders, pick one per rule, and a contract goes to legal/contracts/signed while invoices go to invoices_2026. Change a rule's folder later and nothing already filed moves.
If your account belongs to a team space or a shared folder, it appears in the same browser as your personal Dropbox and any rule can point to it. Handy for contracts or supplier invoices the whole team needs.
Findest never changes a folder's permissions, so where a rule files decides who can see the result, exactly as if you had dropped the file there yourself.
/Personal/invoices_2026/Team/legal/contractsThe files.content.* grant covers Dropbox the way its own picker would. We ask for it because browsing real folders needs it, not because Findest wants to look around.
| What Findest does | Why | Result |
|---|---|---|
| Lists folders | So you can pick the destination of a rule in a real folder browser. | Yes |
| Uploads a file | Only into the folder the matching rule points to, already named Type_Sender_Date. | Yes |
| Reads your existing files | Existing contents aren't read or indexed. | No |
| Changes sharing | A folder's permissions are never touched. | No |
The Dropbox token never reaches your browser: it stays on the server. The connection is tied to the browser that started it, and you get an email when a new account is connected.
Pressing Disconnect in Findest also revokes the token at Dropbox, so Findest stops showing in your connected apps. It isn't just our copy being deleted.
Everything already filed stays exactly where it is in your Dropbox. Findest simply stops uploading new files until you reconnect.
What Findest itself keeps, its database and files, is hosted in London, United Kingdom. Your Dropbox files remain in Dropbox.
Yes. If your account belongs to a Dropbox Business team space or shared folder, it shows up in the same folder browser as your personal Dropbox, and any rule can point to it.
The grant is files.content.*, read and write, the way Dropbox's own picker works. Findest uses it to list folders so you can choose, and only uploads into the folder a rule points to. Existing contents aren't read or indexed. See Security for why we ask for it.
Everyone who already has access to that folder. Findest never changes a folder's sharing, so a private folder stays private and a team folder shows the file to the whole team.
Existing files stay exactly where they are. Findest revokes its token at Dropbox, so it disappears from your connected apps, and stops uploading until you reconnect.
Findest's database and files are hosted in London, United Kingdom. The documents it files live in your own Dropbox.