search person pipedrive and get person pipedrive and open ai
Configured with Gmail Trigger, Open Ai, Pipedrive. Review the connections and setup before adapting this template.
Node categories in this workflow
- Integration
- Routing
- AI & models
- Transform
- Code
- 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.
| Node | Category | Type | Operation |
|---|---|---|---|
| Search Person in CRM | Integration | Pipedrive | person / search |
| In campaign? | Routing | If | See node parameters |
| Get person from CRM | Integration | Pipedrive | person / get |
| Is interested? | AI & models | Open Ai | chat |
| Get email | Transform | Edit Fields | See node parameters |
| Create deal in CRM | Integration | Pipedrive | See node parameters |
| IF interested | Routing | If | See node parameters |
| Get response | Code | Code | See node parameters |
| Email box 1 | Trigger | Gmail Trigger | See node parameters |
| Email box 2 | Trigger | Gmail Trigger | See node parameters |
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
openAiApipipedriveApi
Workflow notes
About the workflow
About the workflow
The workflow reads every reply that is received from a cold email campaign and qualifies if the lead is interested in a meeting. If the lead is interested, a deal is made in pipedrive. You can add as many email inboxes as you need!
Setup:
- Add credentials to the Gmail, OpenAI and Pipedrive Nodes.
- Add a in_campaign field in Pipedrive for persons. In Pipedrive click on your credentials at the top right, go to company settings > Data fields > Person and click on add custom field. Single option [TRUE/FALSE].
- If you have only one email inbox, you can delete one of the Gmail nodes.
- If you have more than two email inboxes, you can duplicate a Gmail node as many times as you like. Just connect it to the Get email node, and you are good to go!
- In the Gmail inbox nodes, select Inbox under label names and uncheck Simplify.
search person pipedrive and get person pipedrive and open ai
search person pipedrive and get person pipedrive and open ai
Purpose and structure
This folder contains the search person pipedrive and get person pipedrive and open ai workflow. Its executable nodes use code, gmailTrigger, if, openAi, pipedrive, 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
Email box 1, Email box 2
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/Code/0379_Code_Pipedrive_Create_Triggered.json MIT; preserve source notices.