Automatically save transactions from all major Israeli banks and credit card companies, using GitHub Actions (or a self-hosted Docker image).
Powered by israeli-bank-scrapers.
Having all your data in one place lets you view all of your expenses in a beautiful dashboard like Looker Studio, Azure Data Explorer dashboards, Microsoft Power BI and YNAB.
This app requires some technical skills. If you prefer a GUI app you can use Caspion instead.
Warning
The current implementation assumes that you run the code on secure and trusted computers. Storing all your financial data and passwords in one place is risky — especially with more than read-only access.
By using moneyman, you acknowledge that you are taking full responsibility for the code quality and will use it only after you review the code and validate that it's secure.
Please use a proper secret management solution to store and pass credentials.
Moneyman can be configured to periodically run automatically, using the scrape GitHub workflow.
By default, this workflow will run twice daily at 10:05 and 22:05 UTC (12:05 and 00:05 or 13:05 and 01:05 in Israel time, depending on DST).
Since logs are public for public repos, most logs are off by default and the progress and error messages will be sent via Telegram.
- Fork the moneyman repo to your account
- Add the
MONEYMAN_CONFIGto the actions secrets of the forked repo- Use
config.example.jsoncas a starting point and add configurations for your selected storage - For better logging, add the Telegram configuration so moneyman can send private logs and errors
- Use
- Build and upload the Docker image using the "Run workflow" button in workflows/build.yml
- Wait for the scrape workflow to be triggered by GitHub
From code
- Clone this repo
- Run
npm install - Run
npm run build - Provide your configuration via
MONEYMAN_CONFIG(inline JSON) or pointMONEYMAN_CONFIG_PATHto a JSON/JSONC file - Run
npm start
From Docker
- Provide configuration via
MONEYMAN_CONFIG(inline JSON) or mount a config file (recommended below) docker run --rm -e MONEYMAN_CONFIG="$(cat config.json)" ghcr.io/daniel-hauser/moneyman:latest
Instead of passing the configuration as an environment variable, you can mount a configuration file:
docker run --rm \
-v /path/to/config:/config \
-e MONEYMAN_CONFIG_PATH=/config/config.json \
ghcr.io/daniel-hauser/moneyman:latestOr use Docker secrets:
docker run --rm \
--secret config.json \
-e MONEYMAN_CONFIG_PATH=/run/secrets/config.json \
ghcr.io/daniel-hauser/moneyman:latestBy default, the Docker image is configured with MONEYMAN_UNSAFE_STDOUT=false to prevent sensitive data from appearing in Docker logs. When enabled, the logs are redirected to /tmp/moneyman.log and sent to the Telegram chat automatically (if configured).
Logs sent to logToPublicLog bypass the redirection and will appear in the Docker logs.
Moneyman uses the debug package for debug messages under the moneyman: namespace.
To enable debug output, set the DEBUG environment variable to moneyman:*.
Moneyman uses a JSON configuration for all settings. You can provide configuration in two ways:
MONEYMAN_CONFIGenvironment variable: The JSON configuration as a stringMONEYMAN_CONFIG_PATHenvironment variable: Path to a JSON or JSONC configuration file
The configuration file approach is recommended for Docker/Kubernetes environments and supports JSON with Comments (JSONC) for better readability.
Tip
See config.example.jsonc for a complete example configuration file with comments.
A JSON array of accounts following this schema with an additional companyId field set to a companyType value.
accounts: Array<{
companyId: string;
password: string;
/**
* And any other fields required by the specific scraper
*/
}>;| env variable name | default | description |
|---|---|---|
TZ |
'Asia/Jerusalem' |
A timezone for the process - used for the formatting of the timestamp |
MONEYMAN_CONFIG |
The JSON configuration for the process | |
MONEYMAN_CONFIG_PATH |
Path to a JSON/JSONC configuration file (used if MONEYMAN_CONFIG is not set) |
|
SEND_NEW_CONFIG_TO_TG |
"false" |
Set to "true" to send the current configuration as config.txt via Telegram for debugging purposes |
MONEYMAN_UNSAFE_STDOUT |
"false" |
Set to "true" to allow sensitive data to be printed to stdout instead of a log file |
MONEYMAN_LOG_FILE_PATH |
"/tmp/moneyman.log" |
The file path where logs are stored when MONEYMAN_UNSAFE_STDOUT is set to "false" |
options: {
scraping: {
/**
* A comma separated list of providers to take from `accounts`. if empty, all accounts will be used
* @default all accounts
*/
accountsToScrape?: string[];
/**
* The amount of days back to scrape
* @default 10
*/
daysBack?: number;
/**
* The amount of months that will be scrapped in the future, starting from the day calculated using `daysBack`
* @default 1
*/
futureMonths?: number;
/**
* The hash type to use for the transaction hash. Can be `moneyman` or empty. The default will be changed to `moneyman` in the upcoming versions
* @default ""
*/
transactionHashType?: "" | "moneyman";
/**
* If set to `'true'`, enables the `additionalTransactionInformation` option in the underlying scraper, which may provide more detailed transaction data for some providers.
* @default false
*/
additionalTransactionInfo?: boolean;
/**
* A comma separated list of deprecations to hide
* @default []
*/
hiddenDeprecations?: string[];
/**
* An ExecutablePath for the scraper. if undefined defaults to system.
*/
puppeteerExecutablePath?: string;
/**
* The maximum number of parallel scrapers to run
* @default 1
*/
maxParallelScrapers?: number;
/**
* Enable tracking of all domains accessed during scraping
* @default false
*/
domainTracking?: boolean;
},
logging: {
/**
* The URL to get IP information from
* @default "https://ipinfo.io/json"
*/
getIpInfoUrl?: string;
};
};Moneyman supports domain tracking and firewall rules to control which domains each scraper can access. See Domain Security for setup instructions.
We use Telegram to send you the update status, including support for OTP 2FA with OneZero accounts. See Telegram Notifications for setup instructions.
| Destination | Description |
|---|---|
| Telegram | Send transactions as a JSON file to your Telegram chat |
| Google Sheets | Export transactions to a Google Sheets spreadsheet |
| Azure Data Explorer | Export transactions to an Azure Data Explorer cluster |
| YNAB | Export transactions to YNAB (YouNeedABudget) |
| Buxfer | Export transactions to Buxfer |
| Actual Budget | Export transactions to Actual Budget |
| PostgreSQL | Persist transactions in a PostgreSQL database |
| Web Post | Export transactions as a POST request to a web address |
| JSON files | Export transactions to local JSON files |
| Excel on OneDrive | Export transactions to Excel on OneDrive (WIP) |