Credit Card Statement Processing and Payment Tracking System - n8n Workflow

• Individuals who hold multiple credit cards (especially with Taiwan banks like SINOPAC, CTBC, Fubon, etc.).


• Users prone to missing credit card payment deadlines who need reliable Google Calendar reminders.


• Finance professionals or personal users looking for powerful n8n templates to handle recurring financial tasks.


• Automation specialists needing a comprehensive example of conditional Gmail routing combined with data extraction.

Managing multiple credit card payment dates across different banks can be complex and lead to late fees if not handled efficiently. This powerful n8n workflow solves this problem by creating an automated financial monitoring system. Utilizing the flexibility of the n8n platform, it monitors several dedicated bank email accounts via the n8n trigger for Gmail. Once a statement is received, it handles PDF data extraction (if necessary), standardizes the payment information (amount, due date, bank name), logs the transaction in Google Sheets, and crucially, sets up a specific payment reminder in Google Calendar. Furthermore, this n8n workflow includes a secondary Webhook path allowing users to instantly mark the payment as 'Paid' upon confirmation, automatically updating both Google Calendar and the Google Sheets tracking log, ensuring accuracy and peace of mind.

This comprehensive n8n workflow operates primarily via two main paths:

1. Statement Receipt and Reminder Setup (Primary Flow)

1. Trigger Activation: The primary flow is activated by several parallel Gmail n8n trigger nodes, configured to listen for emails from specific Taiwan banks (e.g., SINOPAC, Cathay, CTBC, Fubon, E.SUN, DBS, Union, Taishin).


2. Data Extraction: For banks that send statements as PDF attachments, the data is passed to an 'Extract From File' n8n node to pull critical details like the due date and amount.


3. Data Standardization: A series of dedicated 'Set' n8n node branches standardize the extracted or email-parsed data, tagging it with the correct bank name, ensuring uniform data structure.


4. Data Merge and Organization: All standardized payment data streams converge into the 'Organize Data' n8n node.


5. Calendar Reminder: The workflow uses the 'Create Google Calendar Event' n8n node to schedule a reminder event on the payment due date.


6. Logging: The data, including the generated Google Calendar Event ID, is logged into a central Google Sheets spreadsheet for long-term tracking.

2. Payment Confirmation and Status Update (Secondary Flow)

1. Manual Trigger: A Webhook n8n trigger is exposed, likely linked to a dashboard or manual button, which accepts a payload (e.g., the Calendar Event ID) confirming payment completion.


2. Lookup: The workflow uses the 'Get Google Calendar Event by id' n8n node to retrieve the reminder event.


3. Update Calendar: The 'Update Google Calendar event staus' n8n node changes the status of the event (e.g., marks it as completed or deleted).


4. Update Sheet: Finally, the 'Update Google Sheets pay status' n8n node updates the corresponding row in the tracking sheet, marking the transaction as paid.

To deploy this powerful n8n workflow template, follow these steps:

1. Import: Copy the provided JSON code and paste it into your n8n instance using the 'Import from JSON' option.


2. Credentials Setup: You must configure credentials for the following services:

1. Configuration Check (Data Extraction): Review the 'Extract From File' and 'Set' n8n node configurations for each bank path. You may need to customize the data parsing logic based on the precise formatting of the PDFs received from your banks.


2. Webhook Setup: Note the URL provided by the 'Webhook' n8n node. This URL must be integrated into your payment confirmation mechanism (e.g., a simple HTML button, a mobile app shortcut, or another n8n workflow).


3. Activation: Ensure the n8n workflow is activated and test each bank path individually using test emails or the manual n8n trigger.

Gmail Trigger (e.g., Gmail-SINOPAC): This specific n8n trigger monitors a designated Gmail account for incoming credit card statements based on sender and subject line filters. There are eight such parallel triggers, demonstrating a robust structure for complex routing.
Extract From File (e.g., SINOPACPDF): This crucial n8n node is configured to extract structured data (like due date and payment amount) from PDF attachments received via the previous Gmail n8n node. This is a key step for integrating banks that only send statements in PDF format.
Set (e.g., SINOPACset field, Organize Data): These set n8n nodes standardize the diverse incoming data fields into a consistent structure, which is essential before interacting with Google Sheets or Calendar. The 'Organize Data' node acts as the central data consolidation point.
Create Google Calendar Event: This n8n node takes the extracted due date and bank name to automatically schedule a payment reminder event, linking the event ID back into the subsequent nodes.
Google Sheets (Write/Update): Used both for initial data logging (storing the payment details and calendar ID) and later for updating the payment status once confirmed.
Webhook: This acts as an external n8n trigger, allowing an external call (e.g., a manual 'Paid' button press) to initiate the status update sequence.

• Google Calendar (Get Event/Update Status): These n8n nodes handle the retrieval and modification of the reminder event, marking the obligation as fulfilled in your personal calendar.