Firefly III imports through its separate data importer (
firefly-iii/data-importer), not the main Firefly application. If you don’t already run the importer, add it to your stack first.Prerequisites
- A running Firefly III instance
- The Firefly III data importer with SimpleFIN support
- A Redbark account with connected bank accounts
- A Redbark Developer or Professional plan (trials included)
Setup
1
Generate a SimpleFIN setup token
Log into Redbark, go to Settings > SimpleFIN, and generate a SimpleFIN setup token. Name it after your Firefly instance.The token is shown once, can be claimed once, and expires in 7 days if unused.
2
Start a SimpleFIN import
In the data importer, choose the SimpleFIN import flow and paste the Redbark setup token when it asks for one. The importer claims the token and receives its own private, read-only credentials.
3
Set a start date
Set a start date before the first import.
4
Map accounts and import
Map each Redbark account to a Firefly III asset account, then run the import. Later runs pick up new transactions from where the last one finished.
How it behaves
- Live bank balances and transactions are fetched when the importer asks, without a permanent server-side ledger. Banking reads can use a bounded cache. Documents accounts instead read imported transactions retained by Redbark.
- Transactions carry stable source IDs, so repeat imports of the same ID reconcile instead of duplicating.
- Banking and Documents accounts are served over SimpleFIN. Brokerage accounts connected to Redbark are not exposed.
- Rate limiting is sized for the importer’s chunked backfill: 300 requests per minute per connected app. A window ending at or before the ~7-year banking history floor skips banking transaction reads, not balance reads. Documents transactions keep the requested date range, including older imports.
- Revoking the token from Settings > SimpleFIN cuts the importer’s access immediately without touching your bank consent or any other connected app.

