Icypeas Single Email Search Integration - n8n Workflow

• Lead generation specialists needing automated email verification.


• Sales professionals looking to integrate Icypeas into their CRM pipelines.


• n8n users requiring examples of advanced API authentication using the Code n8n node.


• Automation engineers looking for robust n8n templates for custom integrations.

This powerful n8n workflow provides a robust solution for lead generation specialists and recruiters who need to verify or find professional email addresses using the Icypeas service. Unlike standard integrations, this specific n8n workflow handles complex HMAC signature authentication entirely within a custom n8n node, ensuring secure and seamless communication with the Icypeas API. This detailed structure serves as an excellent reference among n8n templates for advanced API integration challenges, streamlining a critical business process into a repeatable n8n workflow execution. By using a specialized n8n node for authentication, the workflow ensures security compliance while automating contact data extraction.

The n8n workflow initiates manually via the 'When clicking "Execute Workflow"' n8n trigger.

1. Authentication Preparation: The 'Authenticates to your Icypeas account' n8n node uses custom JavaScript code and the crypto module to generate an HMAC signature based on the API Key, Secret, User ID, path, and method. This custom code is critical for adhering to Icypeas's security protocol and demonstrates advanced use cases within an n8n workflow. The output of this n8n node includes the required timestamp and signature.


2. API Request: The 'Run email search (single)' n8n node (an HTTP Request n8n node) leverages the dynamically created signature and timestamp, injecting them into the headers for authorization.


3. Search Execution: The HTTP Request n8n node sends a POST request to the Icypeas API endpoint, including the target individual's firstname, lastname, and domainOrCompany as body parameters.


4. Result Delivery: The n8n workflow returns the search result, which can then be processed by subsequent n8n nodes for tasks like CRM updating or notification.

1. Import the n8n workflow: Copy the provided JSON code and import it into your n8n instance via the 'New' menu > 'Import from JSON'.


2. Configure Icypeas Credentials (Code n8n node): Open the 'Authenticates to your Icypeas account' n8n node. Replace the placeholders (PUTAPIKEY_HERE, etc.) with your actual Icypeas credentials, available from your profile on the Icypeas website.


3. Enable Crypto Module (Self-Hosted Users): If you are using a self-hosted n8n instance, ensure the crypto module is enabled in your n8n settings, as specified in the sticky note of the n8n workflow.


4. Configure HTTP Request Credentials: Open the 'Run email search (single)' n8n node. A generic credential named 'Authorization' must be created within the Header Auth section. Set the Value expression to {{ $json.api.key + ':' + $json.api.signature }}.


5. Set Search Parameters: In the 'Run email search (single)' n8n node, update the Body Parameters (lastname, firstname, domainOrCompany) with the data you wish to search for. This completes the setup for this n8n workflow.

When clicking "Execute Workflow" (Manual n8n Trigger):
Function: Starts the entire n8n workflow execution manually, ideal for testing or ad-hoc searches.
Key Configuration: Standard manual n8n trigger setup.
Authenticates to your Icypeas account (Code n8n node):
Function: Generates the necessary timestamp, base URL, and cryptographic HMAC signature required for secure authentication with the Icypeas API. This specialized n8n node logic transforms user inputs into security headers.
Key Configuration: Requires hardcoding the APIKEY, APISECRET, and USER_ID within the JavaScript code.
Run email search (single) (HTTP Request n8n node):
Function: Sends the authenticated POST request to the Icypeas API to retrieve a single email address based on the provided name and domain/company.
* Key Configuration: Authentication is set to 'HTTP Header Auth', using expressions ({{ $json.api.timestamp }} and the configured 'Authorization' header) derived from the preceding Code n8n node. Body parameters define the search criteria (lastname, firstname, domainOrCompany).