Upload leads from a CSV file to Pipedrive CRM

Watches a Google Drive folder for new CSV files and adds only the new contacts to Pipedrive, skipping duplicates.

How the work actually flows

It branches. Exactly one path is taken; runs once per one per contact in file.

Pattern: Multiple Instances without Synchronization (12) · Exclusive Choice (4)

flowchart TD trig>"new csv file uploaded"]:::trig s0["download csv file"]:::task s1[["read contact rows"]]:::mi s2["check for duplicate"]:::task trig --> s0 s0 -->|"one per one per contact in file"| s1 s1 --> s2 gx{"× contact already exists"}:::gate s2 --> gx p00["skip contact"]:::task gx -->|"duplicate found"| p00 p10["create pipedrive contact"]:::task gx -->|"new contact"| p10 p00 --> out p10 --> out out[/"new contacts added, duplicates skipped"/]:::out pay{{"clean crm without manual list cleanup"}}:::pay out --> pay classDef task fill:#e7f6fe,stroke:#34b8f0,color:#2c2a29 classDef svc fill:#f6f8fa,stroke:#7c8795,color:#2c2a29 classDef mi fill:#e7f6fe,stroke:#0079a8,color:#2c2a29,stroke-width:2px classDef human fill:#fff,stroke:#0079a8,color:#0079a8 classDef store fill:#f6f8fa,stroke:#0079a8,color:#2c2a29 classDef trig fill:#00a4eb,stroke:#0079a8,color:#fff,font-weight:bold classDef trigtime fill:#00a4eb,stroke:#0079a8,color:#fff,font-weight:bold classDef trigdata fill:#8ad4f5,stroke:#0079a8,color:#06314c,font-weight:bold classDef gate fill:#fff,stroke:#e8a23d,color:#6b4708,font-weight:bold classDef out fill:#1f9d6b,stroke:#167a53,color:#fff,font-weight:bold classDef pay fill:#06314c,stroke:#021f33,color:#fff

Starts itA stepRuns once per itemOne path onlyResultPayoff

Build size

Advanced

A larger build with multiple systems, AI reasoning, and custom rules.

Business functions

CRM & Sales PipelineFile & Cloud Storage

Connects

Google DrivePipedrive

Featured in

Nonprofits

The problem it solves

Every time you get a new list of leads, someone has to open the CSV, check it against what's already in Pipedrive, and manually add the new ones. It's tedious and easy to create duplicate records or miss people entirely. That manual cleanup takes time away from actually working the leads.

Who it fits

Sales teams and small businesses that regularly import lead lists into Pipedrive.

How it works

Triggers when a new CSV file is uploaded to a designated Google Drive folder
Downloads and reads the contact data from the file
Checks each contact against existing Pipedrive records by email
Filters out anyone who's already in the system
Creates new Pipedrive contacts for everyone else, with organization and notes included

Quick estimate

What it is worth to you

Your numbers, your hourly cost. We add nothing hidden.

Lead list (CSV) files uploaded per week

per week

Average leads per file

leads

Minutes to check each lead against Pipedrive and add it

minutes

Loaded hourly cost

$ per hour

0Hours freed per month

0Value per year at your hourly cost

Assumes freed hours are put to other work and that today's manual checking and entry takes this long per lead.

What you get

New Pipedrive contact records for every lead in the uploaded file, with duplicates automatically skipped.

What you need

A Google account and a Pipedrive account.

We can build this. But should you?

The hard question is not how to build it. It is whether this is the right thing to build first.

That is what a Fractional Chief AI Officer figures out with you, before anyone writes a line of code.

Let's Talk Strategy

Related automations

Back to the AI Playbook