firefly-transaction

Automate transaction entry in Firefly III by retrieving an API token from Nomad variables and posting validated entries via curl. You provide the transaction amount, date, category, source, destination, and description to register withdrawals, deposits, or transfers.

Yes, you need Nomad CLI and curl to record Firefly III transactions. The workflow requires the Nomad CLI to retrieve the API token from variables and curl to post the validated transaction payload to your Firefly III instance.

You can log deposits and transfers to Firefly III in addition to withdrawals. The skill validates and posts all three transaction types by capturing the amount, date, category, source account, destination account, and description.

Interactive confirmation prompts you to verify the amount, date, category, source, destination, and description before posting the Firefly III transaction. This validation step ensures the curl API request contains accurate ledger data.

The best way to integrate personal finance automation with Nomad and Firefly III is using a skill that reads your API token from Nomad variables and posts validated transaction entries via curl, automating withdrawals, deposits, and transfers.

A key limitation is that the Firefly III instance must be accessible with a valid API token stored in Nomad variables. If the Nomad CLI cannot retrieve the token or curl cannot reach the Firefly III endpoint, transaction posting will fail.