DohFlow ships one direct connector today: SimpleFIN. If your bank isn’t covered there — a non-US institution, for example — an aggregator like LunchFlow can still get your data into DohFlow. Neither route below needs a DohFlow-built adapter.
Currency caveat: DohFlow doesn’t support connected accounts in a currency other than your base currency (Settings → Base currency) yet. For a non-US bank, that usually means an account in another currency, which DohFlow can’t import through a connection — Route 1 below explains what happens and how to avoid it.
Route 1: through LunchFlow’s own SimpleFIN Bridge
LunchFlow can expose the accounts it aggregates through the same SimpleFIN protocol DohFlow already speaks natively:
- In your LunchFlow account, create a SimpleFIN destination and choose which accounts to expose. Choose only accounts in your DohFlow base currency: DohFlow can’t import an account in any other currency, and one such account can make the whole connection’s refresh fail.
- LunchFlow gives you a setup token — the same kind of one-time token SimpleFIN Bridge itself issues.
- In DohFlow, connect a bank the normal way (Settings → Connections → SimpleFIN) and paste that token in.
From there it behaves exactly like a direct SimpleFIN connection: DohFlow doesn’t know or need to know the data came from LunchFlow. The token LunchFlow issues expires after a period it sets, so you’ll repeat this when it does — the same re-link flow SimpleFIN connections already use.
Route 2: file export
LunchFlow (and most aggregators) can export your transactions as CSV or OFX. DohFlow already imports both:
- Export from LunchFlow (or your aggregator of choice) as CSV or OFX.
- In DohFlow: Import → pick the file.
- Review staged rows in the Money Inbox before anything touches your ledger — nothing commits automatically.
This route is manual — no ongoing sync, you re-export and re-import when you want fresh data — but it works with any aggregator that produces a standard export, not just LunchFlow, and it’s the same importer path DohFlow already uses for a plain bank export.
Which one to use
Route 1 gives you the closer-to-automatic experience SimpleFIN users already have. Route 2 needs no aggregator account at all beyond whatever your bank already gives you, and works even if an aggregator’s bridge-style destination isn’t available on your plan.
Tell us what you’re using
DohFlow’s site carries no analytics, so we don’t know how many people take either
route above, or which aggregator. If you do, a reaction or a reply on
this GitHub Discussion tells us —
or open an issue labeled connector-request if you’d like to see a dedicated adapter
for a specific aggregator someday.