> ## Documentation Index
> Fetch the complete documentation index at: https://docs.stackone.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Pipedrive Webhook Setup Guide

> Configure Pipedrive to deliver events to StackOne.

## Prerequisites

Before continuing, you should have already completed the following for this connector:

<Steps>
  <Step title="Configure the Connector">
    Enable the connector and set up its connector profile in your project. See <a href="/connect/managing-connectors/overview">Managing Connectors</a>.

    <Columns cols={2}>
      <Card title="Connector Profile" href="/connectors/pipedrive/guides/connector-profile/oauth-2-0" icon="https://stackone-logos.com/api/pipedrive/filled/svg" horizontal>
        Pipedrive - OAuth 2.0
      </Card>

      <Card title="Connector Profile" href="/connectors/pipedrive/guides/connector-profile/api-token" icon="https://stackone-logos.com/api/pipedrive/filled/svg" horizontal>
        Pipedrive - API Token
      </Card>
    </Columns>
  </Step>

  <Step title="Link an Account">
    Connect an account using <a href="/embed/account-linking/overview">StackOne Hub</a> or <a href="/embed/account-linking/auth-link">Auth Link</a>.

    <Columns cols={2}>
      <Card title="Link Account" href="/connectors/pipedrive/guides/link-account/oauth-2-0" icon="https://stackone-logos.com/api/pipedrive/filled/svg" horizontal>
        Pipedrive - OAuth 2.0
      </Card>

      <Card title="Link Account" href="/connectors/pipedrive/guides/link-account/api-token" icon="https://stackone-logos.com/api/pipedrive/filled/svg" horizontal>
        Pipedrive - API Token
      </Card>
    </Columns>
  </Step>
</Steps>

<section data-guide-section data-guide-scopes="">
  <h2>Webhook setup</h2>

  <p>StackOne creates and manages the Pipedrive webhook subscription automatically when the<br />account is connected — no manual configuration is required in Pipedrive. A single<br />subscription is registered covering every enabled event group (e.g. deals, persons) and<br />each object's create, change, and delete actions.<br /><br />The connected account must have <strong>admin</strong> rights in Pipedrive: OAuth 2.0 connections need<br />the `admin` scope enabled on the app, and API-token connections must use a token belonging<br />to an admin user. The subscription is removed automatically when the account is disconnected.</p>
</section>

<section data-guide-section data-guide-scopes="">
  <h2>Available webhook events</h2>

  <p>Events use Pipedrive's native `{action}.{object}` naming, where the action is `create`,<br />`change`, or `delete`.<br /><br />- <strong>Activity Events</strong> (`create.activity`, `change.activity`, `delete.activity`) — fired when an activity is created, changed, or deleted.<br />- <strong>Deal Events</strong> (`create.deal`, `change.deal`, `delete.deal`) — fired when a deal is created, changed (including stage moves and won/lost status changes), or deleted.<br />- <strong>Lead Events</strong> (`create.lead`, `change.lead`, `delete.lead`) — fired when a lead is created, changed, or deleted.<br />- <strong>Note Events</strong> (`create.note`, `change.note`, `delete.note`) — fired when a note is created, changed, or deleted.<br />- <strong>Organization Events</strong> (`create.organization`, `change.organization`, `delete.organization`) — fired when an organization is created, changed, or deleted.<br />- <strong>Person Events</strong> (`create.person`, `change.person`, `delete.person`) — fired when a person contact is created, changed, or deleted.<br />- <strong>Pipeline Events</strong> (`create.pipeline`, `change.pipeline`, `delete.pipeline`) — fired when a sales pipeline is created, changed, or deleted.<br />- <strong>Product Events</strong> (`create.product`, `change.product`, `delete.product`) — fired when a product is created, changed, or deleted.<br />- <strong>Project Events</strong> (`create.project`, `change.project`, `delete.project`) — fired when a project is created, changed, or deleted.<br />- <strong>Stage Events</strong> (`create.stage`, `change.stage`, `delete.stage`) — fired when a pipeline stage is created, changed, or deleted.<br />- <strong>User Events</strong> (`create.user`, `change.user`) — fired when a company user is added or changed; Pipedrive never deletes users, so deactivation arrives as `change.user`.</p>
</section>

<section data-guide-section data-guide-scopes="">
  <h2>How event types are determined</h2>

  <p>Pipedrive webhooks do <strong>not</strong> include a single ready-made event type field. Instead, every<br />delivery carries a `meta` block with two separate fields:<br /><br />- `meta.action` — what happened: `create`, `change`, or `delete`<br />- `meta.entity` — which object it happened to: `deal`, `person`, `activity`, etc.<br /><br />StackOne combines these two fields into the event type shown on each event, in the form<br />`{action}.{object}`. For example, a webhook arriving with `meta.action: create` and<br />`meta.entity: activity` is delivered as the event type `create.activity`. If you are<br />expecting names like `activity.created`, note the difference: the action comes first and<br />uses Pipedrive's verbs (`change` rather than `updated`).</p>
</section>

<section data-guide-section data-guide-scopes="">
  <h2>Delivery format</h2>

  <p>Each delivery contains a single event. The full original Pipedrive payload is forwarded<br />unchanged in the event's `data` field and has three parts:<br /><br />- `meta` — event metadata: the two event-type fields described above, plus the event UUID<br />  (`meta.id`), timestamp (`meta.timestamp`), acting user (`meta.user_id`), and the affected<br />  record's id (`meta.entity_id`).<br />- `data` — the record's current state after the change. Empty for deletions.<br />- `previous` — only the fields that changed, with their old values. Empty for creations.</p>
</section>

## Verify

Your Connector should now be able to receive and process events. Try triggering an event and you should see an Event appear in the Connector logs.