Running on Pipedrive?

Pipedrive automations skipping deals? We fix it.

Pipedrive is the sales team's visual pipeline until an automation skips a stage because the trigger used the display name rather than the ID, an import stalls on a custom field type mismatch, or a webhook stops signing after a user token rotation. We rebuild the workflow against pipeline IDs, back off on the API, and bring the integrations back to life.

  • Since 2015Fixing technology
  • FreeEstimates
  • US teamReal engineers

pipedrive-webhook.log

still misfiring

What it is

Pipedrive at a glance

Pipedrive is a sales CRM founded in 2010 in Estonia by Timo Rein, Urmas Purde, Ragnar Sass, Martin Henk and Martin Tajur. It built its reputation on the visual kanban-style pipeline, with deals moving left to right through stages, and grew into a widely used CRM for small and mid-sized sales teams who want less ceremony than Salesforce or HubSpot.

The platform covers deals, leads, contacts, organizations, activities, products, projects, campaigns, email tracking, Smart Docs for proposals, LeadBooster for chat and web forms, workflow automation, custom fields, pipelines, and a REST API with v1 and v2, webhooks, OAuth 2.0 and an app marketplace. It supports SSO, two-factor authentication, data residency, and integrations with Gmail, Outlook, Slack, Microsoft Teams, Mailchimp, Zapier and many others. The trouble we see clusters around three things: workflow automations that use display names or stale IDs and silently skip deals, API rate limits that catch bulk imports and nightly sync jobs, and custom field mismatches when syncing with other tools like Mailchimp, HubSpot or an accounting system.

Type
Sales CRM focused on pipeline management
First released
2010
License
Proprietary SaaS, per-seat pricing with Essential, Advanced, Professional, Power and Enterprise tiers
Maintained by
Pipedrive, Inc.
Typically used for
Sales pipeline management, lead tracking, deal automation, sales team productivity

The honest version

Pipedrive pros and cons

No technology is all upside. This is where Pipedrive earns its place and where it tends to cause trouble.

Where Pipedrive is strong

  • Sales teams adopt it quicklyThe kanban pipeline is immediately familiar, and reps who have resisted Salesforce for years find themselves updating Pipedrive without a training deck.
  • Workflow automation without extra toolsThe built-in automation covers stage changes, email triggers, activity creation and field updates, which handles most of the glue that sales teams would otherwise push to Zapier.
  • Custom fields are flexibleDropdowns, dates, monetary values, addresses and formulas cover most of what sales operations needs to track without pulling in a separate spreadsheet.
  • Email integration is first classTwo-way sync with Gmail and Outlook, with deal and contact context attached to threads, keeps the inbox and the CRM in step without duplicate data entry.
  • Mobile apps are genuinely usableThe iOS and Android apps are built for sales reps in the field, with offline support, caller recognition and voice note capture that match what reps actually do between meetings.
  • REST API and webhooks are solidThe API is well documented, mutations behave consistently, and webhooks cover the lifecycle events that most integrations need. Writing a custom app is a reasonable project rather than a major one.

Where Pipedrive bites

  • Reporting is lightweightThe built-in reports cover pipeline value, conversion rates and activity counts, but anything cross-cutting (cohort analysis, revenue attribution, multi-touch funnels) needs export to a BI tool, which is more work than the marketing material implies.
  • Per-seat pricing with feature gatingMany useful features (automations, Smart Docs, team management, custom reports) are gated behind the Advanced or Professional tier, so teams who start on Essential often upgrade quickly and the bill moves faster than expected.
  • Marketing and service modules are shallowCampaigns, LeadBooster chat and Projects are serviceable additions but not a replacement for dedicated marketing automation or ticketing tools. Teams end up with multiple systems anyway.
  • Custom fields are per-entity, not sharedA field on Deals does not automatically exist on Organizations, and the same concept in different places needs duplicate definitions, which is a source of silent data drift.
  • API quota is daily, not rollingDaily caps rather than rolling minute limits mean a single heavy batch job can leave the integration throttled for the rest of the day, which hits nightly reports and syncs harder than it should.
  • Workflow automation is name-based in the UITriggers reference pipeline and stage names in the editor, so a rename breaks them. There is no inventory view that flags broken workflows, and admins have to spot them one by one.

Sound familiar?

Common Pipedrive problems we fix

The Pipedrive problems that bring people to us, and what you have once each one is fixed.

workflow trigger skipped

Automations are missing deals they should catch

A workflow that triggers on 'deal enters stage X' using the stage name rather than the ID, with the stage renamed quietly in a pipeline cleanup. Deals pass through without the automation ever firing.

Workflows bound to stable IDs

429 daily quota exceeded

API hits the daily cap partway through a job

A sync or import that runs without backoff and burns the daily quota before mid-afternoon, leaving the rest of the day's integrations throttled. The job completes with half its records.

Sync paced across the day

custom field key not found

Custom field writes fail after a rename

An integration that caches the custom field key at startup, with the field renamed or redefined in Pipedrive without the integration reloading. Every write returns a 400 against that field.

Field keys refreshed on change

webhook retry limit reached

Webhook consumer loses events during an outage

A downstream service that returns 500s during a brief outage, exhausting the webhook retry budget before coming back up. Events are dropped with no clear way to backfill.

Backfill path, retries resilient

sync to Mailchimp: mapping ambiguous

Field mappings break between Pipedrive and other tools

A custom field in Pipedrive whose values do not map cleanly to the target tool's picklist, or two fields with similar names on different entities. The sync stops or silently loses data.

Mappings explicit and documented

pipeline has 8400 open deals

A pipeline is too large to manage visually

Years of deals sitting in early stages because they were never closed-lost, dragging the kanban view and distorting reports. The team avoids the pipeline rather than cleaning it.

Pipeline hygiene policy, archive clean

OAuth app installation revoked

OAuth app disconnected from an account

A user who disconnected the app during a login prompt, or an admin who removed the app globally, leaves the integration with an invalid access_token and no way to refresh without reauthorisation.

OAuth reauthorisation handled

LeadBooster: origin not whitelisted

Chat widget refuses to load on the site

A LeadBooster installation whose allowed origins were set during development and never updated for the production domain, or a CSP header on the site that blocks the Pipedrive script.

Widget installed and whitelisted

What we do

Pipedrive help, pipeline to API

Call us for one failing automation, or let us own the whole Pipedrive setup and the integrations around it.

Rescue
Automations skipping deals, imports throttled, or a webhook consumer that stopped receiving events. We get the pipeline accurate first and explain the cause second.
Workflow audit
Automations inventoried against current pipelines and stages, dead references removed, overlapping rules consolidated, and a cadence for review when sales ops reshapes the pipeline.
API integrations
Custom webhooks, warehouse exports, Mailchimp or HubSpot syncs, accounting integrations, built to respect the daily quota and survive OAuth rotations.
Data hygiene
Duplicate organisations merged, custom field proliferation trimmed, pipelines cleaned up and a convention agreed for who can create what.
Migrations
Moves in from HubSpot, Salesforce or spreadsheets, or out to one of those systems, with field mappings documented and the parallel-run period scoped.
Managed Tech
Monthly workflow and integration health checks, API deprecation watch (v1 to v2), OAuth app monitoring, and a sales engineer on call when something in the CRM stops working mid-quarter.

How it works

From first message to fixed

  1. Look Free estimate

    Tell us what's going wrong. We look at it, then tell you plainly what's wrong and what it will cost.

  2. Fix

    We fix the cause, not the symptom. If something is down, getting it back up comes first.

  3. Harden

    Backups, monitoring, updates and access, so the same problem can't quietly come back.

  4. Hand back or stay on

    You get a plain-language write-up. Or we stay on for hosting, upkeep and new work.

Often found together

Running Pipedrive alongside something else?

We work on the whole stack, so the problem can be wherever it actually is.

Questions

Pipedrive questions

Something else? Call+1 737 727 7327

Why do Pipedrive workflow automations keep missing deals?

The most common reason is a trigger that was written against a stage name or a pipeline name that has since been renamed. Pipedrive stores the automation against the name you selected in the editor, and the UI does not flag broken references after the fact. We rebuild the triggers against stable pipeline and stage IDs where the API allows, and we audit workflows every time the sales ops team reshapes the pipeline.

How do we handle Pipedrive API rate limits for a nightly sync?

The quota is daily rather than rolling per minute, so a burst at midnight can leave you throttled all day. We spread the sync across the day, batch reads using the most efficient endpoints (GET /deals with pagination rather than one-by-one), implement backoff on 429s, and keep a checkpoint so a failed job resumes rather than restarts. For high-volume accounts, Enterprise raises the ceiling but does not change the shape of the problem.

Why does our Pipedrive integration keep breaking after we rename custom fields?

Pipedrive custom fields are addressed by an internal key (something like abc123def456) rather than the display name. Integrations that hardcode the key work until the field is deleted and recreated, which changes the key. Integrations that use the display name break when the field is renamed. The reliable pattern is to fetch the current key at startup from the fields endpoint and cache it for the session only.

Can we migrate from HubSpot or Salesforce to Pipedrive without losing history?

Mostly yes. Contacts, deals, companies and activities transfer through the API, custom fields need explicit mapping, and email history transfers as a bulk import with the usual caveats about threading. Workflows and automations have to be rebuilt on the Pipedrive side (there is no portable format), and we usually run both systems in parallel for a few weeks to catch anything missed.

How do we build a reliable Pipedrive webhook consumer?

Verify the delivery source, respond with a 2xx quickly and process in the background, make the handler idempotent so a retry does no harm, and record every delivery so you can tell the difference between a bug in your consumer and a Pipedrive outage. For important events, also keep a reconciliation job that pulls recent changes from the API in case webhook retries ran out during an outage.

How much does Pipedrive help cost?

A quote is free. Share the tier, the symptom and any integrations in play, and we come back with a scope and a price before any engineer logs in.

Free estimate

Pipedrive giving you trouble?

Workflow audits, API integrations, migrations and the custom field hygiene that keeps Pipedrive honest. We work on the whole CRM footprint rather than one pipeline.

  • No charge to find out what it will take
  • If it's urgent, say so

Replies come from a person. By sending, you authorize us to email you back. No marketing.