This article provides a complete, practical walkthrough of the Code Readpdf Send 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: Automate PDF Filtration and Uploads from Gmail to Google Drive Using OpenAI and n8n
   
   Meta Description:
   Learn how to automate the process of extracting, analyzing, and uploading specific PDF email attachments—like payslips or invoices—using n8n, OpenAI, and Google Drive. Streamline your workflow with this low-code automation.
   
   Keywords:
   n8n workflow, OpenAI, Gmail automation, Google Drive, email PDF filter, payslip automation, invoice PDF automation, generative AI workflows, low-code automation, document management, automate email attachments, PDF text extraction, GPT-3, AI-powered email automation
   
   Third-Party APIs Used:
   
   - Gmail API (via n8n Gmail Trigger Node)
   - OpenAI API (ChatGPT / GPT-3 model integration)
   - Google Drive API (via n8n Google Drive Node)
   
   Article:
   
   Automating Attachment-Based Workflows: Sending Specific PDF Emails to Google Drive Using OpenAI & n8n
   
   Managing email attachments such as invoices, receipts, contracts, or payslips can be tedious. Sorting through these attachments manually to find specific documents wastes valuable time. But what if you could automate that process—filtering for content-rich PDFs and uploading the necessary files directly into your Google Drive?
   
   That’s exactly what the following n8n workflow does. By combining the power of OpenAI's natural language capabilities with Gmail and Google Drive through n8n’s low-code platform, this automation helps you streamline document management effortlessly.
   
   Let’s explore how it works.
   
   Overview of the Workflow
   
   At a high level, this n8n workflow performs the following:
   
   1. Listens for incoming emails with attachments via Gmail.
   2. Iterates over the email’s attachments, identifying PDFs.
   3. Extracts the text content from each PDF.
   4. Sends the content to OpenAI to determine whether it matches a specified term (like “payslip” or “invoice”).
   5. If the document matches, it is automatically uploaded to a designated Google Drive folder.
   
   This setup allows for flexible customization depending on what types of documents you regularly receive and wish to process automatically.
   
   Deep Dive into the Workflow Components
   
   1. Gmail Trigger: Receiving Emails
   
   The workflow is triggered using the “On email received” node. This Gmail node is configured to poll every minute for new emails and automatically download the attachments. Thanks to the built-in support for OAuth2 credentials and attachment fetching, it delivers emails along with their files reliably.
   
   2. Attachment Validator: Does the Email Have Attachments?
   
   The next check ensures that there are indeed attachments with the incoming email. If no files are detected, the workflow halts, saving unnecessary processing.
   
   3. Iterating Through Attachments
   
   A Code node runs custom JavaScript to loop through each attachment found in the email. This ensures that each attachment (especially when multiple are present) is processed individually.
   
   4. Format Checker: Is the File a PDF?
   
   Next, an "If" node checks the file extension to confirm that the attachment is a PDF. If it's not, the file is ignored.
   
   5. Text Extraction: Reading the PDF Content
   
   For all valid PDF files, we use n8n’s Read PDF node to extract text. This is later passed to the OpenAI model for natural language understanding.
   
   6. Token Limit Safety Net
   
   Documents are then screened to ensure the extracted text doesn’t exceed the preconfigured token limits defined in the “Configure” node. This is important to avoid exceeding OpenAI’s input restrictions.
   
   7. AI-Assisted Filtering: Is This the PDF We’re Looking For?
   
   Here’s where the magic happens. The extracted text (and filename) is sent to the OpenAI node, where a prompt asks a simple question:
   Does this PDF look like a [MATCH TERM]?
   
   The MATCH TERM is defined in advance—this could be “invoice,” “payslip,” “contract,” etc. Based on the context of the PDF and its content, OpenAI replies strictly with "true" or "false".
   
   8. Decision Point: Matched or Not
   
   The workflow evaluates the AI’s response. If "true", it passes the PDF to the final stage. If "false", the workflow concludes for that particular attachment.
   
   9. Upload to Google Drive
   
   At the final stage, qualified PDF attachments are automatically uploaded into a specified Google Drive folder. The folder URL is defined in the “Configure” node, but behind the scenes, the Google Drive node translates that URL to the folder ID and handles the upload seamlessly.
   
   Configuring the Workflow
   
   The workflow’s “Configure” node makes it easy to customize behavior without diving into logic blocks. Here’s what can be edited:
   
   - Match on: The filter term (e.g., “invoice”, “payslip”).
   - Google Drive folder: The custom upload destination.
   - maxTokenSize: Maximum allowed tokens for OpenAI input (usually tied to model capacity).
   - replyTokenSize: The expected token size of OpenAI’s “true” or “false” response.
   
   Use Case Scenarios
   
   - HR Departments: Automatically filter and upload payslips for record-keeping.
   - Accounting Teams: Sort and archive invoices from various vendors.
   - Legal Firms: Look for “contract” files submitted via email and archive them centrally.
   - Freelancers: Detect and organize receipts from online transactions for tax season.
   
   Limitations and Considerations
   
   - OpenAI Misclassification: While powerful, the AI may occasionally misclassify a PDF. Always validate outcomes, especially when handling sensitive or financial documents.
   - Token Limits: Large PDFs may be skipped to avoid exceeding token limits, unless chunking and summarization strategies are implemented.
   - API Credentials: Ensure proper credentials are configured for Gmail, OpenAI, and Google Drive.
   
   Final Thoughts
   
   This n8n workflow exemplifies how AI and automation can work together to optimize routine business processes. By integrating Gmail, OpenAI, and Google Drive in a seamless pipeline, users can eliminate repetitive tasks and focus on strategic work.
   
   Whether you're looking to automate document filing or build intelligent workflows, this template is a practical example of what’s possible with modern automation tools and a bit of low-code ingenuity.
   
   Workflow developed by David Sha — visit davidsha.me to explore more intelligent automation solutions.

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.