receive form events and emailverifier hunter and clearbit
Configured with Clearbit, Form Trigger, Hunter, Pipedrive. Review the connections and setup before adapting this template.
Node categories in this workflow
- Trigger
- Routing
- 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.
| Node | Category | Type | Operation |
|---|---|---|---|
| n8n Form Trigger | Trigger | Form Trigger | See node parameters |
| Check if the email is valid | Routing | If | See node parameters |
| Email is not valid, do nothing | Routing | No Op | See node parameters |
| Verify email with Hunter | Integration | Hunter | emailVerifier |
| Clearbit | Integration | Clearbit | person |
| Person already exists in Pipedrive, do nothing | Routing | No Op | See node parameters |
| Is this a new person? | Routing | If | See node parameters |
| Search for person in Pipedrive | Integration | Pipedrive | person / search |
| Is this a new organization? | Routing | If | See node parameters |
| Create Organization | Integration | Pipedrive | organization |
| Search for organization in Pipedrive | Integration | Pipedrive | organization / search |
| Create Person | Integration | Pipedrive | person |
| Create lead | Integration | Pipedrive | lead |
Setup
- Download the JSON and import it into an isolated n8n instance. Leave the workflow inactive.
- Connect your own credentials through n8n’s credential store. Replace
REPLACE_WITH_*values with your resource identifiers. - Inspect API destinations, Code nodes, database queries, file paths, and outbound actions.
- 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
clearbitApihunterApipipedriveApi
Workflow notes
👨🎤 Setup
👨🎤 Setup
- Add your Hunter.io, Clearbit and Pipedrive credentials
- Click the test workflow button
- 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...)
receive form events and emailverifier hunter and clearbit
receive form events and emailverifier hunter and clearbit
Purpose and structure
This folder contains the receive form events and emailverifier hunter and clearbit workflow. Its executable nodes use clearbit, formTrigger, hunter, if, noOp, pipedrive. 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/0436_Hunter_Pipedrive_Create_Triggered.json MIT; preserve source notices.