← All N8N workflows
Messaging & emailForm TriggerHTTP RequestHunterIfNo Op

slack and receive form events and score lead with madkudu

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

Workflow preview
MessagingSlackSlackTriggern8n 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 >60If

Node categories in this workflow

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

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
SlackMessagingSlackSee node parameters
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

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

  • httpHeaderAuth
  • hunterApi
  • slackApi

Workflow notes

👨‍🎤 Setup

👨‍🎤 Setup

  1. Add you MadKudu, Hunter, and Slack credentials
  2. Set the Slack channel
  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

slack and receive form events and score lead with madkudu

slack and receive form events and score lead with madkudu

Purpose and structure

This folder contains the slack and receive form events and score lead with madkudu workflow. Its executable nodes use formTrigger, httpRequest, hunter, if, noOp, slack. 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/Slack/0423_Slack_Hunter_Send_Webhook.json MIT; preserve source notices.

More in Messaging & email