FM
FlowMarket
DevOps & GitHub Intermediate ⚡ 8 n8n Nodes

Add a new lead to Pipedrive once GitHub repo is forked

This workflow automatically adds a new lead to Pipedrive once someone forks your GitHub repository. Prerequisites - Pipedrive account and Pipedrive credentia...

🔌 Nodes & Integrations Used (3)

Pipedrive Github Trigger HTTP Request

📖 Implementation & Setup Guide

This workflow automatically adds a new lead to Pipedrive once someone forks your GitHub repository.

Prerequisites - Pipedrive account and [Pipedrive credentials](https://docs.n8n.io/integrations/builtin/credentials/pipedrive/) - GitHub account and [GitHub credentials](https://docs.n8n.io/integrations/builtin/credentials/github/)

How it works 1. GitHub Trigger node starts the workflow once someone forks your GitHub repository. 2. HTTP Request node gets user's data from GitHub and sends it further. 3. Pipedrive node searches forkee's data in Pipedrive by email. 4. IF node decides whether to create a new person in Pipedrive in case contact doesn't exist yet or update an existing contact in Pipedrive. 5. In case there's no contact existing yet, the Pipedrive node creates a lead and adds a note with GitHub URL.

⚡ How to import this workflow into n8n:

  1. Click the Direct Download JSON button above to save Add a new lead to Pipedrive once GitHub repo is forked.json.
  2. Log in to your n8n Cloud or self-hosted n8n instance.
  3. In your workflow canvas, click the menu in top-right and select Import from File (or paste the JSON directly).
  4. Configure your credentials (e.g. API keys, database URLs) in the corresponding node settings.
  5. Click Execute Workflow to test and switch to Active!

Related DevOps & GitHub Workflows

View All in DevOps & GitHub →