Back to Catalog

Monitor bank transactions with multi-channel alerts for accounting teams

Oneclick AI SquadOneclick AI Squad
333 views
2/3/2026
Official Page

Enhance financial oversight with this automated n8n workflow. Triggered every 5 minutes, it fetches real-time bank transactions via an API, enriches and transforms the data, and applies smart logic to detect critical, high, and medium priority alerts based on error conditions, amounts, or risk scores. It sends multi-channel notifications via email and Slack, logs all data to Google Sheets, and generates summary statistics for comprehensive tracking. πŸ’°πŸš¨

Key Features

  • Real-time monitoring every 5 minutes for instant alerts.
  • Smart prioritization (Critical, High, Medium) based on risk and errors.
  • Multi-channel notifications via email and Slack.
  • Detailed logging and summary reports in Google Sheets.

How It Works

  1. Schedule Trigger: Runs every 5 minutes.
  2. Fetch Transactions: HTTP request retrieves real-time transaction data.
  3. API Error?: If condition for error logic is met, sends error alert.
  4. Enrich & Transform Data: Advanced risk calculation enhances data.
  5. Critical Alert?: If condition (50% or risk > 8) is met, raises alert.
  6. High Priority?: If condition (5% or risk > 7) is met, raises alert.
  7. Medium Priority?: If condition is met, raises alert.
  8. Log Priority to Sheet: Google Sheets appends critical, high, or medium priority data.
  9. Send Critical Email: HTML email to execute sheets append.
  10. Send High Priority Email: Email to finance team.
  11. Send High Priority Slack: Slack notification to finance team.
  12. Send Medium Priority Email: Email to finance team.
  13. Merge All Alerts: Combines all alerts for comprehensive tracking.
  14. Generate Summary Stats: Code block for analytics.
  15. Log Summary to Sheet: Summary statistics storage.

Setup Instructions

  • Import the workflow into n8n and configure the bank API credentials in "Fetch Transactions."
  • Set up Google Sheets OAuth2 and replace the sheet ID for logging nodes.
  • Configure Gmail API Key and Slack Bot Token for alerts.
  • Test the workflow with sample transaction data exceeding risk or amount thresholds.
  • Adjust priority conditions (e.g., 50%, 5%, risk > 8) based on your risk policy.

Prerequisites

  • Bank API access with real-time transaction data (e.g., https://api.bank.com)
  • Google Sheets OAuth2 credentials
  • Gmail API Key for email alerts
  • Slack Bot Token (with chat:write permissions)
  • Structured transaction data format

Google Sheet Structure:

  1. Create a sheet with columns:
    • Transaction ID
    • Amount
    • Date
    • Risk Score
    • Priority (Critical/High/Medium)
    • Alert Sent
    • Summary Stats
    • Updated At

Modification Options

  • Adjust the "Schedule Trigger" interval (e.g., every 10 minutes).
  • Modify "Critical Alert?" and "High Priority?" conditions for custom thresholds.
  • Customize email and Slack templates with branded messaging.
  • Integrate with fraud detection tools for enhanced risk analysis.
  • Enhance "Generate Summary Stats" with additional metrics (e.g., average risk).

Discover more workflows – Get in touch with us

Monitor Bank Transactions with Multi-Channel Alerts for Accounting Teams

This n8n workflow automates the process of monitoring bank transactions and sending multi-channel alerts to accounting teams based on predefined conditions. It simplifies the process of staying informed about critical financial activities, ensuring timely responses and improved financial oversight.

What it does

This workflow performs the following key steps:

  1. Triggers on a Schedule: The workflow starts at scheduled intervals, allowing for regular checks of bank transactions.
  2. Fetches Bank Transactions: It makes an HTTP request to an external API (presumably a bank's API or a financial data provider) to retrieve the latest transaction data.
  3. Processes Transaction Data: A Code node is used to process and potentially transform the raw transaction data, preparing it for analysis.
  4. Filters Transactions: An If node evaluates each transaction based on a defined condition (e.g., transaction amount, type, or recipient).
  5. Sends Conditional Alerts:
    • If a transaction meets the specified condition (e.g., a high-value transaction or a suspicious activity), it sends an alert via Slack to the accounting team.
    • It also sends an Email notification for these specific transactions.
  6. Logs All Transactions: Regardless of whether a transaction triggers an alert, all processed transactions are logged into a Google Sheet for auditing and record-keeping purposes.
  7. Merges Paths: The workflow merges the different alert paths back together before the final logging step.

Prerequisites/Requirements

To use this workflow, you will need:

  • Bank API Access: An API endpoint and credentials to fetch bank transaction data.
  • Slack Account: A Slack workspace and a channel where alerts should be posted.
  • SMTP Server/Email Service: Configuration for sending emails (e.g., an SMTP server or a transactional email service).
  • Google Account: Access to Google Sheets to log transaction data.
  • n8n Instance: A running instance of n8n.

Setup/Usage

  1. Import the Workflow:
    • Copy the provided JSON code.
    • In your n8n instance, click "New" to create a new workflow.
    • Go to the "Workflows" menu, click "Import from JSON", and paste the copied JSON.
  2. Configure Credentials:
    • HTTP Request (Node 19): Configure the HTTP Request node with the URL and authentication details for your bank's API or financial data source.
    • Slack (Node 40): Set up your Slack credential to allow n8n to post messages to your desired channel.
    • Send Email (Node 11): Configure your email credential (SMTP server details, username, password, etc.) to send email alerts.
    • Google Sheets (Node 18): Set up your Google Sheets credential, ensuring it has access to the target spreadsheet.
  3. Customize Nodes:
    • Schedule Trigger (Node 839): Adjust the schedule to your desired frequency for checking transactions.
    • Code (Node 834): Modify the JavaScript code to parse and transform your specific bank transaction data structure.
    • If (Node 20): Define the conditions for filtering transactions that should trigger alerts. For example, {{ $json.amount > 1000 }} for transactions over $1000.
    • Slack (Node 40): Customize the message content and target channel for Slack alerts.
    • Send Email (Node 11): Customize the subject, body, and recipient email addresses for email alerts.
    • Google Sheets (Node 18): Specify the Spreadsheet ID, Sheet Name, and the data to be written for logging all transactions.
  4. Activate the Workflow: Once all configurations are complete, activate the workflow to start monitoring your bank transactions.

Related Templates

Track competitor SEO keywords with Decodo + GPT-4.1-mini + Google Sheets

This workflow automates competitor keyword research using OpenAI LLM and Decodo for intelligent web scraping. Who this is for SEO specialists, content strategists, and growth marketers who want to automate keyword research and competitive intelligence. Marketing analysts managing multiple clients or websites who need consistent SEO tracking without manual data pulls. Agencies or automation engineers using Google Sheets as an SEO data dashboard for keyword monitoring and reporting. What problem this workflow solves Tracking competitor keywords manually is slow and inconsistent. Most SEO tools provide limited API access or lack contextual keyword analysis. This workflow solves that by: Automatically scraping any competitor’s webpage with Decodo. Using OpenAI GPT-4.1-mini to interpret keyword intent, density, and semantic focus. Storing structured keyword insights directly in Google Sheets for ongoing tracking and trend analysis. What this workflow does Trigger β€” Manually start the workflow or schedule it to run periodically. Input Setup β€” Define the website URL and target country (e.g., https://dev.to, france). Data Scraping (Decodo) β€” Fetch competitor web content and metadata. Keyword Analysis (OpenAI GPT-4.1-mini) Extract primary and secondary keywords. Identify focus topics and semantic entities. Generate a keyword density summary and SEO strength score. Recommend optimization and internal linking opportunities. Data Structuring β€” Clean and convert GPT output into JSON format. Data Storage (Google Sheets) β€” Append structured keyword data to a Google Sheet for long-term tracking. Setup Prerequisites If you are new to Decode, please signup on this link visit.decodo.com n8n account with workflow editor access Decodo API credentials OpenAI API key Google Sheets account connected via OAuth2 Make sure to install the Decodo Community node. Create a Google Sheet Add columns for: primarykeywords, seostrengthscore, keyworddensity_summary, etc. Share with your n8n Google account. Connect Credentials Add credentials for: Decodo API credentials - You need to register, login and obtain the Basic Authentication Token via Decodo Dashboard OpenAI API (for GPT-4o-mini) Google Sheets OAuth2 Configure Input Fields Edit the β€œSet Input Fields” node to set your target site and region. Run the Workflow Click Execute Workflow in n8n. View structured results in your connected Google Sheet. How to customize this workflow Track Multiple Competitors β†’ Use a Google Sheet or CSV list of URLs; loop through them using the Split In Batches node. Add Language Detection β†’ Add a Gemini or GPT node before keyword analysis to detect content language and adjust prompts. Enhance the SEO Report β†’ Expand the GPT prompt to include backlink insights, metadata optimization, or readability checks. Integrate Visualization β†’ Connect your Google Sheet to Looker Studio for SEO performance dashboards. Schedule Auto-Runs β†’ Use the Cron Node to run weekly or monthly for competitor keyword refreshes. Summary This workflow automates competitor keyword research using: Decodo for intelligent web scraping OpenAI GPT-4.1-mini for keyword and SEO analysis Google Sheets for live tracking and reporting It’s a complete AI-powered SEO intelligence pipeline ideal for teams that want actionable insights on keyword gaps, optimization opportunities, and content focus trends, without relying on expensive SEO SaaS tools.

Ranjan DailataBy Ranjan Dailata
161

Generate song lyrics and music from text prompts using OpenAI and Fal.ai Minimax

Spark your creativity instantly in any chatβ€”turn a simple prompt like "heartbreak ballad" into original, full-length lyrics and a professional AI-generated music track, all without leaving your conversation. πŸ“‹ What This Template Does This chat-triggered workflow harnesses AI to generate detailed, genre-matched song lyrics (at least 600 characters) from user messages, then queues them for music synthesis via Fal.ai's minimax-music model. It polls asynchronously until the track is ready, delivering lyrics and audio URL back in chat. Crafts original, structured lyrics with verses, choruses, and bridges using OpenAI Submits to Fal.ai for melody, instrumentation, and vocals aligned to the style Handles long-running generations with smart looping and status checks Returns complete song package (lyrics + audio link) for seamless sharing πŸ”§ Prerequisites n8n account (self-hosted or cloud with chat integration enabled) OpenAI account with API access for GPT models Fal.ai account for AI music generation πŸ”‘ Required Credentials OpenAI API Setup Go to platform.openai.com β†’ API keys (sidebar) Click "Create new secret key" β†’ Name it (e.g., "n8n Songwriter") Copy the key and add to n8n as "OpenAI API" credential type Test by sending a simple chat completion request Fal.ai HTTP Header Auth Setup Sign up at fal.ai β†’ Dashboard β†’ API Keys Generate a new API key β†’ Copy it In n8n, create "HTTP Header Auth" credential: Name="Fal.ai", Header Name="Authorization", Header Value="Key [Your API Key]" Test with a simple GET to their queue endpoint (e.g., /status) βš™οΈ Configuration Steps Import the workflow JSON into your n8n instance Assign OpenAI API credentials to the "OpenAI Chat Model" node Assign Fal.ai HTTP Header Auth to the "Generate Music Track", "Check Generation Status", and "Fetch Final Result" nodes Activate the workflowβ€”chat trigger will appear in your n8n chat interface Test by messaging: "Create an upbeat pop song about road trips" 🎯 Use Cases Content Creators: YouTubers generating custom jingles for videos on the fly, streamlining production from idea to audio export Educators: Music teachers using chat prompts to create era-specific folk tunes for classroom discussions, fostering interactive learning Gift Personalization: Friends crafting anniversary R&B tracks from shared memories via quick chats, delivering emotional audio surprises Artist Brainstorming: Songwriters prototyping hip-hop beats in real-time during sessions, accelerating collaboration and iteration ⚠️ Troubleshooting Invalid JSON from AI Agent: Ensure the system prompt stresses valid JSON; test the agent standalone with a sample query Music Generation Fails (401/403): Verify Fal.ai API key has minimax-music access; check usage quotas in dashboard Status Polling Loops Indefinitely: Bump wait time to 45-60s for complex tracks; inspect fal.ai queue logs for bottlenecks Lyrics Under 600 Characters: Tweak agent prompt to enforce fuller structures like [V1][C][V2][B][C]; verify output length in executions

Daniel NkenchoBy Daniel Nkencho
601

Automate invoice processing with OCR, GPT-4 & Salesforce opportunity creation

PDF Invoice Extractor (AI) End-to-end pipeline: Watch Drive ➜ Download PDF ➜ OCR text ➜ AI normalize to JSON ➜ Upsert Buyer (Account) ➜ Create Opportunity ➜ Map Products ➜ Create OLI via Composite API ➜ Archive to OneDrive. --- Node by node (what it does & key setup) 1) Google Drive Trigger Purpose: Fire when a new file appears in a specific Google Drive folder. Key settings: Event: fileCreated Folder ID: google drive folder id Polling: everyMinute Creds: googleDriveOAuth2Api Output: Metadata { id, name, ... } for the new file. --- 2) Download File From Google Purpose: Get the file binary for processing and archiving. Key settings: Operation: download File ID: ={{ $json.id }} Creds: googleDriveOAuth2Api Output: Binary (default key: data) and original metadata. --- 3) Extract from File Purpose: Extract text from PDF (OCR as needed) for AI parsing. Key settings: Operation: pdf OCR: enable for scanned PDFs (in options) Output: JSON with OCR text at {{ $json.text }}. --- 4) Message a model (AI JSON Extractor) Purpose: Convert OCR text into strict normalized JSON array (invoice schema). Key settings: Node: @n8n/n8n-nodes-langchain.openAi Model: gpt-4.1 (or gpt-4.1-mini) Message role: system (the strict prompt; references {{ $json.text }}) jsonOutput: true Creds: openAiApi Output (per item): $.message.content β†’ the parsed JSON (ensure it’s an array). --- 5) Create or update an account (Salesforce) Purpose: Upsert Buyer as Account using an external ID. Key settings: Resource: account Operation: upsert External Id Field: taxid_c External Id Value: ={{ $json.message.content.buyer.tax_id }} Name: ={{ $json.message.content.buyer.name }} Creds: salesforceOAuth2Api Output: Account record (captures Id) for downstream Opportunity. --- 6) Create an opportunity (Salesforce) Purpose: Create Opportunity linked to the Buyer (Account). Key settings: Resource: opportunity Name: ={{ $('Message a model').item.json.message.content.invoice.code }} Close Date: ={{ $('Message a model').item.json.message.content.invoice.issue_date }} Stage: Closed Won Amount: ={{ $('Message a model').item.json.message.content.summary.grand_total }} AccountId: ={{ $json.id }} (from Upsert Account output) Creds: salesforceOAuth2Api Output: Opportunity Id for OLI creation. --- 7) Build SOQL (Code / JS) Purpose: Collect unique product codes from AI JSON and build a SOQL query for PricebookEntry by Pricebook2Id. Key settings: pricebook2Id (hardcoded in script): e.g., 01sxxxxxxxxxxxxxxx Source lines: $('Message a model').first().json.message.content.products Output: { soql, codes } --- 8) Query PricebookEntries (Salesforce) Purpose: Fetch PricebookEntry.Id for each Product2.ProductCode. Key settings: Resource: search Query: ={{ $json.soql }} Creds: salesforceOAuth2Api Output: Items with Id, Product2.ProductCode (used for mapping). --- 9) Code in JavaScript (Build OLI payloads) Purpose: Join lines with PBE results and Opportunity Id ➜ build OpportunityLineItem payloads. Inputs: OpportunityId: ={{ $('Create an opportunity').first().json.id }} Lines: ={{ $('Message a model').first().json.message.content.products }} PBE rows: from previous node items Output: { body: { allOrNone:false, records:[{ OpportunityLineItem... }] } } Notes: Converts discount_total ➜ per-unit if needed (currently commented for standard pricing). Throws on missing PBE mapping or empty lines. --- 10) Create Opportunity Line Items (HTTP Request) Purpose: Bulk create OLIs via Salesforce Composite API. Key settings: Method: POST URL: https://<your-instance>.my.salesforce.com/services/data/v65.0/composite/sobjects Auth: salesforceOAuth2Api (predefined credential) Body (JSON): ={{ $json.body }} Output: Composite API results (per-record statuses). --- 11) Update File to One Drive Purpose: Archive the original PDF in OneDrive. Key settings: Operation: upload File Name: ={{ $json.name }} Parent Folder ID: onedrive folder id Binary Data: true (from the Download node) Creds: microsoftOneDriveOAuth2Api Output: Uploaded file metadata. --- Data flow (wiring) Google Drive Trigger β†’ Download File From Google Download File From Google β†’ Extract from File β†’ Update File to One Drive Extract from File β†’ Message a model Message a model β†’ Create or update an account Create or update an account β†’ Create an opportunity Create an opportunity β†’ Build SOQL Build SOQL β†’ Query PricebookEntries Query PricebookEntries β†’ Code in JavaScript Code in JavaScript β†’ Create Opportunity Line Items --- Quick setup checklist πŸ” Credentials: Connect Google Drive, OneDrive, Salesforce, OpenAI. πŸ“‚ IDs: Drive Folder ID (watch) OneDrive Parent Folder ID (archive) Salesforce Pricebook2Id (in the JS SOQL builder) 🧠 AI Prompt: Use the strict system prompt; jsonOutput = true. 🧾 Field mappings: Buyer tax id/name β†’ Account upsert fields Invoice code/date/amount β†’ Opportunity fields Product name must equal your Product2.ProductCode in SF. βœ… Test: Drop a sample PDF β†’ verify: AI returns array JSON only Account/Opportunity created OLI records created PDF archived to OneDrive --- Notes & best practices If PDFs are scans, enable OCR in Extract from File. If AI returns non-JSON, keep β€œReturn only a JSON array” as the last line of the prompt and keep jsonOutput enabled. Consider adding validation on parsing.warnings to gate Salesforce writes. For discounts/taxes in OLI: Standard OLI fields don’t support per-line discount amounts directly; model them in UnitPrice or custom fields. Replace the Composite API URL with your org’s domain or use the Salesforce node’s Bulk Upsert for simplicity.

Le NguyenBy Le Nguyen
942