firefly-plaid-connector VS quickstart

Interesting, I wasn't aware of this fork. For what it's worth, the original repo is here: https://gitlab.com/GeorgeHahn/firefly-plaid-connector and images are published at registry.gitlab.com/georgehahn/firefly-plaid-connector:latest.

There is already a Plaid Connector but would benefit from independent reviewers and contributors.

It connects via plaid, which isn't that great if you're interested in data privacy. If you really want to use it though, you can use https://gitlab.com/GeorgeHahn/firefly-plaid-connector. As for "your own dashboard" i'm not sure what this means in the context of "better than firefly"...

I was able to get the Plaid API working with n8n an hour or go. I am going to build off of it to create exactly what I need. I used https://github.com/plaid/quickstart to spin up a sample app, login, link my account and get my access token. Then I can take that access token and include it in a HTTP post request to the Plaid API's get transactions endpoint. I can select transactions from a certain date range (today) as well as account balances and run it on a cron job once per day. Each transaction has a transactionId which will help me avoid duplicates. I can then push this info into Google Sheets, Notion, a database or wherever. If I use Google Sheets I can add graphs or link it to Google Data Studio and build a dashboard showing exactly what I need. Yes, it is more steps than using some existing application but the flexibility to create exactly what I need is worth it for me. I am not far enough yet to say if there will be any hiccups or not, but so far it is looking like clear skies ahead.

Also, looks like this might help: https://github.com/plaid/quickstart

git clone https://github.com/plaid/quickstart.git cd quickstart/python # Copy the .env.example file to .env, then fill # out PLAID_CLIENT_ID and PLAID_SECRET in .env cp .env.example .env # Install dependencies pip install -r requirements.txt # Start the backend app ./start.sh