← All N8N workflows
Automation & utilitiesHTTP RequestIfItem ListsMergePipedrive

Find a different ideal buyer:

Configured with HTTP Request, Item Lists, Pipedrive, Pipedrive Trigger. Review the connections and setup before adapting this template.

Workflow preview
Transformlist peopleItem ListsIntegrationPipedrive - EnrichOrganizationPipedriveIntegrationPipedrive - Add PersonPipedriveWeb / APIDatagma - EnrichCompanyHTTP RequestTransformMergeMergeRoutingIf lead is Ideal BuyerIfWeb / APIDatagma - Find EmailsHTTP RequestTransformPrepare Data BeforeMergeEdit FieldsTriggerPipedrive Trigger - NewCompany CreatedPipedrive Trigger

Node categories in this workflow

  • Transform
  • Integration
  • Web / API
  • Routing
  • Trigger

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
list peopleTransformItem ListsSee node parameters
Pipedrive - Enrich OrganizationIntegrationPipedriveorganization / update
Pipedrive - Add PersonIntegrationPipedriveperson
Datagma - Enrich CompanyWeb / APIHTTP RequestSee node parameters
MergeTransformMergeSee node parameters
If lead is Ideal BuyerRoutingIfSee node parameters
Datagma - Find EmailsWeb / APIHTTP RequestSee node parameters
Prepare Data Before MergeTransformEdit FieldsSee node parameters
Pipedrive Trigger - New Company CreatedTriggerPipedrive TriggerSee 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

  • httpQueryAuth
  • pipedriveApi

Workflow notes

Find a different ideal buyer:

Find a different ideal buyer:

In "Datagma - Enrich Company" node - change "employeeTitle" value with the keywords of your ideal buyer (-> Head of Marketing)

Refine lead results

Refine lead results

Here I am refining lead results to make sure they match my search. If you have a different ICP, make sure to change the first value.

Find a different ideal buyer:

Find a different ideal buyer:

Purpose and structure

This folder contains the Find a different ideal buyer: workflow. Its executable nodes use httpRequest, if, itemLists, merge, pipedrive, pipedriveTrigger, set. 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

Pipedrive Trigger - New Company Created

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/Pipedrive/0249_Pipedrive_Stickynote_Create_Webhook.json MIT; preserve source notices.

More in Automation & utilities