Turn GitHub repo forks into sales leads without manual data entry. Great for developer focused teams that want to track interest from open source activity inside a CRM and follow up faster.

When someone forks your repository, the flow starts from a GitHub event. It then calls the GitHub API to get the user profile and email. Next it searches Pipedrive for a matching person by email. If a person is found, their record is used. If not, a new person is created with the GitHub username and email. The workflow then creates a lead linked to that person with a clear title that includes the repo name and the forker. Finally, it adds a note to the lead with the GitHub profile link for quick context. This keeps your pipeline clean by avoiding duplicates and adds helpful links for outreach.

You will need GitHub and Pipedrive accounts and credentials in n8n. Set the owner and repository in the GitHub trigger and make sure the webhook is active. Expect faster follow up and clearer tracking of developer intent. This is useful for dev tool startups, product led growth teams, and agencies that run public repos and want to capture real interest in Pipedrive.

• On app event trigger starts when a repository is forked in GitHub.
• HTTP request fetches the forker profile and email from the GitHub API.
• Pipedrive search finds existing people by email to prevent duplicates.
• If node checks if a person record exists and routes the flow accordingly.
• Create person in Pipedrive when no match is found, using GitHub username and email.
• Set node stores the Pipedrive person id for use in later steps.
• Create lead in Pipedrive and add a note with the GitHub profile link for quick context.

• Reduce manual work from 15 minutes per fork to under 1 minute
• Automate up to 90 percent of lead entry from GitHub forks
• Improve data quality by linking each lead to the GitHub profile
• Connect GitHub and Pipedrive so sales sees developer intent in one place
• Handle hundreds of forks without adding extra workload

1. Import the template into n8n: Create a new workflow in n8n > Click the three dots menu > Select 'Import from File' > Choose the downloaded JSON file.
2. You'll need accounts with GitHub and Pipedrive. See the Tools Required section above for links to create accounts with these services.
3. In the n8n credentials manager, create a GitHub credential. If unsure, double click the GitHub Trigger node, open the Credential to connect with menu, click Create new credential, and follow the on screen steps.
4. Open the GitHub Trigger node and set the repository owner and repository name you want to watch for forks.
5. Confirm the webhook is created in your GitHub repository settings under Webhooks. If it is not present, click Execute Node in n8n to register it, or add the webhook URL shown in the node to GitHub manually.
6. In the n8n credentials manager, create a Pipedrive credential. Double click any Pipedrive node, choose Create new credential, and follow the on screen steps to connect your Pipedrive account.
7. Open the HTTP Request node and make sure it uses your GitHub credential. The URL field should read the sender URL from the GitHub event payload.
8. Open the Pipedrive Search node and verify Fields is set to email and the Term uses the email from the GitHub user data.
9. Check the If node condition to confirm it looks for a non empty name on the search result. This is used to decide if a person exists.
10. Review the Create Person node to ensure the name uses the GitHub login and the email maps from the GitHub API response.
11. Verify the Set node stores the Pipedrive person id and the Create Lead node uses that id and a clear title that includes the repository name and the forker.
12. Open the Create Note node and confirm it attaches the GitHub profile link to the new lead so your team has quick context.
13. Test end to end by forking the watched repository from a separate GitHub account. Check Pipedrive for the new or updated person, the new lead, and the note.
14. If no lead appears, check the GitHub webhook delivery logs for errors and confirm the n8n instance is reachable from the internet.
15. If email is missing on the GitHub profile, the search may not find a person. Consider adding a fallback rule or a manual review queue if your team needs it.