Sync multi-bank balance data to BigQuery using Plaid
Ready for 3.0What this workflow does
This workflow has 17 nodes and runs on a schedule (every week). Along the way it connects Google BigQuery. It also calls production.plaid.com over HTTP.
How it runs
Trigger: On a schedule (every week).
- Fetch RBC Balances (Plaid) (HTTP Request): calls production.plaid.com (POST)
- Fetch Amex Balances (Plaid) (HTTP Request): calls production.plaid.com (POST)
- Fetch Wise Balances (Plaid) (HTTP Request): calls production.plaid.com (POST)
- Fetch PayPal Balances (Plaid) (HTTP Request): calls production.plaid.com (POST)
- Split RBC Accounts (Split Out): splits a list into separate items
- Split Amex Accounts (Split Out): splits a list into separate items
- Split Wise Accounts (Split Out): splits a list into separate items
- Split PayPal Accounts (Split Out): splits a list into separate items
- Map RBC Accounts to QBO (Code): runs custom JavaScript code
- Map Amex Accounts to QBO (Code): runs custom JavaScript code
…plus 6 more steps. See the full node list below.
Services it uses
HTTP calls to: production.plaid.com
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 (6)
- Schedule Trigger
n8n-nodes-base.scheduleTrigger - HTTP Request
n8n-nodes-base.httpRequest - Split Out
n8n-nodes-base.splitOut - Code
n8n-nodes-base.code - Merge
n8n-nodes-base.merge - Google BigQuery
n8n-nodes-base.googleBigQuery
From the author
Quick overview This workflow automatically fetches balances from multiple financial institutions (RBC, Amex, Wise, PayPal) using Plaid, maps them to QuickBooks account names, and loads structured records into Google BigQuery for analytics. How it works 1. The…