This article provides a complete, practical walkthrough of the Googleslides Extractfromfile Create Triggered 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 Custom Lead Presentations with n8n, Google Drive, and Google Sheets
   
   Meta Description:  
   Discover how a powerful n8n workflow automates the creation of personalized sales presentations using Google Drive, Google Sheets, and Google Slides, triggered by new lead files in Google Drive folders.
   
   Keywords:  
   n8n automation, Google Sheets, Google Slides, Google Drive, sales automation, lead generation, workflow automation, personalized presentations, Google API, sales enablement
   
   Third-party APIs Used:
   
   - Google Drive API (OAuth2)
   - Google Sheets API (OAuth2)
   - Google Slides API (OAuth2)
   
   Article:
   
   Streamline Sales Outreach with n8n: Automatically Create Custom Presentations from Lead Data
   
   For any sales team handling multiple leads daily, personalization is key—but also incredibly time-consuming. Enter n8n: an open-source workflow automation tool that bridges systems and APIs to eliminate repetitive manual work. In this article, we explore a practical and compelling n8n workflow that automates the process of generating tailored slide presentations for leads using a combination of Google Drive, Google Sheets, and Google Slides.
   
   This workflow, aptly named “Create Custom Presentations per Lead,” was designed to simplify how sales collateral is generated for each incoming lead. With triggers, data extraction, and dynamic document manipulation, the workflow does all the heavy lifting once a new leads file is dropped into a folder.
   
   Let’s break down how this intelligent system works.
   
   Step 1: Detect New Lead Files
   
   The automation kicks off with a Google Drive Trigger that monitors a specific folder (i.e., “New Leads” folder on Google Drive). When a .csv or .xlsx file gets uploaded, n8n detects the file creation event and proceeds to identify its type using a Switch node.
   
   Step 2: Extract and Structure the Lead Data
   
   Upon recognizing a compatible file format (CSV or XLSX), the system downloads it and extracts the lead data. If it’s a CSV file, the data is parsed accordingly. A new Google Sheet is then created using the current date for organization (e.g., "Leads_2025-24-02"), providing a structured repository for the extracted details.
   
   Next, this structured data is merged into the sheet using AutoMap, facilitated by Google Sheets' append operation. At this point, the lead data becomes accessible to later stages which rely on name, company, and contact details.
   
   Step 3: Copy and Customize the Presentation Template
   
   Once the data is in place, the spreadsheet is moved to a designated "Lead Lists" folder, and the workflow iterates over each row (lead) to initiate the presentation creation process.
   
   The process begins by duplicating a predefined Google Slides template file stored in a “Custom Presentations” folder. The duplicate is dynamically renamed using the lead’s company and the current date, maintaining consistency and traceability.
   
   Then, the customization happens via the Google Slides API. Placeholder text such as {COMPANYNAME} and {Full Name} is automatically replaced with real values from the lead entry. This step ensures that every sales presentation gets tailored with the correct name and company details, increasing the relevancy and professional appearance of each pitch.
   
   Step 4: Log Presentation IDs for Reference
   
   To keep track of which presentation belongs to which lead, the newly generated slide deck’s Presentation ID is recorded next to the corresponding lead’s email address in the same Google Sheet. This ensures that at any point, a team member can retrieve or reference the correct presentation without needing to search manually.
   
   Why This Matters
   
   Personalized experiences are proven to improve lead engagement and conversion rates, but manual customization is rarely scalable. By integrating APIs through n8n, this workflow bridges the gap between efficiency and personalization. It minimizes human error while maximizing consistency and speed.
   
   Use Cases Beyond Sales
   
   Although this example is modeled for sales teams, the core logic can be applied across departments:
   
   - HR teams can personalize onboarding decks.
   - Educational institutions can generate customized student reports.
   - Marketing teams can generate regional campaign briefs or client proposals.
   
   Components Summary
   
   This workflow is powered by seamless integration of several Google services:
   
   - Google Drive for monitoring input files and managing storage.
   - Google Sheets for lead data parsing, transformation, and logging.
   - Google Slides for dynamic slide deck creation and personalized text replacement.
   
   By leveraging these cloud-based APIs via n8n, businesses can achieve better workflow automation without heavy development overhead.
   
   Conclusion
   
   With a smart workflow like “Create Custom Presentations per Lead,” you can take the manual grind out of personalization. Whether you’re handling five or five hundred leads a day, automating your workflow with n8n and Google Workspace APIs can significantly increase both productivity and lead engagement. It’s not just about working smarter—it’s about letting automation do the work so your team can focus on closing the deal.
   
   Ready to implement your own? Grab this workflow as a template, customize your fields and template presentation, and go from chaos to conversion in one clean sweep.

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.