Pipedrive Trigger

Trigger workflows from Pipedrive CRM events

Overview

Triggers a workflow when events happen in Pipedrive CRM. Supports filtering by action type (create, change, delete, or all) and entity type (deal, person, organization, activity, note, pipeline, product, stage, user, activity type, or all). Pipedrive sends webhook POST requests when the configured event occurs on the specified entity. Optionally supports HTTP Basic Auth for incoming webhook verification.

Category: Sales
Tool Name: pipedrive_trigger
Version: 1

Appearance: Icon: lucide-CircleDollarSign | Color: #017737

Node Type

Trigger — webhook (receives incoming HTTP callbacks)

Input / Output

Direction	Port(s)
Input	None (trigger node)
Output	Output

Credentials

This tool requires Pipedrive API credentials. See the Credentials Guide for setup instructions.

Parameters

Parameter	Type	Required	Default	Description
Action	options	No	*	Type of action to receive notifications about.
				Options: * (All), create, change, delete
Entity	options	No	*	Type of entity (object) to receive notifications about.
				Options: activity, activityType, * (All), deal, note, organization, person, pipeline, product, stage, user
Incoming Authentication	options	No	none	If authentication should be activated for the incoming webhook (makes it more secure). When Basic Auth is selected, Pipedrive will send the configured credentials with each webhook request.
				Options: basicAuth, none
Basic Auth Username	string	No	—	Username for HTTP Basic Auth on the incoming webhook. (shown when Incoming Authentication is basicAuth)
Basic Auth Password	string	No	—	Password for HTTP Basic Auth on the incoming webhook. (shown when Incoming Authentication is basicAuth)

Output Data

Each Pipedrive notification produces one output item:

• _trigger — always pipedrive_webhook
• _timestamp — ISO 8601 timestamp of when the request arrived
• _webhookEvent — the event as {entity}.{action}, for example deal.create; either half reads unknown when Pipedrive omits it

The Pipedrive payload is merged in at the top level, so the delivery’s meta block (action, object, record id, user and company ids, timestamp) and its current and previous record snapshots sit directly on the item. Reference them downstream by expression, e.g. {{ $json.current.title }} or {{ $json.meta.action }}. When Incoming Authentication is set to basicAuth, requests that fail the check are rejected and never reach the workflow.

Usage Examples

• Trigger workflow when a new deal is created in Pipedrive
• Start automation when a person is updated in Pipedrive
• Listen for deleted organizations in Pipedrive CRM
• Monitor all changes to deals, persons, and activities in Pipedrive

Example Configuration

Fire when a deal is created:

{
  "id": "pipedrive-trigger",
  "type": "pipedrive_trigger",
  "position": [250, 300],
  "parameters": {
    "entity": "deal",
    "action": "create",
    "incomingAuthentication": "none"
  }
}

Listen to every action on every entity:

{
  "id": "pipedrive-all-events",
  "type": "pipedrive_trigger",
  "position": [250, 300],
  "parameters": {
    "entity": "*",
    "action": "*",
    "incomingAuthentication": "none"
  }
}

Track person changes behind Basic Auth:

{
  "id": "pipedrive-secure-trigger",
  "type": "pipedrive_trigger",
  "position": [250, 300],
  "parameters": {
    "entity": "person",
    "action": "change",
    "incomingAuthentication": "basicAuth",
    "httpAuthUser": "webhook_user",
    "httpAuthPassword": "a-long-random-secret"
  }
}

Watch organization updates only:

{
  "id": "pipedrive-org-updates",
  "type": "pipedrive_trigger",
  "position": [250, 300],
  "parameters": {
    "entity": "organization",
    "action": "change",
    "incomingAuthentication": "none"
  }
}

Monitor every activity event:

{
  "id": "activity-monitor",
  "type": "pipedrive_trigger",
  "position": [250, 300],
  "parameters": {
    "entity": "activity",
    "action": "*",
    "incomingAuthentication": "none"
  }
}

Trigger Behavior

• Activation: When the workflow is activated, a webhook endpoint is registered with the service.
• Deactivation: The webhook is automatically unregistered when the workflow is deactivated.
• Payload: The incoming webhook payload is parsed and output as workflow items.
• Verification: Supports signature verification where applicable.

Tips

Listens for Pipedrive CRM events. Select the action (create, change, delete, or all) and entity type (deal, person, organization, etc.) to filter which events trigger the workflow. Pipedrive will send a POST request to the webhook URL whenever matching events occur.

Important Notes

• The trigger creates a webhook URL that must be registered in your Pipedrive account
• When using Basic Auth, ensure credentials are stored securely and match what’s configured in Pipedrive
• The "*" wildcard values allow monitoring of all entities or all actions, but may result in high webhook volume
• Webhook payloads will contain the full object data from Pipedrive for the triggered event