Pipedrive Webhook Setup

What You’re Setting Up

Pipedrive webhooks notify our integration whenever something changes in your account — a deal moves stages, a contact is created, an activity is completed. Unlike some platforms, Pipedrive has a straightforward webhook system where you register a URL and select which events to listen for.

Step-by-Step Setup

Option A: Through the Pipedrive UI

1. Log into Pipedrive
2. Go to Settings (gear icon)
3. Navigate to Webhooks under the Tools and integrations section
4. Click to create a new webhook
5. Enter the endpoint URL we provided
6. Select the event types you want to subscribe to
7. Save the webhook

Option B: Through the API

We can also create webhooks programmatically using your API token. This is how we typically do it — it’s faster and lets us configure the exact events we need. If we’re handling this, you don’t need to do anything in the UI.

Event Types Available

Pipedrive organizes webhooks by object and action:

Objects:

• Deals
• Persons (contacts)
• Organizations
• Activities
• Notes
• Products
• Pipelines and stages

Actions:

• Added (new record created)
• Updated (any field changed)
• Deleted (record removed)
• Merged (two records combined)

You combine an object with an action. For example: “Deal updated” fires every time any field on a deal changes.

Common Event Configurations

Payload Format

When a webhook fires, Pipedrive sends a JSON payload to our endpoint containing:

• The current state of the object (all fields)
• The previous state of the object (so we can see what changed)
• Metadata: timestamp, event type, user who made the change

The “previous” data is particularly useful — it lets us determine exactly which field changed without having to track state ourselves.

Testing Webhooks

After creating a webhook:

1. Create or update a test record that matches the event type
2. Check our endpoint logs (or use a testing tool like webhook.site during setup)
3. Verify the payload contains the fields your integration needs
4. Confirm the timing — Pipedrive webhooks typically fire within seconds

If you’re testing with webhook.site first, create a temporary webhook pointing there, trigger an event, and inspect the payload before switching to our production URL.

Common Issues

Webhook Not Firing

• Confirm the webhook is active in Settings > Webhooks
• Check that the event type matches what you’re doing (e.g., “deal updated” won’t fire when you create a new deal)
• Verify the endpoint URL is correct and accessible from the internet

Too Many Events

The “updated” event fires on any field change. If your team updates deals frequently, this can generate a lot of webhook traffic. Our integration filters for relevant changes, but if volume is a concern, talk to us about filtering strategies.

Webhook Disabled After Failures

Pipedrive will disable a webhook if the endpoint consistently fails to respond. If webhooks stop unexpectedly, check the webhook list in settings — it may have been auto-disabled. Re-enable it once the endpoint issue is resolved.

Duplicate Events

If you have multiple webhooks subscribed to the same event, you’ll get duplicate deliveries. Check your webhook list for duplicates.

Next Steps

• Need to set up a sandbox first? Pipedrive Developer Sandbox
• Get your API token: Pipedrive API Token Setup
• Learn more about our Pipedrive Integration Services