Compare SQL Data by Customer and Year

# Compare customer orders in MySQL across periods with manual trigger

This automation template enables quick comparison of aggregated payment data for customers across two adjacent periods: 2003–2004 and 2004–2005. Ideal for analyzing customer behavior changes, verifying aggregation accuracy, and tracking sales trends over time.

## Who it´s for
- Data analysts comparing customer data across time periods
- Database developers validating consistency of aggregated values
- Sales managers monitoring customer order dynamics

## What the automation does
- Triggered manually by user action
- Fetches payment data from MySQL for 2003–2004 and 2004–2005 periods
- Groups data by customer and year
- Forces `ordercount` value to 1 in the second dataset before comparison
- Compares aggregated totals and order counts between periods
- Identifies discrepancies by customer number and year

## What´s included
- Ready-to-use n8n workflow
- Trigger and data processing logic
- Integrations with MySQL (db4free)
- Basic textual instructions for launch and adaptation

## Requirements for setup
- Access to a MySQL server (e.g., db4free)
- n8n account with workflow execution permissions
- SQL access to tables containing payment and order data

## Benefits and outcomes
- Quickly identify active or lost customers
- Verify correctness of data aggregation during migration or recalculation
- Analyze purchasing trends with overlapping year (2004)
- Automate routine comparison of large datasets
- Reduce risk of errors in manual analysis

## Important: template only
Important: you are purchasing a ready-made automation workflow template only. Rollout into your infrastructure, connecting specific accounts and services, 1:1 setup help, custom adjustments for non-standard stacks and any consulting support are provided as a separate paid service at an individual rate. To discuss custom work or 1:1 help, contact via chat