n8n Tutorial: Website Form → Pipedrive Deal + Follow-up Task Automation

Your website form works. Someone fills it out, hits submit, and you get an email. Then what? For most teams, that email sits in an inbox while the lead cools. By the time a sales rep copies the details into Pipedrive, creates a deal, and remembers to schedule a follow-up call, an hour has passed — or a day. Studies on lead response consistently show that contacting a prospect within five minutes dramatically outperforms contacting them an hour later. Manual data entry guarantees you lose that window every single time.

This tutorial shows you how to wire a website form directly into Pipedrive using n8n, so every submission instantly becomes a deal with a follow-up call task assigned to the right rep — no copy-paste, no forgotten follow-ups, no cooling leads.

The Problem: Your CRM Is Only as Fast as Your Slowest Rep

The gap between "form submitted" and "deal in CRM" is where revenue leaks. There are three concrete failure modes technical founders and ops teams see over and over:

• Latency. A lead fills out your contact form at 9 PM. Nobody touches it until the next morning. That prospect has already booked a call with a competitor.
• Data loss. Manual entry drops fields. The phone number gets skipped, the message body never makes it into the deal notes, and the rep calls in blind.
• No accountability. A deal lands in the pipeline but nobody owns the next action. Without a scheduled activity, Pipedrive won't remind anyone, and the deal rots in "New."

You can throw discipline and Slack reminders at this, but discipline doesn't scale and reminders get muted. The durable fix is to remove the human from the data-entry loop entirely.

The Solution: One Webhook, Three Guaranteed Actions

The automation is deceptively simple. When your form is submitted, n8n receives the payload, creates a Pipedrive deal, and schedules a follow-up call activity — all in a single execution that finishes in seconds. Every submission produces the same three artifacts, every time, with zero drift:

1. A deal in the correct pipeline stage, carrying the lead's name, email, phone, and message.
2. A person (or matched existing contact) linked to that deal, so you never create orphan records.
3. A follow-up call activity due within a defined window (say, one hour) and assigned to an owner.

Because n8n sits between your form and Pipedrive, it also becomes the place to normalize messy input, enrich data, and route leads — without ever touching your website code again.

Step-by-Step: Building It in n8n

Here's the full build. The workflow uses four core nodes: a Webhook trigger, a Set node for shaping data, and two Pipedrive nodes.

1. Capture the form with a Webhook node

Add a Webhook node as the trigger. Set the HTTP method to POST and copy the generated Production URL. Point your form's action (or your form builder's webhook integration — Typeform, Tally, Webflow, plain HTML with fetch) at that URL. Submit a test entry so n8n captures a real payload; this lets you map the incoming fields by their actual names, like body.name, body.email, body.phone, and body.message.

2. Normalize the data with a Set node

Form payloads are inconsistent. Add a Set (Edit Fields) node right after the webhook to create clean, predictable fields the rest of the workflow depends on. Map:

• fullName → {{ $json.body.name }}
• email → {{ $json.body.email.toLowerCase().trim() }}
• phone → {{ $json.body.phone }}
• dealTitle → {{ "Website lead — " + $json.body.name }}
• notes → {{ $json.body.message }}

Doing this once here means every downstream node references stable field names instead of brittle raw paths.

3. Create the contact and deal with the Pipedrive node

Add a Pipedrive node and authenticate with your API token (Pipedrive → Settings → Personal preferences → API). Set Resource to Deal and Operation to Create. Configure:

• Title → {{ $json.dealTitle }}
• Stage ID → the numeric ID of your intake stage (find it in the Pipedrive UI or via the Get Many Stages operation).
• Under Additional Fields, map the person's name, email, and phone. The Pipedrive node can create the associated person automatically, or you can add a separate Pipedrive → Person → Create node upstream and pass its returned id into the deal's person_id field for tighter control over deduplication.

The node returns the new deal's id — capture it, because the next step needs it.

4. Schedule the follow-up call activity

Add a second Pipedrive node. Set Resource to Activity and Operation to Create. Configure:

• Subject → Call new website lead: {{ $json.fullName }}
• Type → call
• Deal ID → {{ $json.id }} from the previous node, so the activity links to the deal.
• Due date and Due time → use an expression to set it soon, e.g. {{ $now.plus({ hours: 1 }).toFormat('yyyy-MM-dd') }} for the date and a matching time field.
• User ID (assigned to) → the rep who owns inbound. For round-robin, feed this from a small Code node that rotates through a list of user IDs.

Save, toggle the workflow to Active, and submit one more real form entry. You should see a deal appear in your intake stage with a call activity due within the hour. That's the entire loop.

Why This Pays Off Immediately

The benefits compound the moment you flip it on:

• Speed to lead. Response time drops from hours to seconds. The follow-up task exists before the prospect has closed your tab.
• Zero data loss. Every field the form collects lands in the deal notes. Reps call with full context instead of "Hi, I saw you filled out a form."
• Enforced accountability. No deal enters the pipeline without an owner and a due activity. Pipedrive's own reminders now do the nagging for you.
• A clean audit trail. n8n logs every execution, so when a lead swears they submitted the form, you can prove exactly what happened and when.
• It scales for free. Ten submissions or ten thousand — the workflow doesn't get tired, distracted, or take a vacation.

Common Pitfalls (and How to Avoid Them)

A few things trip up first-time builders. Handle these up front and the automation runs untouched for months:

• Hardcoding the wrong stage or user ID. Pipedrive uses numeric IDs, not names. Pull the real IDs via the node's Get Many operations rather than guessing — a wrong ID silently files deals into the wrong pipeline.
• No duplicate handling. If the same person submits twice, you'll create two deals. Add a Pipedrive → Search Persons node before creation and branch with an IF node: update the existing person if found, create if not.
• Ignoring failures. If Pipedrive's API times out, the deal never gets created and you'd never know. Add an Error Trigger workflow that pings Slack or email so a silent failure doesn't become a lost lead.
• Skipping spam defense. Public forms attract bots. Add an IF node that validates the email format and drops submissions with empty or obviously fake fields before they reach Pipedrive.
• Testing only with the Test URL. The Webhook node has separate test and production URLs. After activating, confirm your form points at the production URL, or live submissions will vanish.

Build it once, test it with a handful of real submissions, and this becomes infrastructure you stop thinking about — while it quietly makes sure no lead ever waits again.

PRONTO PARA USAR

Ja construimos isso pra voce

Nao comece do zero. O Website Form → Pipedrive Deal + Follow-up Task e um workflow n8n pronto para instalar — conecta suas ferramentas em minutos, sem codigo.

Instalar por $29 →