Automatic Pipedrive Lead Generation from GitHub Fork Events - n8n Workflow

• DevOps teams who want to track community engagement as potential leads.


• Sales Operations specialists needing automated lead pipeline feeding.


• Technical founders monitoring open-source project adoption.


• Users looking for advanced integration examples using the Pipedrive n8n node and GitHub n8n trigger.

Bridging the gap between technical community engagement and sales pipeline management is crucial for growing open-source or commercial projects. This n8n automation provides a sophisticated way to manage that connection. Whenever a user forks a specified repository on GitHub, this n8n workflow instantly springs into action. It retrieves the user's detailed information, checks Pipedrive to see if the contact already exists, and either creates a new contact or uses the existing one. Finally, it creates a new lead associated with that contact, along with a contextual note detailing the GitHub URL. This robust n8n node configuration ensures sales teams have immediate, actionable intelligence based on technical interest, providing significant value compared to manual tracking.

This structured n8n workflow operates through several conditional and data transformation steps:

1. GitHub n8n trigger: The workflow starts with the "On fork" GitHub Trigger n8n node, which is configured as a webhook listener for fork events on a designated repository.


2. User Data Retrieval: The flow immediately hits the "Get Github user information" HTTP Request n8n node. This node uses the sender's URL from the webhook payload to fetch the full user profile data, including their email address.


3. Pipedrive Search: The "Search forkee in Pipedrive by email" Pipedrive n8n node attempts to find an existing person record in Pipedrive using the retrieved email.


4. Conditional Check: The "person exists" If n8n node checks the output of the search. If a person is found (meaning the name field is present), the flow follows the True path; otherwise, it follows the False path.


5. CRM Update/Creation:

1. Lead Creation: The "Create lead" Pipedrive n8n node uses the collected Person ID to create a new lead entry, dynamically naming it after the forked repository and the user.


2. Contextual Note: The final step, using the "Create note with github url" Pipedrive n8n node, attaches a note to the new lead, providing the direct link to the GitHub user's profile for quick access by the sales team.

To deploy this powerful n8n workflow, follow these steps:

1. Import: Copy the provided JSON and paste it into your n8n canvas via the 'New -> Import from JSON' option.


2. Credentials: You will need to configure two sets of credentials:

1. GitHub Trigger Setup: Open the "On fork" n8n trigger node. Ensure the 'Owner' and 'Repository' parameters match the specific repo you wish to monitor. Activate the workflow to generate the webhook URL.


2. GitHub Webhook Configuration: Copy the generated webhook URL from the "On fork" n8n node and register it in your GitHub repository settings under 'Webhooks'. Make sure the trigger event is set to 'Forks'.


3. Activation: Save the n8n workflow and set it to active.

On fork (GitHub Trigger n8n trigger):
Function: Serves as the starting point, listening for webhook payloads whenever the specified GitHub repository is forked.
Key Configuration: Events set to fork, targeting a specific owner and repository.
Get Github user information (HTTP Request n8n node):
Function: Fetches detailed public user information (crucially, the email address) using the user URL provided in the trigger payload.
Key Configuration: Uses predefined GitHub credentials for authenticated API access.
Search forkee in Pipedrive by email (Pipedrive n8n node):
Function: Attempts to locate an existing Pipedrive Person record using the GitHub user's email address.
Key Configuration: Resource: person, Operation: search, Term: {{ $json["email"]}}.
person exists (If n8n node):
Function: Controls the flow based on whether the Pipedrive search found a matching person, determining if a new contact must be created.
Key Configuration: Condition: value1 (Person Name) isNotEmpty.
Create person (Pipedrive n8n node):
Function: Creates a new Pipedrive Person record if no existing contact was found. This ensures every unique forker becomes a tracked prospect.
Set person Id (Set n8n node):
Function: Standardizes the Pipedrive Person ID (whether retrieved from the search or newly created) into the PipedrivePersonId variable for subsequent nodes.
Create lead (Pipedrive n8n node):
Function: Creates the core lead object in Pipedrive, linking it to the associated contact.
Key Configuration: Title is dynamically generated to include the repository and the user name, Resource: lead, Association: person via PipedrivePersonId.
Create note with github url (Pipedrive n8n node):
* Function: Attaches a supporting note to the newly created lead, providing the direct URL to the GitHub profile for context.