Multi-platform revenue reconciliation across Stripe, PayPal & bank with tax archive
Ready for 3.0Ready for 3.0. This template uses no nodes that n8n 3.0 removes. No removed nodes, versions or helpers found. Static check, last run 2026-10-19.
What this workflow does
This workflow has 16 nodes and runs on a schedule (every month at 02:00). Along the way it connects Google Drive and Gmail.
How it runs
Trigger: On a schedule (every month at 02:00).
- Workflow Configuration (Edit Fields (Set)): sets 6 fields: stripeApiUrl, paypalApiUrl, bankApiUrl…
- Get Stripe Revenue (HTTP Request): calls an HTTP API
- Get PayPal Revenue (HTTP Request): calls an HTTP API
- Get Bank Statements (HTTP Request): calls an HTTP API
- Normalize Stripe Data (Edit Fields (Set)): sets 6 fields: transactionId, amount, currency…
- Normalize PayPal Data (Edit Fields (Set)): sets 6 fields: transactionId, amount, currency…
- Normalize Bank Data (Edit Fields (Set)): sets 6 fields: transactionId, amount, currency…
- Combine Revenue Sources (Merge): merges the data from its input branches
- Reconcile Revenue vs Bank (Code): runs custom JavaScript code
- Check for Mismatches (If): checks a condition and branches into true / false
…plus 5 more steps. See the full node list below.
Services it uses
Before you upgrade to n8n 3.0
Nothing in this workflow is removed in n8n 3.0, so it should import and run after the upgrade.
Nodes used (9)
- Schedule Trigger
n8n-nodes-base.scheduleTrigger - Edit Fields (Set)
n8n-nodes-base.set - HTTP Request
n8n-nodes-base.httpRequest - Merge
n8n-nodes-base.merge - Code
n8n-nodes-base.code - If
n8n-nodes-base.if - Aggregate
n8n-nodes-base.aggregate - Google Drive
n8n-nodes-base.googleDrive - Gmail
n8n-nodes-base.gmail
From the author
How It Works This workflow automates monthly revenue reconciliation across Stripe, PayPal, and bank statements by standardizing data formats, detecting discrepancies, and producing audit-ready reports. It concurrently retrieves revenue data from multiple…