How it works

From your inbox to your folder, without lifting a finger.

Findest isn't an app you check: it's a process that runs on its own every time a document reaches you. Here's exactly what happens to one attachment, from the moment it arrives to the line it leaves in your History.

The journey

One attachment, five moments.

Your mailbox, opened read-only

Gmail and other IMAP mailboxes are checked every 5 minutes; Outlook tells Findest the moment mail lands. Either way the mailbox is only read: nothing is marked as read, moved, sent or deleted.

In Findest
  1. New email seen
  2. 3 attachments listed
  3. Pre-filter skips 2
  4. 1 queued for reading

Read the way a person would

PDFs, scans, photos, Word and Excel files are opened and read in full. Type, sender and date come from what's printed on the page, so scan_0326.pdf is still recognised as an electricity invoice.

In Findest
  1. Open the file
  2. Read the whole content
  3. Pull type, sender and date

One request, all your rules

The document and every active rule go to the AI together, in a single request. Seeing them side by side, it picks the most specific fit. There's no order to manage, and the rule you made first has no advantage.

In Findest
  1. Your 4 active rules
  2. One request
  3. Answer: Office electricity

A name you can sort by

The file is renamed Type_Sender_Date in your account's language and uploaded to the folder the rule points to. If you've set up a webhook, it fires once the upload is done.

In Findest
  1. Rename to Type_Sender_Date
  2. Upload to Drive
  3. Webhook, if you set one

Nothing files itself silently

Each attachment gets a line in your History: the rule it went to, or the reason it wasn't filed, in plain words. Documents no rule fits wait there for you to decide.

In Findest
  1. Filed: rule and link
  2. Not filed: the reason
  3. All in your History
When things go wrong

If something doesn't go as planned, nothing is lost.

Most of the time you won't notice any of this. It's here because a process that runs at three in the morning has to know what to do without asking you.

If something fails midway

An expired token, a moment of cloud downtime: none of it matters. An automatic job checks every minute for documents stuck for more than three minutes and retries them, up to five times, without you having to do anything.

If no rule matches

Findest never improvises a destination. A document that doesn't fit any of your rules stays in your History marked “No rule”, with the reason, so you can decide where it goes. That's normal operation, so it doesn't trigger an email.

If one attachment is broken

A corrupt or unreadable file doesn't hold up the rest of the email. Each attachment is handled on its own, so the other documents in the same message are still read, renamed and filed.

If a connection stops working

When a mailbox or a cloud stops accepting Findest, for example after a password change or a revoked permission, you get one email the moment it goes from working to broken. Not one every five minutes.

The same message is never archived twice, even if a mailbox reports it more than once. What each step does when it fails, and which errors are worth retrying, is on Automatic retries

Your History, always

Every document, and why it went where it did.

Every document Findest touches shows up in your History with the label the AI assigned, which rule applied (or didn't, and why), and a direct link to where it landed in your cloud.

It's also the quickest way to tune a rule. If something went somewhere you didn't expect, the line tells you which rule took it, and a sharper sentence in that rule's description fixes the next one.

The statuses are the same words you'll see in the app: Archived, No rule and Error, plus Queued, Analyzing and Uploading while a document is still on its way.

One line, everything you need

Open any line to see what was read and where the file went.

Invoice_Endesa_2026-03-14.pdf
Read asInvoice
RuleOffice electricity
Saved toDrive · Invoices / Electricity
Archived

Building on top of Findest? The same records are available through the API, and a signed webhook fires for every archived document. API & webhooks

Questions about the process

What people usually ask about how it works.

See all questions

How long does it take to file a document?

Gmail and other IMAP mailboxes are checked every 5 minutes, and Outlook tells Findest as soon as mail arrives, so a document is normally filed within 5 minutes of reaching you. Once a message has been picked up, reading, classifying, renaming and uploading run in a single pass and take seconds. If your cloud is slow or down, the document is retried and still completes once it's back.

Can I see why a document ended up where it did?

Yes. Your History shows, for every document, the label the AI assigned, which rule applied, or why none did, and a direct link to the file in your cloud.

Can I reprocess a document if I change a rule?

Changing or creating a rule doesn't reprocess documents already filed; it only affects the ones that arrive from then on. Past documents stay where they are.

Does Findest mark my emails as read?

No. Mailboxes are opened read-only: Findest never marks a message as read, and never moves, sends or deletes anything in your inbox.