← All N8N workflows
Messaging & emailForm TriggerGmailHTTP RequestHunterIf

receive form events and score lead with madkudu and emailverifier hunter

Configured with Form Trigger, Gmail, HTTP Request, Hunter. Review the connections and setup before adapting this template.

Workflow preview
Triggern8n Form TriggerForm TriggerRoutingCheck if the email isvalidIfRoutingEmail is not valid, donothingNo OpWeb / APIScore lead with MadKuduHTTP RequestIntegrationVerify email withHunterHunterRoutingNot interesting enoughNo OpRoutingif customer fit score >60IfMessagingGmailGmail

Node categories in this workflow

  • Trigger
  • Routing
  • Web / API
  • Integration
  • Messaging

Icons describe general node roles, inferred from node types. Inspect the parameters for the configured action.

Drag to pan; use + and − to zoom. Reconstructed from the exported node positions; nothing runs here. Dashed lines represent non-main connections. Full node names and notes appear below.

How it works

The exported workflow contains the following configured nodes. Their connections are shown above; inspect the JSON for the complete logic, expressions, and external actions.

Workflow node names, types, and operations
NodeCategoryTypeOperation
n8n Form TriggerTriggerForm TriggerSee node parameters
Check if the email is validRoutingIfSee node parameters
Email is not valid, do nothingRoutingNo OpSee node parameters
Score lead with MadKuduWeb / APIHTTP RequestSee node parameters
Verify email with HunterIntegrationHunteremailVerifier
Not interesting enoughRoutingNo OpSee node parameters
if customer fit score > 60RoutingIfSee node parameters
GmailMessagingGmailSee node parameters

Setup

  1. Download the JSON and import it into an isolated n8n instance. Leave the workflow inactive.
  2. Connect your own credentials through n8n’s credential store. Replace REPLACE_WITH_* values with your resource identifiers.
  3. Inspect API destinations, Code nodes, database queries, file paths, and outbound actions.
  4. Run with synthetic data and harmless destinations. Enable triggers only after checking the actual outputs.

Requirements

An n8n instance with the listed node types and compatible versions. Service-connected workflows may require accounts, credentials, or paid APIs.

Credential types declared in the source

  • gmailOAuth2
  • httpHeaderAuth
  • hunterApi

Workflow notes

👨‍🎤 Setup

👨‍🎤 Setup

  1. Add you MadKudu, Hunter, and Email credentials
  2. Set the email where you want the alert
  3. Click the Test Workflow button, enter your email and check the Slack channel
  4. Activate the workflow and use the form trigger production URL to collect your leads in a smart way
Sticky Note1

👆 You can exchange this with any form you like (e.g. Typeform, Google forms, Survey Monkey...)

Sticky Note2

👆 Adjust the fit as you see necessary

Sticky Note3

👇🏽 Update the email to send to

receive form events and score lead with madkudu and emailverifier hunter

receive form events and score lead with madkudu and emailverifier hunter

Purpose and structure

This folder contains the receive form events and score lead with madkudu and emailverifier hunter workflow. Its executable nodes use formTrigger, gmail, httpRequest, hunter, if, noOp. The table and connection map below are derived from the JSON, not an inferred guarantee of behavior.

Setup

Import inactive. Configure your own credentials and replace REPLACE_WITH_* values. Review external destinations and Code nodes before running.

Entry points

n8n Form Trigger

Verification

Sanitized source candidate; not runtime-tested. This overview is generated from node metadata. Read the folder README for the connection map, credential types, and license.

Attribution

https://github.com/Zie619/n8n-workflows/blob/94007c1445d9258a7da116646b79473e7c7c3282/workflows/Hunter/0424_Hunter_Form_Send_Webhook.json MIT; preserve source notices.

More in Messaging & email