gmail-statement-fetcher

Automating bank statement PDF downloads from Gmail is done by using IMAP or OAuth authentication to fetch emails, driven by a bank-config.json file to support multiple banks without changing code.

UID-based deduplication tracks unique email identifiers to prevent re-downloading the same Gmail bank statements, ensuring each email is processed only once across multiple workflow runs.

You can decrypt password-protected bank statement PDFs automatically by applying per-bank passwords configured in your settings, using pikepdf for optional PDF decryption after extraction.

You need either OAuth or IMAP credentials stored in a .env file to fetch financial statements from Gmail, enabling secure authentication and environment-based secret handling for your workflows.

The best way to handle multiple banks when downloading email statements is using a config-driven approach where you define bank settings in a JSON file, avoiding code modifications for each new bank.

Bank statement ZIP attachments fail to extract automatically if ZIP extraction is not enabled or per-bank passwords are missing, which are required for processing encrypted archives within the config-driven workflow.