Ossian Madisson
Workflows by Ossian Madisson
Gmail attachment manager with Google Drive upload and smart filtering
# This n8n template allows you to automatically upload all attached files from incoming emails to Google Drive with optional filters on sender, receiver and file types This template is built to be customized for your specific needs. This template has the core logic and n8n node specific references sorted to work with dynamic file names throughout the workflow. ## Use cases * Store invoices in Google Drive * Save recurring reports in Google Drive * Post recurring reports to another n8n workflow for further processing * Archive files to Google Drive by email * Save all files received by a client in a dedicated Google Drive folder ## Good to know * The workflow is designed to not use custom code, preferring built-in nodes in n8n ## How it works * Trigger on incoming emails with attachments * (Optional) filter on sender/recipient * Splits all attachments of the email into separate items * (Optional) filter attachment based on file type * (Optional) treat attachments with different file types through different paths * Upload attachment to Google Drive * Mark the email read and archive it after all attachments has been processed * Notify in Slack how many attachments was processed in the execution ## How to use * Configure Google credentials (1,2,6) * Configure Slack credentials (7) * Configure or disable sender/receiver filter (3) * Configure or disable file type filter (4) * Configure or disable file type paths (5) * Configure destination folder (6) * Build on this to fit your use case ## Note: there's a [similar template](https://n8n.io/workflows/2966-upload-multiple-attachments-from-gmail-to-google-drive-without-a-code-node/) with the same basics but with less ready-made modifications and no loop that allows us to archive the email and notify to Slack when done.
Perform Multi-type DNS Lookups with Google's Free Public DNS Service
# This n8n template makes it easy to perform DNS lookups directly within your n8n workflow using dns.google, without any API credentials. ## Use Cases * **Track changes:** Schedule execution and log DNS answers to track changes to records over time. * **Monitoring and alerts:** Schedule execution for DNS monitoring to detect misconfiguration and to trigger immediate alerts. * **Prerequisite checks:** Use in more extensive workflows to ensure DNS resolves correctly before running a website crawl or other sensitive tasks. ## Good to Know * Requires **no API credentials**. You do not need to sign up for any third party service for DNS resolution. * Can easily be modified to use with a **webhook** instead of the default **Forms** node for external triggering. * By default performs lookup for: A CNAME AAAA MX TXT NS ## How It Works 1. The workflow checks the input for a specified DNS type. If none is found, it uses all types in a predefined list. 2. It splits the data into separate items for each DNS type. 3. It loops through all items and executes DNS resolution via the highly reliable _dns.google_ service. 4. It aggregates all results into a single, easy-to-use output structure. ## How to Use 1. Import the template and execute the workflow to enter the domain you want to look up in the Form interface. 2. Connect the final output node to your specific use case (logging, alerting, subsequent workflow steps, etc.).
Scheduled monitoring of new & modified files across Google Drive folders
# This n8n template allows you to, on a schedule, list all files that have been modified since the last execution in a Google Drive folder and in all its subfolders While Google Drive is accessible and easy to use, file listings via API are limited to either all files in the entire Drive or all files in a specific folder. This also means that the n8n triggers for Google Drive are limited to changes to a specific file or folder. This template is built to replace the built-in trigger nodes in the situations when you need to trigger on new or changed files in a folder or any of its subfolders. ## Use cases * Trigger a RAG pipeline to update with new or updated documents * Push newly uploaded or updated documents into CMS, project management tool or other external platform * Log changes to build an audit trail * Trigger a backup job or sync process only for files that have changed since the last run, saving bandwidth and processing time. * Notify team or client about new documents * Can also be run without the scheduling part to perform a one-time iteration of all files ## Good to know * Works well if you attach a loop node to the "output node" to run additional actions on the files * The workflow is designed to use a minimal amount of custom code, preferring built-in nodes in n8n * Does not identify file removals ## How it works * Recursively executes a subworkflow for each folder in the main folder * Each subworkflow execution sends a list of all files in the folder to an "output node" that checks if the files was created or modified since the last execution * When all subworkflows have been executed, the files in the main folder are sent to the "output node" * A persistent variable (time of trigger node activation) is set for timestamp comparison on the next execution (**this is only set on non-manually triggered active workflow executions**) ## How to use * Set schedule interval in the trigger node (default every 60min) * Add Google Drive credentials to the four Google Drive nodes * Define your main/root folder in the two nodes inside the red box * Connect your workflow to process the files after the node in the yellow box, please note that there will be "one output" per folder