This article provides a complete, practical walkthrough of the Manual Http Send 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 Single Email Lookup with Icypeas API Using n8n
   
   Meta Description:
   Learn how to automate a single email search using the Icypeas API with n8n. This guide walks you through authenticating with Icypeas, building a secure HTTP request, and retrieving results dynamically.
   
   Keywords:
   n8n automation, Icypeas email search, n8n workflow tutorial, email lookup API, Icypeas API integration, n8n HTTP request, API authentication, domain search automation, email finder workflow, no-code automation
   
   Third-party APIs Used:
   
   - Icypeas API (https://app.icypeas.com/api/domain-search)
   
   Article:
   
   Automating Single Email Lookup with Icypeas API Using n8n
   
   In today’s fast-moving digital landscape, automation of tasks like email searches helps maximize efficiency and streamline data-gathering efforts. This article introduces an n8n workflow designed to perform an email lookup using the Icypeas platform's single search capability. If you’re in sales, recruitment, or marketing, this can be an invaluable tool in your toolkit.
   
   What is n8n?
   
   n8n is a powerful, open-source workflow automation tool that enables you to connect various apps and services via low-code or no-code configurations. It provides a flexible and scalable environment for automating repetitive tasks, making it especially useful for developers and non-technical users alike.
   
   What is Icypeas?
   
   Icypeas is an email discovery and enrichment platform used to find professional email addresses based on a person’s name and company. With its API, users can perform domain or single email searches programmatically.
   
   In this tutorial, you’ll learn how to:
   
   - Set up a manual n8n trigger to control execution
   - Authenticate to Icypeas’ API securely
   - Construct and execute a POST request to search for a professional email address
   - Understand the structure so you can adapt it for your own use
   
   Step-by-Step Breakdown of the Workflow
   
   1. Manual Trigger Initialization
   
   The workflow begins with a Manual Trigger node. This node allows you to execute the workflow manually from the n8n UI for testing and experimentation. It's perfect for workflows that you want to run on-demand.
   
   2. Authentication with Icypeas API
   
   The next step involves authenticating with the Icypeas API using a Code node. You must provide your API Key, API Secret, and User ID, all of which can be obtained from your Icypeas account at https://app.icypeas.com/bo/profile.
   
   Replace the placeholders in the provided code with your actual credentials:
   
   const API_KEY = "PUT_API_KEY_HERE";
   const API_SECRET = "PUT_API_SECRET_HERE";
   const USER_ID = "PUT_USER_ID_HERE";
   
   The authentication process generates a timestamp and signature using HMAC SHA1 encryption via the crypto module. This is particularly important for secure, authenticated API requests.
   
   Note for Self-hosted Users:
   If you're running n8n on your server, make sure the crypto module is enabled in Settings -> General -> Additional Node Packages.
   
   3. Configuring the HTTP Request to Icypeas
   
   This is where the actual email lookup happens. The data collected from the previous step is utilized in an HTTP Request node. The request is a POST method sent to:
   
   https://app.icypeas.com/api/domain-search
   
   The headers include:
   
   - X-ROCK-TIMESTAMP: A timestamp generated during authentication
   - Authorization: A dynamically created string using API key and generated signature in the format: API_KEY:signature
   
   The body parameters required are:
   
   - firstname: First name of the individual (e.g., Pierre)
   - lastname: Last name of the individual (e.g., Landoin)
   - domainOrCompany: Domain or company the individual works for (e.g., icypeas)
   
   You can find these parameters in the Body Parameters section of the HTTP Request configuration. Once executed, the Icypeas API returns the associated professional email address if found.
   
   4. Testing the Workflow
   
   With authentication properly set and the request parameters filled in, you can now click “Execute Workflow” in the n8n UI. The request is processed instantly, and if successful, you’ll receive the identified email address as part of the response.
   
   Where to See Results
   
   You can view the request's outcome by going to your Icypeas dashboard:
   https://app.icypeas.com/bo/singlesearch?task=email-search
   
   Conclusion
   
   This n8n workflow showcases how easily you can integrate external APIs like Icypeas into automation pipelines. By using secure authentication and precise API requests, tasks like email lookups become seamless and fast. Once set up, it’s easy to adapt this workflow to run on schedules, triggers from other applications, or even bulk queries using spreadsheets and databases.
   
   With tools like n8n and Icypeas, you're empowered to transform manual data chasing into efficient, reliable automation.
   
   Final Tips:
   
   - Always keep your API credentials secure; avoid hardcoding them in shared environments.
   - Use environment variables or n8n credential managers for better security.
   - Consider using a Loop or SplitInBatches node for bulk searches using a list of names.
   
   With this setup, you're now ready to dive into scalable, automated email discovery!

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.