Add Pipedrive Lead on GitHub Repo Fork

This n8n workflow triggers on GitHub repository forks, fetching the forker's user data via HTTP request, then checks if they exist in Pipedrive by email. If not found, it creates a new person, generates a lead associated with that person, and adds a note with the repo URL. If existing, it updates the contact accordingly.

Benefits include effortless lead generation from GitHub activity, saving manual tracking time for developers and marketers. It turns passive repo interactions into actionable CRM data, ideal for open-source projects, SaaS promotions, or developer outreach.

Use cases: Promote a travel app repo where forks signal itinerary planning interest; track hospitality tool adopters; or build sales pipelines from dev community engagement. Prerequisites: GitHub and Pipedrive credentials. Scalable for multiple repos with minor tweaks.