Add a new lead to Pipedrive once GitHub repo is forked
Ready for 3.0Ready for 3.0. This template uses no nodes that n8n 3.0 removes. No removed nodes, versions or helpers found. Static check, last run 2026-10-19.
What this workflow does
This workflow has 8 nodes and runs on Github events (fork). Along the way it connects Pipedrive and GitHub.
How it runs
Trigger: On Github events (fork).
- Get Github user information (HTTP Request): calls an HTTP API
- Search forkee in Pipedrive by email (Pipedrive): search (person)
- person exists (If): checks a condition and branches into true / false
- Set person Id (Edit Fields (Set)): sets or maps fields
- Create person (Pipedrive): work with person
- Create lead (Pipedrive): work with lead
- Create note with github url (Pipedrive): work with note
Services it uses
Before you upgrade to n8n 3.0
Nothing in this workflow is removed in n8n 3.0, so it should import and run after the upgrade.
Nodes used (5)
- If
n8n-nodes-base.if - Edit Fields (Set)
n8n-nodes-base.set - Pipedrive
n8n-nodes-base.pipedrive - Github Trigger
n8n-nodes-base.githubTrigger - HTTP Request
n8n-nodes-base.httpRequest
From the author
This workflow automatically adds a new lead to Pipedrive once someone forks your GitHub repository. Prerequisites - Pipedrive account and Pipedrive credentials - GitHub account and GitHub credentials How it works 1. GitHub Trigger node starts the workflow…