telegram-ledger

You can convert Telegram messages into finance ledger entries using a Draft -> Confirm -> Commit workflow. This parses INCOME/EXPENSE text, creates a TransactionDraft, and only writes the final entry after explicit approval via inline keyboard actions.

To enforce category and transaction type consistency during a ledger commit, apply safe commit guards using DraftStatus and PendingAction transitions. The commit only executes when the Draft is approved and Category.transaction_type matches the transaction_type.

Yes, n8n workflows integrate with FastAPI routes to handle Telegram bot callback actions. The system uses a callback action contract to process interactive inline keyboard actions for approving, rejecting, or adjusting category, amount, and date.

Validating allowed chat constraints for Telegram text parsing requires applying strict validation rules within your FastAPI endpoints. This ensures only messages from authorized chats are processed into TransactionDrafts during the staging phase.

The best way to stage partial parsing results safely is to create or update a TransactionDraft. This keeps partial INCOME/EXPENSE data secure and accessible for category matching and adjustment until the user explicitly confirms or rejects the entry.

You need a draft approval gate to prevent invalid or misinterpreted free-text data from corrupting your finance ledger. The gate generates reply summaries and inline keyboard actions, ensuring entries are only committed after explicit user review and validation.