This article provides a complete, practical walkthrough of the Code Manual 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 Bulk Search with n8n and Icypeas Integration
   
   Meta Description:
   Learn how to automate bulk domain scanning for lead generation using n8n and the Icypeas API. This step-by-step workflow integrates Google Sheets and Icypeas to streamline the process of searching company domains at scale.
   
   Keywords:
   n8n, Icypeas, domain search, API integration, Google Sheets automation, bulk search, CRM enrichment, lead generation, workflow automation, HTTP request, SHA1 signature
   
   Third-Party APIs Used:
   
   - Icypeas API (https://app.icypeas.com/api/bulk-search)
   - Google Sheets API
   
   Article:
   
   Automating Domain Bulk Search with n8n and Icypeas Integration
   
   In the data-centric world of sales and marketing, domain search has become an essential process for prospecting, CRM enrichment, and business development. With the rapid growth of SaaS tools, automating such processes is not just a luxury—it's a necessity. This article breaks down how to build an automated workflow using n8n, Google Sheets, and the Icypeas API to perform high-volume domain lookups with minimal effort.
   
   What Is Icypeas?
   
   Icypeas is a powerful data-enrichment and domain-search platform aimed at helping professionals retrieve valuable information such as domain names associated with company names. Its bulk scan feature makes it ideal for marketers, salespeople, and business analysts who deal with large datasets.
   
   The n8n Advantage
   
   n8n (short for “node-node”) is an open-source workflow automation tool that enables users to connect APIs, services, and logic using a no-code/low-code interface. With n8n, you can extract data from a source, process it, and interact with third-party APIs like Icypeas—all in one place.
   
   Overview of the Workflow
   
   This n8n workflow is designed to:
   
   - Read a list of companies from a Google Sheet.
   - Generate a secure request signature using the Icypeas API specs.
   - Make an authenticated HTTP POST request to run a bulk domain search.
   
   Step-by-Step Breakdown
   
   1. Triggering the Workflow Manually
   
   The workflow starts with a Manual Trigger node. This allows you to execute the flow on-demand within the n8n interface.
   
   2. Reading Input Data from Google Sheets
   
   The Google Sheets node is configured to fetch a list of companies from a specified worksheet. You must set up the correct document ID and sheet name. The workflow reads a column labeled "company", where each row represents a business entity you want to look up.
   
   3. Authenticating with Icypeas
   
   The next node is a custom JavaScript Code node that creates an authentication signature required by Icypeas. Here's how it works:
   
   - You must insert your API credentials from your Icypeas profile.
   - The code generates a timestamp and an HMAC-SHA1 signature using your API secret and the HTTP method and path.
   - These details are packaged into the request payload.
   
   Note for Self-Hosted Users: If you’re running your own instance of n8n, be sure to activate the built-in crypto module following these steps:
   
   - Go to Settings > General > Additional Node Packages.
   - Enable the crypto module.
   - Save and restart your instance.
   
   4. Making the API Call
   
   The HTTP Request node runs the actual domain search by sending the credentials and data to Icypeas. Here’s what happens:
   
   - The method is set to POST, targeting https://app.icypeas.com/api/bulk-search.
   - It includes headers like X-ROCK-TIMESTAMP and a custom Authorization header formed using an expression: {{ $json.api.key + ':' + $json.api.signature }}.
   - The body includes user ID, company data, and task parameters.
   
   5. Receiving the Results
   
   While the API itself doesn’t return an immediate result set, your searches will queue up in Icypeas. Here’s how to get your scans:
   
   - Visit the Icypeas interface: https://app.icypeas.com/bo/bulksearch?task=domain-search
   - Wait for the process to complete (results are usually emailed by Icypeas).
   - Download the finalized result from the dashboard or inbox.
   
   Getting Started with Credentials
   
   Before launching this workflow, ensure you collect the following from your Icypeas account:
   
   - API Key
   - API Secret
   - User ID
   
   You can find these on your Icypeas profile page: https://app.icypeas.com/bo/profile
   
   Also, don’t forget to configure Google Sheets credentials within n8n to allow access to your documents.
   
   Wrapping Up
   
   By combining n8n, Google Sheets, and the Icypeas API, this workflow demonstrates how to scale a domain search process from manual to automated. Whether you're handling dozens or thousands of company names, this integration saves time and ensures accuracy by leveraging the strengths of modern APIs and automation platforms.
   
   This is just one real-world example of how n8n can replace complex, repetitive tasks with structured, automated logic. As always, you can expand on this by adding error-handling, notifications (e.g. via Slack or email), or integrating with other data-enrichment services.
   
   Start building smarter automations today—because in business, every second counts.
   
   Links:
   
   - n8n: https://n8n.io
   - Icypeas: https://icypeas.com
   - Icypeas API Docs: https://app.icypeas.com/bo/profile
   - Google Cloud Console (for Sheets API): https://console.cloud.google.com
   
   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.