Skip to main content

Consolidate and report monthly financial PDFs with Google Drive and Slack

Workflow preview

Workflow preview
100%
Consolidate and report monthly financial PDFs with Google Drive and Slack preview
Open on n8n.io

Important notice

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

1. Workflow Overview

Consolidate and report monthly financial documents using Google Drive and Slack Description Streamline your month end accounting processes with this enterprise grade automation designed to aggre...

Best for

  • Document Extraction automation workflows
  • Multimodal AI automation workflows
  • intermediate n8n builders looking for reusable templates

Tools used

n8n-nodes-base.stickynote, n8n-nodes-htmlcsstopdf.htmlcsstopdf, n8n-nodes-base.scheduletrigger, n8n-nodes-base.googledrive, n8n-nodes-base.if, n8n-nodes-base.aggregate, n8n-nodes-base.slack

Source and attribution

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

Original n8n.io source

1.1 Workflow description

Title
Consolidate and report monthly financial PDFs with Google Drive and Slack
Workflow name
Consolidate and report monthly financial PDFs with Google Drive and Slack

Consolidate and report monthly financial documents using Google Drive and Slack

🎯 Description

Streamline your month-end accounting processes with this enterprise-grade automation designed to aggregate, validate, and merge fragmented financial documents into a single, professional reporting bundle. This workflow transforms manual document chaos into a structured, touchless system using Google Drive and Slack.

✨ How to achieve automated document consolidation

You can achieve a fully autonomous financial reporting cycle by using the available tools to:

  1. List and scan folders β€” Automatically retrieve all documents from a designated Google Drive folder at the end of each month.
  2. Validate file formats β€” Use an IF Node to ensure only PDF documents (invoices, receipts, statements) are processed, preventing workflow crashes from incompatible file types.
  3. Aggregate binary data β€” Gather separate file streams into a unified data array using the Aggregate Node to ensure stable processing for the merge engine.
  4. Merge into master reports β€” Utilize the HTML to PDF engine to consolidate individual files into one "Monthly Finance Pack" with professional naming conventions.
  5. Secure and archive β€” Upload the consolidated master file back to a secure archive folder in Google Drive.
  6. Notify the team β€” Send a real-time Slack alert with the final filename, ensuring the accounting team knows exactly when the report is ready.

πŸ’‘ Key features

Intelligent filtering and validation The workflow auto-detects MIME types to filter out non-PDF noise and system files. This ensures a consistent input for the merge engine and prevents processing errors.

Advanced data aggregation By utilizing the Aggregate Node, the workflow handles multiple binary files simultaneously. This architecture prevents the "looping errors" common in basic PDF workflows and maintains document order during the merge process.

Dynamic time-stamping with Luxon A critical technical feature of this template is the use of Luxon expressions for professional document naming. By utilizing {{ $now.setZone('America/New_York').toFormat('MMMM yyyy') }} within the Slack and upload nodes, the workflow automatically generates accurate timestamps. This eliminates manual renaming and ensures your archives are perfectly organized by month and year.

🎯 Perfect for

  • Finance departments β€” Consolidate hundreds of monthly vendor invoices into one audit-ready file.
  • Property managers β€” Bundle monthly utility bills and maintenance receipts for property owners.
  • Freelancers and agencies β€” Collate all business expenses for the month to send to a tax preparer.

πŸ“¦ What you will need

Required integrations:

  1. Google Drive β€” Source folder for documents and destination for the final bundle.
  2. HTML to PDF Node β€” The core engine for PDF merging operations.
  3. Slack β€” For automated team notifications and status updates.

πŸ“ˆ Expected results

  • 90% time savings β€” Reduce manual report creation from 30 minutes to seconds.
  • Zero lost documents β€” Maintain a complete digital trail with automatic archival.
  • Audit readiness β€” Ensure a consistent naming and storage structure for all past financial reports.

Ready to automate your reporting? Import this template, connect your credentials, and turn your monthly document collection into a 100% automated workflow.

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 - Processing Sticky

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

Block 2 - Merge multiple PDFS into one

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

Block 3 - Trigger: Monthly on the 1st1

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

Block 4 - List Financial PDFs from Drive1

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

Block 5 - Validate File Format (PDF only)1

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

Block 6 - Download Documents for Processing1

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

Block 7 - Batch Files for Merging1

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

Block 8 - Upload Consolidated Master Report1

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

Block 9 - Notify Finance Team (Slack)1

Type / Role
n8n-nodes-base.slack - slack
Config choices
Version 2.1

Block 10 - Main Documentation1

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

3. Summary Table

Workflow Consolidate and report monthly financial PDFs with Google Drive and Slack
Complexity intermediate
Nodes 10
Categories Document Extraction, Multimodal AI
Author Jitesh Dugar
Published 07 Jan 2026

4. Reproducing the Workflow from Scratch

  1. 1. Download the workflow JSON

    Use the JSON export at /data/workflows/12544/12544.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 Consolidate and report monthly financial PDFs with Google Drive and Slack do?

Consolidate and report monthly financial documents using Google Drive and Slack Description Streamline your month end accounting processes with this enterprise grade automation designed to aggre...

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 Document Extraction, Multimodal AI use case.