Pipedrive Email to Webhook Integration

Why Connect Pipedrive to Inbound Email

Pipedrive is built to manage customer relationships, but leads and inquiries often arrive via email before they ever reach your CRM. Manually copying email data into Pipedrive is time-consuming and error-prone. JsonHook automates this handoff by converting every inbound email into a structured JSON payload and posting it directly to Pipedrive's webhook endpoint.

Connecting your inbound email to Pipedrive through JsonHook unlocks a range of high-value automation scenarios:

• Create a new contact record automatically from every inbound inquiry email
• Update deal stages when a prospect replies to a proposal
• Log every customer email as an activity on the correct contact timeline
• Assign leads to sales reps based on keywords in the email body
• Trigger follow-up tasks when a client email includes words like "interested" or "quote"

Pipedrive supports Pipedrive API (Persons, Deals, Notes endpoints), which makes it a natural target for JsonHook's outbound POST requests. Every email that hits your JsonHook address is parsed within milliseconds and delivered to Pipedrive as a clean JSON object — no polling, no manual export, no middleware server to maintain.

Setting Up Pipedrive with JsonHook

The following steps walk you through connecting JsonHook to Pipedrive. The entire setup typically takes under ten minutes.

1. Step 1: Generate a Pipedrive API token from Settings → Personal preferences → API.
2. Step 2: In Make or Zapier, create a workflow triggered by the JsonHook webhook URL. Add a Pipedrive action to search for an existing Person by email, create one if not found, and then create a Deal or Note linked to that Person.
3. Step 3: In JsonHook, configure the inbound address and set the automation tool's webhook URL as the destination.
4. Step 4: Map from.address to the Pipedrive Person email, from.name to the Person name, subject to the Deal title or Note subject, and text to the Note content.

Once the connection is active, every email sent to your JsonHook address will be automatically parsed and forwarded to Pipedrive. You can test the integration by sending a plain-text email to your JsonHook address and verifying that the payload appears in Pipedrive within a few seconds.

JsonHook supports Pipedrive API (Persons, Deals, Notes endpoints) on the Pipedrive side, so no additional configuration is needed in Pipedrive beyond the steps above. If Pipedrive requires header-based authentication for incoming webhooks, add the required headers in the JsonHook endpoint configuration under Advanced Settings.

Example Workflow: When a prospect responds to a cold email, create a Pipedrive Deal and log the email as a note

This walkthrough demonstrates one concrete way to use JsonHook with Pipedrive. The scenario: When a prospect responds to a cold email, create a Pipedrive Deal and log the email as a note.

When an email matching this scenario arrives, JsonHook parses the raw SMTP message and constructs the following JSON payload before POSTing it to your Pipedrive endpoint:

{
  "messageId": "",
  "from": {
    "name": "Jane Smith",
    "address": "[email protected]"
  },
  "to": [
    { "address": "[email protected]" }
  ],
  "subject": "When a prospect responds to a cold email, create a Pipedrive Deal and log the email as a note",
  "text": "Hi, I need help with my account. Please contact me at your earliest convenience.",
  "html": "
Hi, I need help with my account...
",
  "date": "2026-03-15T10:32:00.000Z",
  "attachments": [],
  "headers": {
    "x-priority": "1"
  }
}

Pipedrive Person: from.address → email[0].value, from.name → name. Pipedrive Deal: subject → title. Pipedrive Note: text → content, associate with Person ID returned from the Person create/search call.

Once Pipedrive receives this payload, it can execute any downstream action — whether that is posting a notification, creating a record, updating a field, or triggering an entire multi-step workflow. The key advantage is that the data arrives as structured JSON, so Pipedrive never needs to parse raw email text or deal with MIME encoding.

Payload Mapping for Pipedrive

JsonHook delivers a consistent JSON schema for every parsed email. The table below shows which JsonHook fields map to the equivalent fields in Pipedrive. Use this as a reference when configuring your Pipedrive Pipedrive API (Persons, Deals, Notes endpoints).

Not every field will be present in every email. Always check for null or missing values before mapping to required fields in Pipedrive. For text-only emails, html will be empty; for HTML-only emails, text may be empty or auto-generated from the HTML. The attachments array will be an empty array when no files are attached.

Best Practices for Pipedrive Email Integration

Following these best practices will make your Pipedrive email integration more reliable, easier to debug, and simpler to scale as your email volume grows.

• Use dedicated addresses per workflow. Create a separate JsonHook inbound address for each distinct Pipedrive workflow you want to trigger. This makes routing explicit and avoids a single endpoint becoming a bottleneck for all email types.
• Validate the payload before acting. In Pipedrive, add a conditional check at the start of your workflow to confirm that required fields like from.address and subject are present and non-empty before executing downstream actions.
• Test with real emails first. Use JsonHook's delivery log to inspect the raw JSON payload before wiring up Pipedrive. Confirm that all the fields you plan to map are actually populated by your email source.
• Handle errors gracefully. Configure Pipedrive to catch webhook delivery failures and send an alert. JsonHook will retry failed deliveries, but your Pipedrive endpoint should return a 2xx status promptly to acknowledge receipt.
• Keep secrets out of email content. Avoid routing emails that contain passwords, API keys, or PII through workflows unless you have appropriate data-handling controls configured in Pipedrive. Use JsonHook's HTTPS delivery to protect data in transit.