File & Document Management Automation Workflows — Page 2 | Neura Market
    Neura Market
    Neura Market
    /Categories
    Marketplace
    Directories
    Resources
    Home/Categories/File & Document Management

    File & Document Management Workflows

    Document processing and management

    • Automatically Save Gmail Attachments to Google Drive

      ## Gmail Attachment Extractor to Google Drive Description: This workflow monitors your Gmail inbox for new emails, specifically those with attachments, and automatically saves those attachments to a designated folder in your Google Drive. Use Case: Automatically archive invoices, client documents, reports, or photos sent via email to a structured cloud storage. ## How It Works This workflow operates in three main steps: **Gmail New Email Trigger**: The workflow starts with a Gmail trigger node, set to monitor for new emails in your specified Gmail inbox (e.g., your primary inbox). It checks for emails that contain attachments. Conditional Check (Optional but Recommended): An If node checks if the email actually has attachments. This prevents errors if an email without an attachment somehow triggers the workflow. **Upload to Google Drive**: A Google Drive node receives the email data and its attachments. It's configured to upload these attachments to a specific folder in your Google Drive. The attachments are named dynamically based on their original filenames. ## Setup Steps To get this workflow up and running, follow these instructions: Step 1: Create Gmail and Google Drive Credentials in n8n In your n8n instance, click on Credentials in the left sidebar. Click New Credential. Search for and select Gmail OAuth2 API and follow the authentication steps with your Google account. Save it. Click New Credential again. Search for and select Google Drive OAuth2 API and follow the authentication steps with your Google account. Save it. Make note of the Credential Names (e.g., My Gmail Account, My Google Drive Account). Step 2: Create a Destination Folder in Google Drive Go to your Google Drive (drive.google.com). Create a new folder where you want to save the email attachments (e.g., Email Attachments Archive). Copy the Folder ID from the URL (e.g., https://drive.google.com/drive/folders/YOUR_FOLDER_ID_HERE).

    Marketplace

    • Prompts
    • Workflows
    • Agents Store
    • Workflow Packs
    • Categories
    • Marketplace

    Directories

    • AI Tools Directory
    • ChatGPT
    • Claude
    • Gemini
    • Cursor
    • Grok
    • DeepSeek
    • Perplexity
    • CoPilot
    • Midjourney
    • Stable Diffusion
    • MCP Servers
    • .md Directory
    • All Directories

    Free Tools

    • AI Text Humanizer
    • AI Content Detector
    • Workflow Generator
    • Model Comparison
    • AI Pricing Calculator
    • AI Benchmarks
    • ROI Calculator
    • All Free Tools

    Resources

    • AI News
    • Blog
    • AI Models
    • Integrations
    • Alternatives
    • n8n vs Zapier
    • Make vs Zapier
    • n8n vs Make
    • Resource Library
    • Documentation

    Community

    • AI Jobs
    • AI Events
    • AI Companies
    • Start Selling
    • Sell n8n Workflows
    • Sell AI Agents
    • Sell Prompts
    • Creator Guide
    • Advertise
    • Affiliates

    Company

    • About
    • Contact
    • Help
    • Careers
    • Pricing
    • Terms
    • Privacy
    • License
    • DMCA

    Stay Updated

    Get the latest AI tools and insights delivered to your inbox.

    Neura Market Logoneuramarket

    © 2026 Neura Market. All rights reserved.

    n8n
    Free
  1. Automatically Generate Quotes in Google Docs from New Google Sheets Rows

    Automatically create a quote document in Google Docs for each new row added in a Google Sheets spreadsheet. This workflow streamlines the process of generating quotes by using predefined templates.

    MakeFree
  2. Seamlessly Convert Markdown to Google Docs with Automatic Formatting

    Effortlessly transform Markdown content into Google Docs with preserved formatting, timestamped naming, and organized storage in Google Drive. Ideal for content teams needing streamlined collaboration and review.

    n8nFree
  3. Bulk PDF to Markdown Conversion with Google Drive & LLM-Powered Parsing

    This workflow contains community nodes that are only compatible with the self-hosted version of n8n. ## High-Volume PDF to Markdown Conversion Convert multiple PDF documents to clean, structured Markdown format in bulk. Perfect for documentation teams, content managers, and anyone needing to process large volumes of PDFs. ### Key Features: - Process PDFs from multiple sources (URLs, Google Drive, Dropbox) - Intelligent LLM-based parsing for complex layouts - Preserve formatting, tables, and structure - Export to various destinations ### Workflow Components: 1. **Input Sources**: Multiple file sources supported 2. **Batch Processing**: Handle hundreds of PDFs efficiently 3. **Smart Parsing**: Auto-detect when LLM parsing is needed 4. **Quality Check**: Validate conversion results 5. **Export Options**: Save to cloud storage or database ### Ideal For: - Converting technical documentation - Migrating legacy PDF content - Building searchable knowledge bases

    n8nFree
  4. Automate SlideShare Downloads to Google Drive with RapidAPI

    Streamline the process of downloading SlideShare presentations and saving them directly to Google Drive using the Slideshare Downloader Pro API.

    n8nFree
  5. Create a Google Drive MCP Server for File Search and Content Extraction

    Set up a Google Drive MCP server to search files and extract content using AI tools. This workflow enables efficient file management and content retrieval from Google Drive.

    n8nFree
  6. Dropbox Tool MCP Server - All 11 Operations

    Need help? Want access to this workflow + many more paid workflows + live Q&A sessions with a top verified n8n creator? [Join the community](https://www.skool.com/beyond-nodes-automation-lab-2006/about) Complete MCP server exposing all Dropbox tool operations to AI agents. Zero configuration needed - all 11 operations pre-built. ## Quick Setup 1. **Import** this workflow into your n8n instance 2. **Activate** the workflow to start your MCP server 3. **Copy** the webhook URL from the MCP trigger node 4. **Connect** AI agents using the MCP URL ## How it Works - **MCP Trigger**: Serves as your server endpoint for AI agent requests - **Tool Nodes**: Pre-configured for every Dropbox tool operation - **AI Expressions**: Automatically populate parameters via `$fromAI()` placeholders - **Native Integration**: Uses official n8n Dropbox tool with full error handling ## Available Operations (11 total) Every possible Dropbox tool operation is included: ### File (5 operations) - **Copy a file** - **Delete a file** - **Download a file** - **Move a file** - **Upload a file** ### Folder (5 operations) - **Copy a folder** - **Create a folder** - **Delete a folder** - **List a folder** - **Move a folder** ### Search (1 operation) - **Query** ## AI Integration **Parameter Handling**: AI agents automatically provide values for: - Resource IDs and identifiers - Search queries and filters - Content and data payloads - Configuration options **Response Format**: Native Dropbox tool API responses with full data structure **Error Handling**: Built-in n8n error management and retry logic ## Usage Examples Connect this MCP server to any AI agent or workflow: - **Claude Desktop**: Add MCP server URL to configuration - **Custom AI Apps**: Use MCP URL as tool endpoint - **Other n8n Workflows**: Call MCP tools from any workflow - **API Integration**: Direct HTTP calls to MCP endpoints ## Benefits - **Complete Coverage**: Every Dropbox tool operation available - **Zero Setup**: No parameter mapping or configuration needed - **AI-Ready**: Built-in `$fromAI()` expressions for all parameters - **Production Ready**: Native n8n error handling and logging - **Extensible**: Easily modify or add custom logic > **[Free for community use](https://github.com/Cfomodz/community-use)!** Ready to deploy in under 2 minutes.

    n8nFree
  7. Automate Google Docs Template Population with n8n Form Data

    Streamline document creation by automatically replacing placeholders in Google Docs templates with data from n8n forms.

    n8nFree
  8. Upload & Categorize Files with Supabase Storage and Secure URL Generation

    # Supabase Storage File Upload Workflow *works with self-hosted Supabase* ## How it works - Accepts file data (MIME type, filename, base64 content) from other workflows - Automatically routes files to appropriate storage buckets based on file type (images, audio, video, documents) - Uploads files to Supabase Storage using the REST API - Generates secure signed URLs for file access with 30-day expiration - Returns structured success/error responses for downstream processing ## Set up steps - Configure Supabase API credentials in n8n - Create storage buckets in your Supabase project (image-files, audio-files, video-files, document-files) (or choose your own structuring system) - Replace URL paths with your own - Test the workflow using the included form trigger - Remove test form and integrate with your main workflows **Reference:** [Supabase Storage Documentation](https://supabase.com/docs/guides/storage)

    n8nFree
  9. Save email attachments to Google Drive

    Every time you receive an email with an attachment, Make will automatically save that attachment to a specified folder in Google Drive. he attachment will be saved in its original format.

    MakeFree
  10. Automate Audio Transcription and Summarization with Notion Integration

    Streamline your audio content processing by automatically transcribing and summarizing audio files, then storing the summaries in Notion for easy access and organization.

    n8nFree
  11. PDF Document Filling and Generation Server for AI Agents with doqs.dev API

    Complete MCP server exposing 14 doqs.dev | PDF filling API operations to AI agents. ## Quick Setup Need help? Want access to more workflows and even live Q&A sessions with a top verified n8n creator? All 100% free? [Join the community](https://www.skool.com/n8n-nodes-automation-lab-1570/about) 1. **Import** this workflow into your n8n instance 2. **Credentials** Add doqs.dev | PDF filling API credentials 3. **Activate** the workflow to start your MCP server 4. **Copy** the webhook URL from the MCP trigger node 5. **Connect** AI agents using the MCP URL ## How it Works This workflow converts the doqs.dev | PDF filling API into an MCP-compatible interface for AI agents. - **MCP Trigger**: Serves as your server endpoint for AI agent requests - **HTTP Request Nodes**: Handle API calls to https://api.doqs.dev/v1 - **AI Expressions**: Automatically populate parameters via `$fromAI()` placeholders - **Native Integration**: Returns responses directly to the AI agent ## Available Operations (14 total) ### Designer (7 endpoints) - **GET /designer/templates/**: List templates - **POST /designer/templates/**: Create template - **POST /designer/templates/preview**: Preview - **DELETE /designer/templates/{id}**: Delete - **GET /designer/templates/{id}**: List templates - **PUT /designer/templates/{id}**: Update template - **POST /designer/templates/{id}/generate**: Generate Pdf ### Templates (7 endpoints) - **GET /templates**: List - **POST /templates**: Create - **DELETE /templates/{id}**: Delete - **GET /templates/{id}**: Get template - **PUT /templates/{id}**: Update - **GET /templates/{id}/file**: Get File - **POST /templates/{id}/fill**: Fill ## AI Integration **Parameter Handling**: AI agents automatically provide values for: - Path parameters and identifiers - Query parameters and filters - Request body data - Headers and authentication **Response Format**: Native doqs.dev | PDF filling API responses with full data structure **Error Handling**: Built-in n8n HTTP request error management ## Usage Examples Connect this MCP server to any AI agent or workflow: - **Claude Desktop**: Add MCP server URL to configuration - **Cursor**: Add MCP server SSE URL to configuration - **Custom AI Apps**: Use MCP URL as tool endpoint - **API Integration**: Direct HTTP calls to MCP endpoints ## Benefits - **Zero Setup**: No parameter mapping or configuration needed - **AI-Ready**: Built-in `$fromAI()` expressions for all parameters - **Production Ready**: Native n8n HTTP request handling and logging - **Extensible**: Easily modify or add custom logic > **[Free for community use](https://github.com/Cfomodz/community-use)!** Ready to deploy in under 2 minutes.

    n8nFree
  12. Automate Image to PDF Conversion with Google Slides and Drive

    Effortlessly convert images from a Google Drive folder into a single PDF using Google Slides as an intermediary. Customize the PDF's page size and orientation for free.

    n8nFree
  13. Automate Google Drive File Organization by MIME Type

    This n8n workflow automatically organizes files in a specified Google Drive folder by detecting their MIME types and moving them to designated folders for documents, PDFs, and images. It streamlines file management, saving time and reducing manual effort.

    n8nFree
  14. Create a REST API for PDF Digital Signatures with Webhooks

    ## Overview An automation workflow that creates a complete REST API for digitally signing PDF documents using n8n webhooks. This service demonstrates how to implement secure document signing functionality through standardized API endpoints with file upload and download capabilities. ## Use Case This workflow is designed for developers and automation specialists who need to implement digital document signing. It's particularly useful for: - Integrating PDF signing capabilities into existing document workflows - API-based automation of signature processes - Creating proof-of-concept implementations for document verification systems - Learning n8n's webhook capabilities and file handling techniques - Testing PDF signing in development environments before production implementation ## What This Workflow Does ### API-Based Document Management - Exposes RESTful webhook endpoints for all document operations - Handles multipart/form-data uploads for PDF documents - Processes JSON payloads for signing configuration - Provides download functionality for completed documents ### Digital Certificate Handling - Uploads existing PFX/PKCS#12 digital certificates - Generates new certificates with customizable attributes - Securely manages certificate storage and access - Associates certificates with signing operations ### Cryptographic PDF Signing - Applies digital signatures using industry-standard cryptographic methods - Embeds signature information within PDF document structure - Validates document integrity through cryptographic verification - Preserves original document while adding signature elements ### Webhook Integration System - Routes different API methods to appropriate handlers - Validates request payloads and file content - Manages authentication through webhook paths - Returns structured responses for integration with other systems ## Technical Architecture ### Components 1. **API Gateway**: n8n webhook nodes that receive external requests 2. **Request Router**: Switch nodes that direct operations based on method parameters 3. **Document Processor**: Function nodes for PDF manipulation and verification 4. **Certificate Manager**: Specialized nodes for cryptographic key operations 5. **Storage Interface**: File operation nodes for document persistence 6. **Response Formatter**: Nodes that structure API responses ### Integration Flow ``` Client Request → Webhook Endpoint → Method Router → Processing Engine → Digital Signing → Storage → Response Generation → Client Response ``` ## Setup Instructions ### Prerequisites - n8n installation (minimum version 0.214.0) - Node.js 14 or higher - Required environment variable: ``` NODE_FUNCTION_ALLOW_EXTERNAL: node-forge,@signpdf/signpdf,@signpdf/signer-p12,@signpdf/placeholder-plain ``` ### Configuration Steps 1. **Import Workflow** - Import the workflow JSON into your n8n instance - Activate the workflow to enable the webhooks 2. **Configure Storage** - Set the storage path variables in the workflow - Ensure proper permissions on the storage directories 3. **Test API Endpoints** - Use the included test scripts to verify functionality - Test PDF upload, certificate generation, and signing 4. **Integration** - Document the webhook URLs for integration with other systems - Configure error handling according to your requirements ### Testing Methods Test the workflow functionality using various HTTP requests and JSON data: - Upload PDF documents to the document processing endpoint - Upload or generate digital certificates - Execute PDF signing operations - Download signed documents from the download endpoint ## Webhook Endpoints The workflow exposes two primary webhook endpoints that form a complete API for PDF digital signing operations: ### 1. Document Processing Endpoint (`/webhook/docu-digi-sign`) This endpoint handles all document and certificate operations: **Method: Upload PDF** - HTTP: `POST` - Content-Type: multipart/form-data - Parameters: method, uploadType, fileName, fileData **Method: Upload Certificate** - HTTP: `POST` - Content-Type: multipart/form-data - Parameters: method, uploadType, fileName, fileData **Method: Generate Certificate** - HTTP: `POST` - Content-Type: application/json - Parameters: method, subjectCN, issuerCN, serialNumber, validFrom, validTo, password **Method: Sign PDF** - HTTP: `POST` - Content-Type: application/json - Parameters: method, inputPdf, pfxFile, pfxPassword ### 2. Document Download Endpoint (`/webhook/docu-download`) This endpoint handles the retrieval of processed documents: **Method: Download Signed PDF** - HTTP: `GET` - Content-Type: application/json - Parameters: method, fileType, fileName ## Key Workflow Sections The workflow is organized into logical sections with clear responsibilities: - **Request Processing**: Parses incoming webhook data - **Method Routing**: Directs requests to appropriate handlers - **Document Management**: Handles file operations and storage

    n8nFree
  15. Monitor File Changes with Google Drive Push Notifications

    **Tired of being let down by the Google Drive trigger? Rather not exhaust system resources by polling every minute? Then this workflow is for you!** Google Drive is a great storage option for automation due to its relative simplicity, cheap costs, and readily-available integrations. Using Google Drive as a trigger is the next logical step, but many n8n users quickly realize the built-in Google Drive trigger just isn't that reliable. Disaster! Typically, the workaround is to poll the Google Drive search API in short intervals, but the trade-off is wasted server resources during inactivity. The ideal solution is, of course, push notifications, but they seem quite complicated to implement... or are they? This template demonstrates that setting up **Google Push Notifications for Google Drive File Changes** actually isn't that hard! Using this approach, Google sends a POST request every time something in a drive changes, which solves the reliability of events and efficiency of resources. ### How it works 1. We begin with registering a **Notification channel (webhook)** with the Google Drive API. 2 key pieces of information are (a) the webhook URL which notifications will be pushed to and (b) because we want to scope to a single location, the driveId. Good to know that you can register as many as you like using HTTP calls, but you have to manage them yourself, there's no Google dashboard for notification channels! 2. The registration data along with the startPageToken are saved in `workflowStaticData` - This is a convenient persistence which we can use to hold small bits of data between executions. 3. Now, whenever files or folders are created or updated in our target Google Drive, Google will send push notifications to our webhook trigger in this template. 4. Once triggered, we still need to call Google Drive's `Changes.list` to get the actual change events which were detected. We can do this with the HTTP request node. 5. The Changes API will also return the `nextPageToken` - a marker to establish where next to get the new batch of changes. It's important that we use this token the next time we request from the changes API, and so, we'll update the `workflowStaticData` with this updated value. 6. Unfortunately, the `changes.list` API isn't able to filter change events by folder or action, and so be sure to do your own set of filtering steps to get the files you want. 7. Finally, with the valid change events, optionally fetch the file metadata which gives you more attributes to play with. For example, you may want to know if the change event was triggered by n8n, in which case you'll want to check the ModifiedByMe value. ### How to use * Start with Step 1 and fill in the Set Variables node and Click on the Manual Execute trigger. This will create a single Google Drive Notification Channel for a specific drive. * Activate the workflow to start receiving events from Google Drive. * To test, perform an action e.g., create a file, on the target drive. Watch the webhook calls come pouring in! * Once you have the desired events, finish off this template to do something with the changed files. ### Requirements * Google Drive Credentials. Note this workflow also works on Shared Drives. ### Optimizing This Workflow * With bulk actions, you'll notice that Google gradually starts to send increasingly large amounts of push notifications - sometimes numbering in the hundreds! For cloud plan users, this could easily exhaust execution limits if lots of changes are made in the same drive daily. One approach is to implement a throttling mechanism externally to batch events before sending them to n8n. * This throttling mechanism is outside the scope of this template but quite easy to achieve with something like Supabase Edge Functions.

    n8nFree
  16. Automate Gmail Attachment Backup to Google Drive

    This n8n workflow automatically backs up email attachments from a specified sender in Gmail to a designated folder in Google Drive, ensuring secure and organized storage.

    n8nFree
  17. Build Your Own FileSystem MCP Server

    **This template is for self-hosted n8n instances only.** ### This n8n demonstrates how to build a simple FileSystem MCP server. Connecting to this server allows MCP clients and agents to list, read, and create directories and files on the local machine or remote server. This MCP example is based off an official MCP reference implementation which can be found here - [https://github.com/modelcontextprotocol/servers/tree/main/src/filesystem](https://github.com/modelcontextprotocol/servers/tree/main/src/filesystem) ### How it works - A MCP server trigger is used and connected to 5 tools: 3 Execute Command tools and 2 custom workflow tools. - The 3 Execute Command tools allow for listing, searching, and creating directories. - The 2 custom workflow tools are for reading and writing files to disk. - Special care has been taken to not allow the MCP agent to execute arbitrary Linux commands on the target server. This is achieved by only allowing the agent to provide parameters such as filenames and paths rather than raw commands. ### How to use - This Filesystem MCP server will write to the server which hosts the n8n instance - this can be your local machine or a remote server. If your target filesystem is on neither, then modify the commands to connect to the desired server. - Connect your MCP client by following the n8n guidelines here - https://docs.n8n.io/integrations/builtin/core-nodes/n8n-nodes-langchain.mcptrigger/#integrating-with-claude-desktop - Try the following queries in your MCP client: - Please help me list all folders under the project directory. - Help me create a bash script to send a notification to Slack. - Search for the log file on the 22nd April and read its contents. What was the cause of the outage? ### Requirements - Linux file system for this example template. Feel free to modify if working on Windows. - MCP Client or Agent for usage such as Claude Desktop - https://claude.ai/download ### Customizing this workflow - Implement the moving and renaming of files by adding more custom workflow tools to the MCP server. - Remember to set the MCP server to require credentials before going to production and sharing this MCP server with others!

    n8nFree
  18. Change Binary Mimetype/Extension

    ### How it works This workflow changes the file name, and therefore the extension and MIME type, of any binary file passed to it. This is perfect for converting file formats on the fly, like turning a Telegram voice message (`.oga`) into an MP3 for an AI transcription service. 1. **Set New File Name:** The `SET OUTPUT FILE NAME` node is where you define the desired output file name and extension (e.g., `audio.mp3`). It also dynamically captures the property name of the incoming binary (e.g., `data`). 2. **Extract Binary Data:** The workflow temporarily converts the binary file into a Base64 text string to make it accessible in the next step. 3. **Rebuild Binary with New Name:** A Code node takes the Base64 data and reconstructs it as a binary file, but this time, it assigns the new file name you specified. n8n automatically sets the MIME type based on the new file extension. ### Set up steps **Setup time: < 1 minute** This workflow is designed to be used as a sub-workflow. 1. In your main workflow, add an **Execute Sub-Workflow** node where you need to change a file's type. 2. In the **Workflow** parameter, select this Change Binary Mime Type/Extension workflow. 3. **Open this workflow** and go to the **`SET OUTPUT FILE NAME`** node. 4. Modify the `output_file_name` value to your desired file name (e.g., `voice_message.mp3` or `document.pdf`). 5. Save this workflow. Now, any binary file you send to it from your main workflow will be returned with the new file name and mime type.

    n8nFree
  19. Automatically Convert and Save New SharePoint Files as PDFs

    This workflow automatically converts new files in a SharePoint library to PDF format using Plumsail Documents and saves the converted files back to SharePoint.

    MakeFree
  20. Auto-Convert OneDrive Word Documents to PDF with Foxit and Send via Gmail

    ## This n8n template demonstrates how to add a document conversion process to incoming Word documents in a OneDrive folder. Documents are converted to PDF and emailed to a reviewer. Use cases would be environments where incoming documents are dropped into cloud storage and a human needs to review them. By converting to PDF, it becomes easier to read in a consistent format in the browser. ## How it works - Listen for new files added in a OneDrive folder, identified by an ID - Download the bits of the new document if the file was a Microsoft Word document (the API I'm using can convert any Office document, but wanted to start simple) - Upload to Foxit's API service, convert to PDF, and download when done - Use Gmail to mail the PDF to a human reviewer. ## How to use - You'll need to determine a OneDrive folder ID to monitor, or select an entire account instead, just be careful when testing. - When the workflow is done, it emails to myself, so please connect your own Gmail and set a preferred email address for testing. ## Requirements - A Microsoft OneDrive account - Foxit developer account (https://developer-api.foxit.com) - A Gmail account - At least one Word document - we all have that, right? ## Next Steps This workflow could be modified to work with any Office-style document, and could also upload the PDF version back to OneDrive.

    n8nFree
  21. Organize Email Attachments into Google Drive Folders by Company with Gmail & Sheets

    # Automated Email Attachment Organizer **Automatically process labeled emails with attachments into organized Google Drive folders** --- ## Who Is This For? - **Teams or Individuals** needing to: - Automatically sort invoices, receipts, and files. - Organize client documents by date. - Verify sender emails against a whitelist. - Timestamp files to avoid duplicate names. --- ## What Does This Workflow Solve? - **Manual Email Sorting**: Saves time by automating the organization of email attachments. - **Disorganized Cloud Storage**: Ensures attachments are neatly stored in Google Drive folders. - **Unverified Sender Issues**: Filters and validates emails using a whitelist. - **Duplicate Filenames**: Uses timestamps to ensure every file name is unique. --- ## Setup Guide ### 1. Pre-Requisites - **Whitelist Sheet**: Make a copy of the [Example Whitelist Sheet](https://docs.google.com/spreadsheets/d/1tz9BflstxVL18YG11Ny1eiDj3FcjvtZ619b_bHx8h4/copy) - **Gmail Filter**: Create a filter in Gmail to label emails with attachments. **To Create a Gmail Filter:** 1. Open your Gmail Inbox. 2. Click the search bar and select **Show search options**. 3. Enter your criteria (e.g., type `has:attachment`). 4. Click **Create filter**. 5. Choose **Apply the label: Custom_Label** and save. --- ### 2. Credentials Setup Make sure your n8n instance is connected with: - **Gmail Account**: (via OAuth2) - **Google Drive Account**: (via OAuth2) - **Google Sheets** (via OAuth2) --- ### 3. Configure Your n8n Workflow Nodes #### 1. Trigger and Email Retrieval - **Gmail Trigger**: Setup check interval and filters for emails (i.e., emails labeled with `Custom_Label`) #### 2. Whitelist Settings - **Lookup in Sheets**: Searches for a row with the sender email. Configure this node to point to your whitelist spreadsheet containing two columns: |email|company| #### 3. File Storage Location - Configure parent folder to create sub-folders and store files into in the **Create Company Folder** node *Parent Folder* dropdown --- ## Final Steps 1. **Test Your Workflow**: Run the workflow to verify emails are processed and files are uploaded correctly. --- Happy Automating!

    n8nFree
  22. Generate PDF Invoices with CustomJS API

    # n8n Workflow: Invoice PDF Generator This n8n workflow captures invoice data and generates a PDF invoice, ready to be sent or saved. It uses a webhook to trigger the process, preprocesses the invoice data, and converts it to a PDF using HTML and custom styling. [@custom-js/n8n-nodes-pdf-toolkit](@custom-js/n8n-nodes-pdf-toolkit) ## Features: - **Webhook Trigger**: Receives incoming data, including invoice details. - **Preprocessing**: Transforms the invoice data into HTML format. - **HTML to PDF Conversion**: Converts the preprocessed HTML into a styled PDF document. - **Response**: Sends the generated PDF back to the webhook response. # Notice Community nodes can only be installed on self-hosted instances of n8n. ## Requirements - **Self-hosted** n8n instance - A **CustomJS API key** for website screenshots. - **Invoice data** for PDF generation ## Workflow Steps: 1. **Webhook Trigger**: - Accepts incoming data (e.g., invoice number, recipient details, itemized list). - This data is passed to the next node for processing. 2. **Set Data Node**: - Configures initial values for the invoice, including the recipient, sender, invoice number, and the items on the invoice. - The invoice details include information like description, unit price, and quantity. 3. **Preprocess Node**: - Processes the raw data to format it correctly for HTML. This includes splitting addresses and converting the items into an HTML table format. 4. **HTML to PDF Conversion**: - Converts the generated HTML into a PDF document. The HTML includes a header, a detailed invoice table, and a footer with contact information. 5. **Respond to Webhook**: - Returns the generated PDF as a response to the initial webhook request. --- ## Setup Guide: ### 1. Configure CustomJS API - Sign up at [CustomJS](https://www.customjs.space). - Retrieve your API key from the profile page. ![1.png](fileId:1057) - Add your API key as n8n credentials. ![2.png](fileId:1055) ### 2. Design Workflow 1. **Create a Webhook**: - Set up a webhook to trigger the workflow when invoice data is received. 2. **Prepare Data**: - Ensure the incoming request contains fields like Invoice No, Bill To, From, and Details (list of items with price and quantity). 3. **Customize the HTML**: - The HTML template for the invoice includes custom styling to give the invoice a professional look. 4. **Convert to PDF**: - The **HTML to PDF** node is configured with the data generated from the preprocessing step to convert the invoice HTML to a PDF format. --- ## Example Invoice Data: ```json { "Invoice No": 1, "Bill To": "John Doe\n1234 Elm St, Apt 567\nCity, Country, 12345", "From": "ABC Corporation\n789 Business Ave\nCity, Country, 67890", "Details": [ { "description": "Web Hosting", "price": 150, "qty": 2 }, { "description": "Domain", "price": 15, "qty": 5 } ], "Email": "support@mycompany.com" } ``` ## Result PDF File ![3.png](fileId:1058)

    n8nFree
  23. Automate Invoice Processing with AI and PDF.co

    Streamline your invoice processing by automatically converting PDF invoices into structured JSON using AI, and storing the data in Google Sheets.

    MakeFree
  24. ← PreviousPage 2 of 34Next →

    Related categories

    Communication (2,463)AI (1,929)Business Operations & ERPs (1,540)Other (1,425)Productivity (1,202)Marketing (1,145)Data & Analytics (995)CRM - Sales (604)Notifications (580)Social Media (562)

    Need a custom file & document management workflow?

    Our automation experts build tailored workflows for your exact stack and process.

    Request a Custom Workflow