Pipedrive triggers start a run from what happens in your Pipedrive company. All six are instant — Pipedrive tells Bizomate when it happens:

  • Pipedrive · New deal — When a deal is added.
  • Pipedrive · New person — When a person is added.
  • Pipedrive · New organisation — When an organisation is added.
  • Pipedrive · New activity — When an activity is added.
  • Pipedrive · Deal updated — When a deal's fields change — previous holds what they were.
  • Pipedrive · Deal won / lost — When a deal is marked won or lost.

Publishing adds a webhook to your Pipedrive company for you, and nothing needs pasting — see How instant triggers work.

Who can do this

Workspace Admins and Editors. Viewers see the trigger and its status but cannot change it. Pipedrive is a premium service, marked ◇: you can set the trigger up and test it on any plan; publishing asks for a paid plan.

Before you start

A Pipedrive connection — see Connect Pipedrive.

Steps

  1. Open the workflow in the designer and open the trigger picker — Browse all triggers on an empty workflow, or select the trigger and Change how it starts.
  2. Under Pipedrive, select the event. It reads Pipedrive · instant. Or type Pipedrive in Search triggers.
  3. In Connection, choose your Pipedrive connection — Consulace Pipedrive.
  4. For New deal, Deal updated and Deal won / lost: optional, in Pipeline, choose one — Sales. Empty: every pipeline.
  5. For Deal updated: optional, in Fields to watch, choose a field — Stage. Only a change to this field starts a run — to watch several, use a value with their names separated with commas. Empty: any field.
  6. For Deal won / lost: in When it is, choose Won or lost (the default), Won or Lost.
  7. The panel reads Publishing sets this up in Pipedrive, and every publish sets it up again. It stays while the workflow is published — switched off, what arrives is ignored — and is taken away when the workflow is deleted or starts another way.
  8. Add the steps, then Publish. Bizomate adds a webhook to your Pipedrive company. The panel reads Waiting for the first event — Make one happen; it appears here within seconds.

Test with a real event:

  1. Make the event happen in Pipedrive — add a deal for Northwind Logistics, say.
  2. When Pipedrive sends it, the panel reads Listening — instant — Last event 10:45 · New deal · Northwind Logistics — fleet tracking.
  3. On Output, select Use the last event, then Test run.

What the trigger gives

The record, read back from Pipedrive as the Pipedrive steps read it — id, url, each field by its API name with linked records' names beside them (org_id and orgName), createdAt, updatedAt, and for a deal stageName and pipelineName — and user, the name of whoever did it. Also:

  • Deal updated: previous — the fields that changed, by API name, as they were before — {"stage_id": 3}.
  • Deal won / lost: status — won or lost.

What happens next

  • Each event starts one run of the live version, in Production, named after it — New deal · Northwind Logistics — fleet tracking, New person · Rohan Mehta, Deal updated · …, Deal won · ….
  • Each workflow has its own webhook in Pipedrive. Every publish sets it up again; changing to another trigger and publishing, or deleting the workflow, removes it.
  • If Pipedrive cannot be asked for the record when the event arrives, the run starts with the record as the event told it.

How Bizomate knows an event is Pipedrive's

When it makes the webhook, Bizomate gives Pipedrive a user name and password of its own making, keeps the password encrypted, and Pipedrive sends both with every event. An event without them is answered 401 — The signature does not match. — and starts nothing. You never see or type them.

Good to know

  • Deal updated ignores fields Pipedrive works out itself, such as the update time and counts. A change to anything else — a stage move, a win — counts, unless Fields to watch narrows it.
  • Deal won / lost starts a run only when a deal's status changes to won or lost — not when another field of a won deal changes.
  • Fields to watch takes labels or API names. A watched field deleted in Pipedrive since is passed over.
  • The webhook is made with the connection's token. Pipedrive sends the events about what that user can see. If the user is deactivated, replace the token and publish again.
  • Runs count in the month's allowance.

If something goes wrong

What you see Why What to do
Not listening — Pipedrive would not take Bizomate's address: Pipedrive refused: … Check the connection's details on Connections. Fix it, then publish again. The token was regenerated, or its user deactivated. Select Reconnect and replace the token, then publish again.
Not listening — Pipedrive would not take Bizomate's address: Pipedrive did not say which webhook it made. Publish again. Fix it, then publish again. Pipedrive's answer was incomplete. Publish again.
Waiting for the first event stays Nothing has happened yet, the deal is in another pipeline, or the field changed is not one you watch. Make the event happen with a record that matches.
Nothing has arrived yet — make one happen in Pipedrive, then try again. on Output No event has reached the trigger yet. Make one happen, wait for Listening — instant, then Use the last event.
Publishing stops — "“New deal” needs a paid plan. Change the plan, or remove it and publish the rest." The company is on the Free plan. Ask the company Owner to change the plan; see Premium connections on the Free plan.
A run did not start for an event the panel shows The workflow is switched off, or its workspace is archived. Switch it on — see Switch a workflow on or off. The missed event does not run later.