Workflows: Statements arrive. Spreadsheets appear.
A workflow watches where statements already land, a Dropbox or OneDrive folder or a forwarded email, parses each new file, and delivers the result where it is needed: a CSV, Excel, JSON, or Google Sheet in a folder, a signed webhook to your own system, or both. Nobody uploads, nobody downloads.
50 free page credits · No card · Cancel anytime
- Folders and email in
- Files and webhooks out
- One pipeline, several ends
Email imports
SettingsThe slowest step is carrying the file between tools.
Parsing a statement takes seconds. Getting it there takes longer: downloading the attachment, uploading it, waiting, exporting, and saving the result somewhere a colleague or a client can find it. Done for one statement that is a minute of clicks; done for every statement from every account it is a job, and it is the job that gets skipped when things are busy. A workflow turns the whole route into a standing instruction: this folder in, that folder out, and the same export settings every time.
How it works
Building one
- 01
Choose where statements arrive
Add one or more inputs: a folder in a connected Dropbox or OneDrive account, polled for new files, or forwarded email from approved senders. One workflow can read from several.
- 02
Choose what to read them as
Bank statements, or invoices and receipts. The same parser and checks run as for a manual upload, including the balance tie-out on statements.
However a file arrives, it is counted while it runs and lands in the same library. - 03
Choose where results go
Write a file, CSV, Excel, or JSON, into a Dropbox or OneDrive folder, or a native Google Sheet into Google Drive, and post to a webhook. Each output names its own destination; by default a file lands beside the one it came from.
- 04
Let it run
The Workflows page shows every pipeline, whether it is on, and the files each one has handled, counted from the jobs it created. Pause, run, or delete them in bulk.
A webhook endpoint, its subscribed events, and the secret deliveries are signed with.
What a workflow can do
Watched folders
Dropbox and OneDrive folders are read as well as written, so a folder can be where statements arrive and where results are filed.
Forwarded email
Statements forwarded from approved senders become workflow input, for the bank that has only ever offered an email attachment.
Native Google Sheets
Google Drive takes results as a real Google Sheet, not a CSV with a spreadsheet's name, alongside CSV, XLSX, and JSON.
Webhooks as an output
Post results to your own endpoint in the same workflow that writes the file, so a system and a person are both served.
Several outputs per pipeline
Inputs and outputs are lists, so one workflow covers what used to take several kept in step by hand.
Narrow permissions
Google Drive is connected under a scope limited to files Bankflow creates, which is why it is an output only. Dropbox asks for exactly the access the connector uses.
Which connector does what
The workflow editor offers only the connectors your account can use, and never one that does not work yet.
| Connector | Role in a workflow |
|---|---|
| Dropbox | Input and output: watch a folder, write CSV, XLSX, or JSON |
| OneDrive | Input and output: watch a folder, write CSV, XLSX, or JSON |
| Google Drive | Output only: Google Sheet, CSV, XLSX, or JSON |
| Forwarded email | Input: attachments from approved senders |
| Webhook | Output: results posted to your endpoint |
FAQ
Common questions
Why can Google Drive not be an input?
Bankflow connects to Google Drive under a narrow scope that only reaches files it created or files you hand it. It cannot list a folder, so it cannot watch one. Use Dropbox, OneDrive, or forwarded email as the input and Drive as the destination.
Are the exported files the same as a manual export?
Yes. Workflows use the same columns and export presets as the export dialog, so a file delivered by a workflow and one downloaded by hand match.
Can one workflow read from several places?
Yes. Inputs are a list: a folder in one account, a shared folder in another, and forwarded email can all feed the same workflow and share its parsing and output settings.
Can I connect more than one account per provider?
Yes. A personal account and a practice's account are separate connections, and each output names the one it writes to.
What happens to the statement after it is delivered?
By default it stays in Bankflow like any other. A workflow can instead remove it once every output has landed, for pipelines where Bankflow should only pass the data through.
Do workflows cost extra?
No. Every plan includes every feature. Pages read by a workflow use credits the same way as an upload.
Keep exploring
Categorization Rules
Include, exclude, and scope rules that run on every import.
Merchant Intelligence
Every narration resolved to a named merchant with its history.
Risk Review
An evidence-backed read of a set of statements, with no verdict.
Bank Statement Converter
What a converter has to get right, and what the file looks like when it does.
Bank Statement → Excel
Download a clean XLSX of every parsed transaction.
Make the folder the interface.
Connect Dropbox or OneDrive, point a workflow at a folder, and drop a statement in.