This article provides a complete, practical walkthrough of the Splitout Filter Create Scheduled n8n agent. It connects HTTP Request, Webhook across approximately 1 node(s). Expect a Intermediate setup in 15-45 minutes. One‑time purchase: €29.

What This Agent Does

This agent orchestrates a reliable automation between HTTP Request, Webhook, handling triggers, data enrichment, and delivery with guardrails for errors and rate limits.

It streamlines multi‑step processes that would otherwise require manual exports, spreadsheet cleanup, and repeated API requests. By centralizing logic in n8n, it reduces context switching, lowers error rates, and ensures consistent results across teams.

Typical outcomes include faster lead handoffs, automated notifications, accurate data synchronization, and better visibility via execution logs and optional Slack/Email alerts.

How It Works

The workflow uses standard n8n building blocks like Webhook or Schedule triggers, HTTP Request for API calls, and control nodes (IF, Merge, Set) to validate inputs, branch on conditions, and format outputs. Retries and timeouts improve resilience, while credentials keep secrets safe.

Third‑Party Integrations

• HTTP Request
• Webhook

Import and Use in n8n

1. Open n8n and create a new workflow or collection.
2. Choose Import from File or Paste JSON.
3. Paste the JSON below, then click Import.
4. Show n8n JSON

   Title:  
   Automating Google Drive Permissions Audits Using n8n: A Step-by-Step Workflow for Better Access Control
   
   Meta Description:  
   Discover how to automate Google Drive permissions audits using n8n. This no-code workflow checks for publicly shared or externally accessible files and sends email reports with findings, improving your data security posture.
   
   Keywords:  
   Google Drive, n8n workflow, access control, document security, Google Sheets, Gmail API, automation, permissions audit, shared drive, external sharing, no-code, workflow automation
   
   Third-party APIs Used:
   
   - Google Drive API (via n8n)
   - Google Sheets API (via n8n)
   - Gmail API (via n8n)
   
   Article:
   
   In today’s collaborative digital environments, ensuring that sensitive business documents are shared appropriately is an ongoing challenge. Google Drive makes file sharing simple—but sometimes too simple, inadvertently increasing data exposure. Over time, permissions can become too permissive, especially when users share documents externally or with open access links (“Anyone with the link”).
   
   To tackle this issue, we’ve created an automated audit solution using n8n, a powerful open-source workflow automation tool. This dynamic setup retrieves recently modified files from Google Drive, analyzes their sharing settings, logs results to Google Sheets, and sends an actionable audit report via email—all without a line of traditional code.
   
   Let’s explore the components and function of this ready-to-use n8n workflow template.
   
   ⏰ 1. Scheduled Daily Audit Trigger  
   The workflow begins with a Schedule Trigger node configured to execute at 6 AM daily. This ensures logs are created consistently, allowing security teams to stay informed of recent sharing behaviors. As part of this initialization, the workflow also creates a new tab in an existing Google Sheet titled with the current date—for example, audit-20240610—where the day's findings will be stored.
   
   📁 2. Retrieving Recently Modified Google Drive Files  
   Next, we use the Google Drive node with an advanced query to fetch recently modified documents (within the last 24 hours). The system filters for Docs, Sheets, and Slides that are not trashed and collects metadata like file ID, name, sharing status, and permissions list.
   
   🔐 3. Identifying At-Risk Documents  
   The core of this audit lies in detecting over-shared documents:
   
   - Public Link Sharing: Files where the permission type is set to “anyone,” meaning anyone with the link can access the document.
   - External Email Access: Files shared with email addresses outside the specified domain (e.g., not ending with "example.com"), thus indicating access beyond the organization.
   
   Files identified through either condition are passed to the next step for permission-level analysis.
   
   🔄 4. Splitting and Filtering Permissions  
   Once a flagged document is identified, we loop through each file using a Split In Batches node, extract each permission entry using a Split Out node, and drop any entries for document owners. This step ensures the report focuses only on external viewers, editors, or collaborators.
   
   📊 5. Normalizing and Logging Audit Results  
   With the relevant sharing information extracted, a Set node is used to normalize and rename the fields—such as file_name, user, role, permission type—to ensure consistency. These records are aggregated into rows and reshaped into a flat structure appropriate for appending to our audit spreadsheet.
   
   📄 6. Appending to Google Sheets  
   We utilize the Google Sheets API to append structured data rows into the newly created audit sheet. This log provides a historical record of potential sharing violations and can be referenced or analyzed later for trends.
   
   📧 7. Emailing the Audit Report  
   Finally, a Gmail node compiles the audit findings into a well-formatted text report. The email includes two key sections:
   
   - “Shared with Anyone (Public Link)”: Listing files that allow unrestricted access.
   - “Shared with External Users (By Invite)”: Highlighting files shared specifically with outside individuals.
   
   The report also contains a link to the complete audit spreadsheet, allowing the recipient to dive deeper into the data for further action.
   
   🛠 Additional Customization Options  
   This workflow is easily adaptable for your specific security needs. Consider the following tweaks:
   
   - Adjust scheduling to run weekly, hourly, or at critical workflow endpoints.
   - Replace domain filtering logic with an allowlist of trusted domains.
   - Replace the output destination with Slack, MS Teams, or incident response tools.
   - Swap out Google integrations for Microsoft 365 equivalents like SharePoint and Outlook.
   
   🌐 Requirements
   
   To run this workflow, you will need:
   
   - Google Drive OAuth2 credentials
   - Google Sheets OAuth2 credentials
   - Gmail OAuth2 credentials
   - An n8n instance (self-hosted or cloud)
   
   🔒 Why This Matters  
   File-sharing sprawl is a creeping risk in many organizations. A document initially shared for collaboration purposes may remain available long after its utility is gone. Without regular audits, this creates persistent avenues for data leaks or unintended access. Automating audits helps maintain a tight security posture while enriching your organization's observability around access management.
   
   📣 Try It Yourself  
   Deploy this prebuilt workflow in your n8n environment and start auditing your Google Drive today. You can also extend this concept as part of your broader SecOps strategy!
   
   Need help customizing or deploying this workflow? Join the growing n8n community on Discord or in the forum.
   
   Stay secure, and happy automating!

5. Set credentials for each API node (keys, OAuth) in Credentials.
6. Run a test via Execute Workflow. Inspect Run Data, then adjust parameters.
7. Enable the workflow to run on schedule, webhook, or triggers as configured.

Tips: keep secrets in credentials, add retries and timeouts on HTTP nodes, implement error notifications, and paginate large API fetches.

Validation: use IF/Code nodes to sanitize inputs and guard against empty payloads.

Why Automate This with AI Agents

AI‑assisted automations offload repetitive, error‑prone tasks to a predictable workflow. Instead of manual copy‑paste and ad‑hoc scripts, your team gets a governed pipeline with versioned state, auditability, and observable runs.

n8n’s node graph makes data flow transparent while AI‑powered enrichment (classification, extraction, summarization) boosts throughput and consistency. Teams reclaim time, reduce operational costs, and standardize best practices without sacrificing flexibility.

Compared to one‑off integrations, an AI agent is easier to extend: swap APIs, add filters, or bolt on notifications without rewriting everything. You get reliability, control, and a faster path from idea to production.

Best Practices

• Credentials: restrict scopes and rotate tokens regularly.
• Resilience: configure retries, timeouts, and backoff for API nodes.
• Data Quality: validate inputs; normalize fields early to reduce downstream branching.
• Performance: batch records and paginate for large datasets.
• Observability: add failure alerts (Email/Slack) and persistent logs for auditing.
• Security: avoid sensitive data in logs; use environment variables and n8n credentials.

FAQs

Can I swap integrations later? Yes. Replace or add nodes and re‑map fields without rebuilding the whole flow.

How do I monitor failures? Use Execution logs and add notifications on the Error Trigger path.

Does it scale? Use queues, batching, and sub‑workflows to split responsibilities and control load.

Is my data safe? Keep secrets in Credentials, restrict token scopes, and review access logs.