HumationHuman + Automation
Back to Catalog

Daily cash flow reports with Google Sheets, Slack & Email for finance teams

Oneclick AI SquadOneclick AI Squad
619 views
2/3/2026
HTTPLoggingWebhookData CaptureAPI Integration
Official Page

Simplify financial oversight with this automated n8n workflow. Triggered daily, it fetches cash flow and expense data from a Google Sheet, analyzes inflows and outflows, validates records, and generates a comprehensive daily report. The workflow sends multi-channel notifications via email and Slack, ensuring finance professionals stay updated with real-time financial insights. 💸📧

Key Features

  • Daily automation keeps cash flow tracking current.
  • Analyzes inflows and outflows for actionable insights.
  • Multi-channel alerts enhance team visibility.
  • Logs maintain a detailed record in Google Sheets.

Workflow Process

  • The Every Day node triggers a daily check at a set time.
  • Get Cash Flow Data retrieves financial data from a Google Sheet.
  • Analyze Inflows & Outflows processes the data to identify trends and totals.
  • Validate Records ensures all entries are complete and accurate.
  • If records are valid, it branches to:
    • Sends Email Daily Report to finance team members.
    • Send Slack Alert to notify the team instantly.
  • Logs to Sheet appends the summary data to a Google Sheet for tracking.

Setup Instructions

  • Import the workflow into n8n and configure Google Sheets OAuth2 for data access.
  • Set the daily trigger time (e.g., 9:00 AM IST) in the "Every Day" node.
  • Test the workflow by adding sample cash flow data and verifying reports.
  • Adjust analysis parameters as needed for specific financial metrics.

Prerequisites

  • Google Sheets OAuth2 credentials
  • Gmail API Key for email reports
  • Slack Bot Token (with chat:write permissions)
  • Structured financial data in a Google Sheet

Google Sheet Structure:

  1. Create a sheet with columns:
    • Date
    • Cash Inflow
    • Cash Outflow
    • Category
    • Notes
    • Updated At

Modification Options

  • Customize the "Analyze Inflows & Outflows" node to include custom financial ratios.
  • Adjust the "Validate Records" filter to flag anomalies or missing data.
  • Modify email and Slack templates with branded formatting.
  • Integrate with accounting tools (e.g., Xero) for live data feeds.
  • Set different trigger times to align with your financial review schedule.

Discover more workflows – Get in touch with us

Daily Cash Flow Reports with Google Sheets, Slack, and Email for Finance Teams

This n8n workflow automates the generation and distribution of daily cash flow reports, making it easier for finance teams to stay updated. It fetches data from Google Sheets, processes it, generates a report, and then distributes it via Slack and email.

What it does

This workflow simplifies the daily cash flow reporting process by:

  1. Triggering Daily: The workflow is scheduled to run automatically, likely at a specific time each day (though the exact schedule is not defined in the provided JSON).
  2. Fetching Cash Flow Data: It retrieves the latest cash flow data from a specified Google Sheet.
  3. Processing Data (Placeholder): A Code node is included, suggesting that the fetched data is processed or transformed before report generation. The specific logic within this node is not visible in the JSON.
  4. Merging Data (Placeholder): A Merge node is present, indicating that data from different sources or different stages of processing might be combined.
  5. Generating Report (Placeholder): An HTTP Request node is included, which could be used to interact with an external service or API to generate a formatted report (e.g., a PDF, an image, or a structured text).
  6. Distributing to Slack: The generated report or a summary is posted to a designated Slack channel, ensuring the finance team receives timely updates.
  7. Sending via Email: The report is also sent to specified email addresses, providing an alternative or supplementary distribution channel.
  8. Google Drive (Placeholder): A Google Drive node is present, which could be used to store the generated report or fetch additional files.

Prerequisites/Requirements

To use this workflow, you will need:

  • n8n Instance: A running instance of n8n.
  • Google Sheets Account: With access to the spreadsheet containing your cash flow data.
  • Google Drive Account: For potential file storage or retrieval.
  • Slack Account: With a workspace and channel where reports will be posted.
  • SMTP Credentials: For sending emails.
  • External API/Service (Optional): If the HTTP Request node is used to interact with a report generation service, you will need credentials and configuration for that service.

Setup/Usage

  1. Import the Workflow: Import the provided JSON into your n8n instance.
  2. Configure Credentials:
    • Google Sheets: Set up your Google Sheets credential to grant n8n access to your cash flow spreadsheet.
    • Google Drive: Configure your Google Drive credential if you plan to use this node.
    • Slack: Set up your Slack credential to allow n8n to post messages to your desired channel.
    • Send Email: Configure your SMTP credentials for sending emails.
  3. Customize Nodes:
    • Schedule Trigger (ID: 839): Configure the schedule for when you want the daily report to run (e.g., every weekday morning).
    • Google Sheets (ID: 18): Specify the Spreadsheet ID and Sheet Name where your cash flow data resides.
    • Code (ID: 834): Implement your JavaScript logic to process and transform the cash flow data as needed. This is crucial for generating a meaningful report.
    • Merge (ID: 24): If you have multiple data sources or processing steps, configure how they should be merged.
    • HTTP Request (ID: 19): If you use an external service for report generation, configure the URL, method, headers, and body for the API call.
    • Slack (ID: 40): Configure the Slack channel and the message content for your report. You can use expressions to include data from previous nodes.
    • Send Email (ID: 11): Specify the recipient email addresses, subject, and body of the email. You can attach the report generated by the HTTP Request node.
    • Google Drive (ID: 58): If used, configure the operation (e.g., upload, download) and file details.
  4. Activate the Workflow: Once configured, activate the workflow to enable it to run on schedule.

Related Templates

Automate Dutch Public Procurement Data Collection with TenderNed

TenderNed Public Procurement What This Workflow Does This workflow automates the collection of public procurement data from TenderNed (the official Dutch tender platform). It: Fetches the latest tender publications from the TenderNed API Retrieves detailed information in both XML and JSON formats for each tender Parses and extracts key information like organization names, titles, descriptions, and reference numbers Filters results based on your custom criteria Stores the data in a database for easy querying and analysis Setup Instructions This template comes with sticky notes providing step-by-step instructions in Dutch and various query options you can customize. Prerequisites TenderNed API Access - Register at TenderNed for API credentials Configuration Steps Set up TenderNed credentials: Add HTTP Basic Auth credentials with your TenderNed API username and password Apply these credentials to the three HTTP Request nodes: "Tenderned Publicaties" "Haal XML Details" "Haal JSON Details" Customize filters: Modify the "Filter op ..." node to match your specific requirements Examples: specific organizations, contract values, regions, etc. How It Works Step 1: Trigger The workflow can be triggered either manually for testing or automatically on a daily schedule. Step 2: Fetch Publications Makes an API call to TenderNed to retrieve a list of recent publications (up to 100 per request). Step 3: Process & Split Extracts the tender array from the response and splits it into individual items for processing. Step 4: Fetch Details For each tender, the workflow makes two parallel API calls: XML endpoint - Retrieves the complete tender documentation in XML format JSON endpoint - Fetches metadata including reference numbers and keywords Step 5: Parse & Merge Parses the XML data and merges it with the JSON metadata and batch information into a single data structure. Step 6: Extract Fields Maps the raw API data to clean, structured fields including: Publication ID and date Organization name Tender title and description Reference numbers (kenmerk, TED number) Step 7: Filter Applies your custom filter criteria to focus on relevant tenders only. Step 8: Store Inserts the processed data into your database for storage and future analysis. Customization Tips Modify API Parameters In the "Tenderned Publicaties" node, you can adjust: offset: Starting position for pagination size: Number of results per request (max 100) Add query parameters for date ranges, status filters, etc. Add More Fields Extend the "Splits Alle Velden" node to extract additional fields from the XML/JSON data, such as: Contract value estimates Deadline dates CPV codes (procurement classification) Contact information Integrate Notifications Add a Slack, Email, or Discord node after the filter to get notified about new matching tenders. Incremental Updates Modify the workflow to only fetch new tenders by: Storing the last execution timestamp Adding date filters to the API query Only processing publications newer than the last run Troubleshooting No data returned? Verify your TenderNed API credentials are correct Check that you have setup youre filter proper Need help setting this up or interested in a complete tender analysis solution? Get in touch 🔗 LinkedIn – Wessel Bulte

Wessel BulteBy Wessel Bulte
247

AI-powered code review with linting, red-marked corrections in Google Sheets & Slack

Advanced Code Review Automation (AI + Lint + Slack) Who’s it for For software engineers, QA teams, and tech leads who want to automate intelligent code reviews with both AI-driven suggestions and rule-based linting — all managed in Google Sheets with instant Slack summaries. How it works This workflow performs a two-layer review system: Lint Check: Runs a lightweight static analysis to find common issues (e.g., use of var, console.log, unbalanced braces). AI Review: Sends valid code to Gemini AI, which provides human-like review feedback with severity classification (Critical, Major, Minor) and visual highlights (red/orange tags). Formatter: Combines lint and AI results, calculating an overall score (0–10). Aggregator: Summarizes results for quick comparison. Google Sheets Writer: Appends results to your review log. Slack Notification: Posts a concise summary (e.g., number of issues and average score) to your team’s channel. How to set up Connect Google Sheets and Slack credentials in n8n. Replace placeholders (<YOURSPREADSHEETID>, <YOURSHEETGIDORNAME>, <YOURSLACKCHANNEL_ID>). Adjust the AI review prompt or lint rules as needed. Activate the workflow — reviews will start automatically whenever new code is added to the sheet. Requirements Google Sheets and Slack integrations enabled A configured AI node (Gemini, OpenAI, or compatible) Proper permissions to write to your target Google Sheet How to customize Add more linting rules (naming conventions, spacing, forbidden APIs) Extend the AI prompt for project-specific guidelines Customize the Slack message formatting Export analytics to a dashboard (e.g., Notion or Data Studio) Why it’s valuable This workflow brings realistic, team-oriented AI-assisted code review to n8n — combining the speed of automated linting with the nuance of human-style feedback. It saves time, improves code quality, and keeps your team’s review history transparent and centralized.

higashiyama By higashiyama
90

🎓 How to transform unstructured email data into structured format with AI agent

This workflow automates the process of extracting structured, usable information from unstructured email messages across multiple platforms. It connects directly to Gmail, Outlook, and IMAP accounts, retrieves incoming emails, and sends their content to an AI-powered parsing agent built on OpenAI GPT models. The AI agent analyzes each email, identifies relevant details, and returns a clean JSON structure containing key fields: From – sender’s email address To – recipient’s email address Subject – email subject line Summary – short AI-generated summary of the email body The extracted information is then automatically inserted into an n8n Data Table, creating a structured database of email metadata and summaries ready for indexing, reporting, or integration with other tools. --- Key Benefits ✅ Full Automation: Eliminates manual reading and data entry from incoming emails. ✅ Multi-Source Integration: Handles data from different email providers seamlessly. ✅ AI-Driven Accuracy: Uses advanced language models to interpret complex or unformatted content. ✅ Structured Storage: Creates a standardized, query-ready dataset from previously unstructured text. ✅ Time Efficiency: Processes emails in real time, improving productivity and response speed. *✅ Scalability: Easily extendable to handle additional sources or extract more data fields. --- How it works This workflow automates the transformation of unstructured email data into a structured, queryable format. It operates through a series of connected steps: Email Triggering: The workflow is initiated by one of three different email triggers (Gmail, Microsoft Outlook, or a generic IMAP account), which constantly monitor for new incoming emails. AI-Powered Parsing & Structuring: When a new email is detected, its raw, unstructured content is passed to a central "Parsing Agent." This agent uses a specified OpenAI language model to intelligently analyze the email text. Data Extraction & Standardization: Following a predefined system prompt, the AI agent extracts key information from the email, such as the sender, recipient, subject, and a generated summary. It then forces the output into a strict JSON structure using a "Structured Output Parser" node, ensuring data consistency. Data Storage: Finally, the clean, structured data (the from, to, subject, and summarize fields) is inserted as a new row into a specified n8n Data Table, creating a searchable and reportable database of email information. --- Set up steps To implement this workflow, follow these configuration steps: Prepare the Data Table: Create a new Data Table within n8n. Define the columns with the following names and string type: From, To, Subject, and Summary. Configure Email Credentials: Set up the credential connections for the email services you wish to use (Gmail OAuth2, Microsoft Outlook OAuth2, and/or IMAP). Ensure the accounts have the necessary permissions to read emails. Configure AI Model Credentials: Set up the OpenAI API credential with a valid API key. The workflow is configured to use the model, but this can be changed in the respective nodes if needed. Connect the Nodes: The workflow canvas is already correctly wired. Visually confirm that the email triggers are connected to the "Parsing Agent," which is connected to the "Insert row" (Data Table) node. Also, ensure the "OpenAI Chat Model" and "Structured Output Parser" are connected to the "Parsing Agent" as its AI model and output parser, respectively. Activate the Workflow: Save the workflow and toggle the "Active" switch to ON. The triggers will begin polling for new emails according to their schedule (e.g., every minute), and the automation will start processing incoming messages. --- Need help customizing? Contact me for consulting and support or add me on Linkedin.

DavideBy Davide
1616