This article provides a complete, practical walkthrough of the Manual Code 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 Domain Scans with Icypeas Using n8n: A Step-by-Step Workflow Guide
   
   Meta Description:
   Learn how to automate single domain or company scans using the Icypeas API and n8n. This guide walks through authentication, API integration, and execution of automated scans with practical setup tips.
   
   Keywords:
   n8n workflow, Icypeas API, automate domain scan, HTTP request n8n, custom API authentication, domain scanner automation, Icypeas single search, Icypeas integration, Node-based automation, digital footprint scanning
   
   Third-Party APIs Used:
   - Icypeas API (https://icypeas.com)
   
   Article:
   
   Automating Domain Scans with Icypeas Using n8n: A Step-by-Step Workflow Guide
   
   For professionals in cybersecurity, marketing, or competitive analysis, scanning and profiling domains or companies is a crucial task. Icypeas, a platform designed to uncover digital footprints and gather domain intelligence, can become even more powerful when automated. This article walks you through how to use the n8n automation platform to perform a single domain scan using the Icypeas API, dramatically cutting down manual work and improving real-time analysis workflows.
   
   Introduction to n8n and Icypeas
   
   n8n is a popular open-source workflow automation tool that allows users to integrate APIs and automate repetitive tasks without needing deep coding expertise. In this scenario, we're combining the flexibility of n8n with the analytical powers of Icypeas—a platform that enables users to discover domain-related intelligence such as associated technologies, subdomains, WHOIS records, and more.
   
   This article is based on a real n8n workflow titled “Perform a domain search (single) with Icypeas.” We'll explore each component of the workflow and explain how it interacts with Icypeas to scan a single domain input.
   
   Workflow Overview
   
   The entire process is divided into three major steps:
   
   1. Manually triggering the workflow
   2. Authenticating with Icypeas
   3. Executing a domain/company scan and reviewing results
   
   Step 1: Manual Trigger
   
   The workflow starts with a Manual Trigger node. This simply allows users to execute the workflow manually via the n8n UI. This is ideal for testing or one-off domain scans without having to rely on automated schedules or external triggers.
   
   Step 2: Authenticating with Icypeas
   
   Before accessing any secure data via Icypeas, you need to authenticate using your API credentials. The workflow includes a code node named "Authenticates to your Icypeas account", which relies on custom JavaScript to securely generate headers required by Icypeas for API validation.
   
   Key variables to insert:
   - API_KEY: Your Icypeas API key
   - API_SECRET: Your secret token
   - USER_ID: Your Icypeas user ID
   
   These credentials can be retrieved from your Icypeas profile page (https://app.icypeas.com/bo/profile).
   
   Inside the node, a SHA1-based HMAC signature is dynamically generated using the Crypto module. This signature is vital for authorization and is based on a combination of HTTP method, API path, and current timestamp.
   
   For self-hosted users, don't forget to enable Node.js crypto module in your n8n instance by:
   - Navigating to Settings → General → Additional Node Packages
   - Enabling the “crypto” option
   
   Step 3: Performing the Domain Scan
   
   Once authenticated, the next step uses an HTTP Request node named “Run domain scan (single).” This step sends a POST request to the Icypeas API with the required headers and body parameters.
   
   Key configurations needed in this node:
   - Authentication set to HTTP Header Auth with credentials created dynamically.
   - Header includes:
     - X-ROCK-TIMESTAMP: dynamic timestamp
     - Authorization: composed expression of API key and the generated signature
   
   You must also provide the domain or company you want to scan in the body. For example, scanning "google" will look for any digital footprint associated with the term through Icypeas’ powerful engine.
   
   To see your scan results, visit:
   https://app.icypeas.com/bo/singlesearch?task=domain-search
   
   Configuration Tips
   
   - Always use the “Expression” mode in n8n fields where dynamic values like {{ $json.api.key + ':' + $json.api.signature }} are needed.
   - Create explicit sticky notes inside your n8n canvas to document what each node does, improving team collaboration and future troubleshooting.
   - Make sure all required parameters inside the HTTP request are filled correctly. Icypeas expects the domain name to appear under the “domainOrCompany” field in the body payload.
   
   Benefits of Working with Icypeas + n8n
   
   By connecting Icypeas with n8n:
   - You automate a traditionally manual task
   - You speed up domain intelligence gathering
   - You free up time for analysis instead of data collection
   - Your team gains consistent and repeatable outcomes
   
   Conclusion
   
   The integration of Icypeas domain scanning with n8n's workflow platform offers a scalable and flexible solution for security analysts, digital marketers, and analysts who need frequent domain intelligence. Whether you're studying competitors, vetting business partnerships, or simply performing tech stack analysis, this automation gives you the edge in extracting insights faster and more accurately.
   
   This guide unlocks a powerful use case—just imagine what else you could automate with a little customization and imagination.
   
   Start today by signing up at https://icypeas.com and integrating with n8n to bring intelligence automation to your workspace.
   
   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.