Skip to main content

Automate multi-bank transaction sync & reporting with GoCardless & Maybe Finance

Workflow preview

Workflow preview
100%
Automate multi-bank transaction sync & reporting with GoCardless & Maybe Finance preview
Open on n8n.io

Important notice

This workflow is provided as-is. Please review and test before using in production.

1. Workflow Overview

Who’s it for Freelancers, founders, households, and side hustlers who work with several bank accounts but want one, always up to date budget inside Maybe Finance—no more CSV exports or copy p...

Best for

  • Miscellaneous automation workflows
  • advanced n8n builders looking for reusable templates

Tools used

n8n-nodes-base.httprequest, n8n-nodes-base.stickynote, n8n-nodes-base.merge, n8n-nodes-resend.resend, n8n-nodes-base.itemlists, n8n-nodes-base.set, n8n-nodes-base.scheduletrigger

Source and attribution

This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by Giannis Kotsakiachidis.

Original n8n.io source

1.1 Workflow description

Title
Automate multi-bank transaction sync & reporting with GoCardless & Maybe Finance
Workflow name
Automate multi-bank transaction sync & reporting with GoCardless & Maybe Finance

🏦 GoCardless ⇄ Maybe Finance — Automatic Multi-Bank Sync & Weekly Overview 💸

Who’s it for 🤔

Freelancers, founders, households, and side-hustlers who work with several bank accounts but want one, always-up-to-date budget inside Maybe Finance—no more CSV exports or copy-paste.


How it works / What it does ⚙️

  1. Schedule Trigger (cron) fires every Monday 📅
    (switch to Manual Trigger while testing)
  2. Get access token — fresh 24 h GoCardless token 🔑
  3. Fetch transactions for each account:
    • Revolut Pro
    • Revolut Personal
    • ABN AMRO
      (add extra HTTP Request nodes for any other GoCardless-supported banks)
  4. Extract booked — keep only settled items 🗂️
  5. Set transactions … — map every record to Maybe Finance’s schema 📝
  6. Merge all arrays into one payload 🔄
  7. Create transactions to Maybe — POSTs each item via API 🚀
  8. Resend Email — sends you a “Weekly transactions overview” 📧

All done in a single run — your Maybe dashboard is refreshed and you get an inbox alert.


How to set up 🛠️

  1. Import the template into n8n (cloud or self-hosted).
  2. Create credentials
    • GoCardless secret_id & secret_key
    • Maybe Finance API key
    • (Optional) Resend API key for email notifications
  3. One-time GoCardless config (run the blocks on the left):
    1. /token/new/ → obtain token
    2. /institutions → find institution IDs
    3. /agreements/enduser/ → create agreements
    4. /requisitions/ → get the consent URL & finish bank login
    5. /requisitions/{id} → copy the GoCardless account_ids
  4. Create the same accounts in Maybe Finance and run the HTTP GET request in the purple frame and copy their account_ids.
  5. Open each Set transactions … node and paste the correct Maybe account_id.
  6. Adjust the Schedule Trigger (e.g. daily, monthly).
  7. Save & activate 🎉

Requirements 📋

  • n8n 1.33 +
  • GoCardless app (secret ID & key, live or sandbox)
  • Maybe Finance account & API key
  • (Optional) Resend account for email

How to customize ✨

  • Include pending transactions: change the Item Lists filter.
  • Add more banks: duplicate the “Get … transactions” → “Extract booked” → “Set transactions” path and plug its output into the Merge node.
  • Different interval: edit the cron rule in Schedule Trigger.
  • Disable emails: just remove or deactivate the Resend node.
  • Send alerts to Slack / Teams: branch after the Merge node and add a chat node.

Happy budgeting! 💰

1.2 Logical Blocks

This catalog entry is organized from the workflow JSON. The node-level section below shows the executable blocks available for review before importing the template.

2. Block-by-Block Analysis

Block 1 - Get access token

Type / Role
n8n-nodes-base.httpRequest - httpRequest
Config choices
Version 4.2

Block 2 - Get Revolut Pro transactions

Type / Role
n8n-nodes-base.httpRequest - httpRequest
Config choices
Version 4.2

Block 3 - Get Revolut Personal transactions

Type / Role
n8n-nodes-base.httpRequest - httpRequest
Config choices
Version 4.2

Block 4 - Get accounts id from Maybe

Type / Role
n8n-nodes-base.httpRequest - httpRequest
Config choices
Version 4.2

Block 5 - Sticky Note

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 6 - Step 2 - Get institution id

Type / Role
n8n-nodes-base.httpRequest - httpRequest
Config choices
Version 4.2

Block 7 - Step 5 - Get account id

Type / Role
n8n-nodes-base.httpRequest - httpRequest
Config choices
Version 4.2

Block 8 - Sticky Note1

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 9 - Create transactions to Maybe

Type / Role
n8n-nodes-base.httpRequest - httpRequest
Config choices
Version 4.2

Block 10 - Sticky Note2

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 11 - Sticky Note3

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 12 - Merge all transactions in one array

Type / Role
n8n-nodes-base.merge - merge
Config choices
Version 3.1

Block 13 - Resend

Type / Role
n8n-nodes-resend.resend - resend
Config choices
Version 1

Block 14 - Sticky Note4

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 15 - Extract booked - Revolut Personal

Type / Role
n8n-nodes-base.itemLists - itemLists
Config choices
Version 3

Block 16 - Extract booked - Revolut Pro

Type / Role
n8n-nodes-base.itemLists - itemLists
Config choices
Version 3

Block 17 - Set transactions for Revolut Pro

Type / Role
n8n-nodes-base.set - set
Config choices
Version 3.4

Block 18 - Set transactions for Revolut Personal

Type / Role
n8n-nodes-base.set - set
Config choices
Version 3.4

Block 19 - Schedule Trigger

Type / Role
n8n-nodes-base.scheduleTrigger - scheduleTrigger
Config choices
Version 1.2

Block 20 - Step 4 - Building link with Revolut

Type / Role
n8n-nodes-base.httpRequest - httpRequest
Config choices
Version 4.2

Block 21 - Step 3a - User agreement with first Revolut Account

Type / Role
n8n-nodes-base.httpRequest - httpRequest
Config choices
Version 4.2

Block 22 - Step 3a - User agreement with second Revolut Account

Type / Role
n8n-nodes-base.httpRequest - httpRequest
Config choices
Version 4.2

3. Summary Table

Workflow Automate multi-bank transaction sync & reporting with GoCardless & Maybe Finance
Complexity advanced
Nodes 22
Categories Miscellaneous
Author Giannis Kotsakiachidis
Published 22 Jul 2025

4. Reproducing the Workflow from Scratch

  1. 1. Download the workflow JSON

    Use the JSON export at /data/workflows/6284/6284.json as the source template for this automation.

  2. 2. Import the template into n8n

    Open n8n, import the downloaded JSON, and review each node before activating the workflow.

  3. 3. Configure credentials and variables

    Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.

  4. 4. Test with sample data

    Run the workflow manually or in a staging workspace, inspect node output, and confirm downstream systems receive the expected data.

  5. 5. Activate and monitor

    Enable the workflow only after testing, then monitor executions, errors, and rate limits during the first production runs.

5. General Notes & Resources

Review imported nodes carefully before activation. This catalog entry is intended to help you inspect the workflow structure, understand required services, and find related templates faster.

Node names, credentials, schedules, webhook paths, and external service limits may need adjustment for your workspace.

Frequently asked questions

What does Automate multi-bank transaction sync & reporting with GoCardless & Maybe Finance do?

Who’s it for Freelancers, founders, households, and side hustlers who work with several bank accounts but want one, always up to date budget inside Maybe Finance—no more CSV exports or copy p...

What do I need before importing this workflow?

Review the workflow JSON, configure any required credentials in n8n, and test the automation in a safe workspace before using it in production.

Can I customize this workflow?

Yes. Use the block-by-block analysis and the downloadable JSON to inspect each node, then adjust credentials, prompts, schedules, filters, or destinations for your Miscellaneous use case.