Prerequisites
Before continuing, you should have already completed the following for this connector:Configure the Connector
Connector Profile
Connector Profile
Link an Account
Link Account
Link Account
Webhook setup
StackOne creates and manages the Pipedrive webhook subscription automatically when the
account is connected — no manual configuration is required in Pipedrive. A single
subscription is registered covering every enabled event group (e.g. deals, persons) and
each object’s create, change, and delete actions.
The connected account must have admin rights in Pipedrive: OAuth 2.0 connections need
the admin scope enabled on the app, and API-token connections must use a token belonging
to an admin user. The subscription is removed automatically when the account is disconnected.
Available webhook events
Events use Pipedrive’s native {action}.{object} naming, where the action is create,change, or delete.
- Activity Events (create.activity, change.activity, delete.activity) — fired when an activity is created, changed, or deleted.
- Deal Events (create.deal, change.deal, delete.deal) — fired when a deal is created, changed (including stage moves and won/lost status changes), or deleted.
- Lead Events (create.lead, change.lead, delete.lead) — fired when a lead is created, changed, or deleted.
- Note Events (create.note, change.note, delete.note) — fired when a note is created, changed, or deleted.
- Organization Events (create.organization, change.organization, delete.organization) — fired when an organization is created, changed, or deleted.
- Person Events (create.person, change.person, delete.person) — fired when a person contact is created, changed, or deleted.
- Pipeline Events (create.pipeline, change.pipeline, delete.pipeline) — fired when a sales pipeline is created, changed, or deleted.
- Product Events (create.product, change.product, delete.product) — fired when a product is created, changed, or deleted.
- Project Events (create.project, change.project, delete.project) — fired when a project is created, changed, or deleted.
- Stage Events (create.stage, change.stage, delete.stage) — fired when a pipeline stage is created, changed, or deleted.
- User Events (create.user, change.user) — fired when a company user is added or changed; Pipedrive never deletes users, so deactivation arrives as change.user.
How event types are determined
Pipedrive webhooks do not include a single ready-made event type field. Instead, every
delivery carries a meta block with two separate fields:
- meta.action — what happened: create, change, or delete
- meta.entity — which object it happened to: deal, person, activity, etc.
StackOne combines these two fields into the event type shown on each event, in the form{action}.{object}. For example, a webhook arriving with meta.action: create andmeta.entity: activity is delivered as the event type create.activity. If you are
expecting names like activity.created, note the difference: the action comes first and
uses Pipedrive’s verbs (change rather than updated).
Delivery format
Each delivery contains a single event. The full original Pipedrive payload is forwarded
unchanged in the event’s data field and has three parts:
- meta — event metadata: the two event-type fields described above, plus the event UUID
(meta.id), timestamp (meta.timestamp), acting user (meta.user_id), and the affected
record’s id (meta.entity_id).
- data — the record’s current state after the change. Empty for deletions.
- previous — only the fields that changed, with their old values. Empty for creations.