This article provides a complete, practical walkthrough of the Removeduplicates Converttofile Automation Webhook 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 IP Log Collection and Delivery Using n8n and SaaS APIs
   
   Meta Description: Learn how this no-code n8n workflow automates collecting, filtering, deduplicating, and emailing IP sign-in data from SaaS Alerts using the SMTP2Go API.
   
   Keywords: n8n workflow, SaaS Alerts API, IP log automation, SMTP2Go, sign-in event tracking, CSV export, deduplicate IPs, Office365 login data, OAuth authentication, automation tools
   
   Third-Party APIs Used:
   
   1. SaaS Alerts API – https://app.swaggerhub.com/apis/SaaS_Alerts/functions  
   2. SMTP2Go Email API – https://developers.smtp2go.com/docs/send-an-email
   
   —
   
   Article:
   
   Automating IP Log Collection and Delivery Using n8n and SaaS APIs
   
   In today’s digital ecosystem, organizations require better visibility into user activity — specifically around authentication events like logins and OAuth token grants. These data points are essential for identifying suspicious IPs, enforcing security compliance, and improving incident detection. Luckily, modern low-code platforms like n8n empower businesses to automate this kind of log collection and delivery with minimal technical overhead.
   
   In this article, we’ll explore a powerful n8n workflow titled “Query List of Sign-in IPs” that integrates multiple third-party APIs to retrieve, process, and email a deduplicated report of sign-in IPs from the last 24 hours. With just a form submission, users can receive a comprehensive CSV file of activity across their organization — no manual intervention or scripting required.
   
   Overview: The Automation Workflow in Action
   
   The “Query List of Sign-in IPs” workflow initiates with a user-friendly form built using n8n’s built-in FormTrigger node. Here, the user provides their name, email address, and an API key for accessing the SaaS Alerts API.
   
   Once the form is submitted, the automation kicks off a sequence of data gathering steps:
   
   1. Set Variables and Compute Timestamps  
     Using a Set node, the workflow stores user-submitted data and dynamically calculates the timestamp for “last 24 hours,” ensuring it always fetches the most recent data.
   
   2. Fetch SaaS Authentication Events  
     Three different HTTP Request nodes are used to query the SaaS Alerts API for various authentication events, including:
      - Standard login successes (`login.success`)
      - OAuth permission grants (`oauth.granted.permission`)
      - Office365 Shell logins (`ms.shell.login.success`)
   
     Each request includes the provided API key and uses scroll and sort parameters to fetch up to 10,000 results per event type efficiently.
   
   3. Merge and Process the Data  
     Once the data from all three endpoints is retrieved, a Merge node combines the results into a single stream. From there, the workflow filters the fields to include only relevant attributes such as:
      - Customer Name
      - User Full Name
      - IP Address
      - City, Region, Country (Location Metadata)
   
   4. Deduplicate IPs  
     Security data often includes redundant entries, especially when users perform repeated logins. The Remove Duplicates node cleans the dataset by checking for uniqueness in the "ip" field, ensuring multiple entries from the same address don’t bloat the report.
   
   5. Convert and Encode to Send as Email  
     The processed data is transformed into a CSV file using the Convert to CSV node. This file is then base64 encoded (a requirement by most email APIs for file attachments) and passed to the final step.
   
   6. Send Email via SMTP2Go  
     Using the SMTP2Go API, the workflow sends an automated email to the user. The email includes:
      - Subject line: “Workflow Complete”
      - Personalized Message: Greeting by name and explanation of the attached file
      - Attachment: base64-encoded CSV containing the filtered, deduplicated IP data.
   
     SMTP2Go credentials are handled securely using n8n’s HttpHeaderAuth for authentication, ensuring sensitive API keys are never exposed.
   
   Benefits of This Automated n8n Workflow
   
   - Time-Saving: Automates a multi-step technical task with just one form submission.
   - Scalable: Can handle upwards of 10,000 events per endpoint with scroll-based querying.
   - Secure: Utilizes header-based API key authentication and encodes attachments for email delivery.
   - Customizable: Easily extended to include more event types, additional metadata, or custom formatting.
   - User-Friendly: Includes descriptive Sticky Notes and well-labeled nodes for clarity and future maintenance.
   
   Use Cases
   
   - Security Analysts tracking login activity for audit purposes
   - Compliance Officers generating routine IP activity reports
   - Managed service providers monitoring SaaS tool activity
   - IT admins tracing suspicious sign-ins across clients or subsidiaries
   
   Conclusion
   
   This n8n workflow is a great example of how low-code tools can help operations and security teams automate critical processes without relying on heavy internal development resources. By integrating SaaS Alerts and SMTP2Go APIs, the solution combines real-time data acquisition with reliable report delivery — giving users smart, timely access to their sign-in IP information.
   
   Whether you’re part of a cybersecurity team, an MSP, or a business analyst looking to streamline visibility, this type of automation offers a valuable template for transforming raw logs into actionable intelligence — all through an intuitive, visual interface.
   
   —
   
   Looking to build something similar? Check out the SaaS Alerts API documentation and SMTP2Go's email API to get started today.

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.