Website-to-CRM Integration

At a Glance

Formspree Forms

All contact and inquiry forms on the site submit to a single Formspree endpoint (formspree.io/f/xvzbywbr). Formspree stores the submission, fires an email notification, and triggers a webhook to a Netlify Function that creates the appropriate Pipedrive record.

Every form automatically includes hidden UTM fields (injected by ds-includes-v2.js from sessionStorage) and a hidden source field identifying the page — so every submission is traceable back to its origin.

Form → Pipedrive Flow

Complete Form Inventory

Pages with Scheduler Only (No Form)

Note: /start/ is the only page with both a Formspree form and a Pipedrive Scheduler link.

Pipedrive Scheduler

Replaced Calendly in March 2026. The Scheduler creates meetings natively in Pipedrive, eliminating a third-party middleware layer. Because booking happens on Pipedrive's domain (not ours), campaign attribution and contact details can't be captured in a single request — so the integration runs in two phases.

All scheduler links point to: digitalscientists3.pipedrive.com/scheduler/kOOeAEu2/meeting-with-bob-klein

Phase 1 — Pre-Booking (on our site, before redirect)

Phase 2 — Post-Booking (after prospect completes the form)

UTM Attribution — How It Works Across Both Systems

The same UTM capture mechanism feeds both Formspree and the Scheduler. When a visitor arrives via a campaign link, ds-includes-v2.js stores the UTM values in sessionStorage — persisting across page navigations within the same session. At conversion (form submit or scheduler click), UTMs are passed to the Netlify Function.

Pipedrive Custom Field API Keys (Deal)

End-to-End Examples

Google Calendar Integration

Pipedrive's native two-way calendar sync connects Scheduler bookings to Bob's Google Calendar. Pipedrive is the single source of truth — no duplicate events (the old Calendly setup could write directly to Google Calendar and create doubles).

Configured in Pipedrive → Settings → Calendar Sync → Google Calendar. "Meeting" activity type must be enabled for sync.

Technical Reference

Netlify Functions

External Service Connections

Pipedrive Configuration

Resilience & Failure Modes

Pipedrive Reporting

With UTM fields on Deals, Pipedrive's built-in reporting can answer:

Webhook Payload Reference (Pipedrive v2.0)

Sent to scheduler-webhook.mjs on activity.create. The webhook uses person_id and org_id to link the Deal. Booking form text (name, phone, company, agenda) is not in this payload — the handler fetches it via a separate call to GET /activities/{id}.

{
  "data": {
    "id": 12345,
    "type": "meeting",
    "subject": "Jane Smith / Bob Klein - Meeting with Bob Klein",
    "person_id": 20348,
    "org_id": 13528,
    "due_date": "2026-03-25",
    "due_time": { "value": "10:00:00" }
  },
  "previous": null,
  "meta": {
    "action": "create",
    "entity": "activity",
    "version": "2.0"
  }
}