http request and filter leads by company criteria and clearbit
Configured with Clearbit, Filter, Google Sheets, HTTP Request, and additional nodes. Review the connections and setup before adapting this template.
Node categories in this workflow
- Web / API
- Routing
- Integration
- Transform
- Trigger
- Data store
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 |
|---|---|---|---|
| Get Leads | Web / API | HTTP Request | See node parameters |
| Filter Leads by company criteria | Routing | Filter | See node parameters |
| Enrich company | Integration | Clearbit | See node parameters |
| Setup | Transform | Edit Fields | See node parameters |
| Get all Leedfeeder accounts | Web / API | HTTP Request | See node parameters |
| Only for wanted accounts | Routing | Filter | See node parameters |
| Split out accounts | Transform | Split Out | See node parameters |
| Split Out Leads | Transform | Split Out | See node parameters |
| Schedule Trigger | Trigger | Schedule Trigger | See node parameters |
| Filter leads by engagement | Routing | Filter | See node parameters |
| Save leads to Google Sheets | Data store | Google Sheets | appendOrUpdate |
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
clearbitApigoogleSheetsOAuth2ApihttpHeaderAuth
Workflow notes
Setup
Setup
- Add your Leedfeeder credentials. The name should be
Authorizationand the valueToken token=yourapitoken. You can find your token via Settings -> Personal -> API-Token - Add your Google Sheet credentials
- Save the Leedfeeder account names you want to use in the
Setupnode - Copy the Google Sheets Template and add its URL to the
Setupnode
Sticky Note1
Adjust your engagement criteria here
Sticky Note2
Adjust your company criteria here
Sticky Note3
Adjust the schedule here
http request and filter leads by company criteria and clearbit
http request and filter leads by company criteria and clearbit
Purpose and structure
This folder contains the http request and filter leads by company criteria and clearbit workflow. Its executable nodes use clearbit, filter, googleSheets, httpRequest, scheduleTrigger, set, splitOut. 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
Schedule 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/Splitout/0418_Splitout_Filter_Export_Scheduled.json MIT; preserve source notices.