Pipedrive Trigger

Node catalog Triggers

On this page

Receive CRM events through an authenticated webhook.

Usage and specifics

Create a CRM Webhook credential with a random secret, publish, then configure a CRM-side JSON POST. Send the secret in X-Nodulz-CRM-Secret or the token parameter. This dedicated secret does not verify native HubSpot or Close signatures. Remote subscriptions are not created automatically.

Technical type : pipedrive_trigger. Runtime : nodulz.

Credentials and prerequisites

CRM webhook (integration / crm_webhook). Dedicated shared secret for CRM webhooks. Send it in X-Nodulz-CRM-Secret or the URL token parameter.

Create credentials in your nodulz instance’s Credentials area, then select them on the node. Availability depends on ownership and sharing. See the credentials guide for access and rotation.

Parameters

Names below are technical keys. Defaults are not a ready-to-run configuration: complete fields required by your operation. Paths containing [] describe list items; some fields depend on the selected mode.

Parameter	Type	Default	Values / limits
`rateLimitEnabled`	`boolean`	-	-
`rateLimitMax`	`number`	-	-; > 0
`rateLimitWindowMs`	`number`	-	-; > 0
`allowedIps`	`array`	-	-; max 256
`blockedIps`	`array`	-	-; max 256
`credentialId`	`string`	`""`	-
`events`	`array`	`[]`	-
`resourceId`	`string`	`""`	-
`testPayload`	`string`	`""`	-

Configuration help

events Events to receive: Exact names, separated by commas. Examples: created, updated, deleted. Empty: all. For native formats, use the name sent by the CRM, such as contact.creation for HubSpot and create for Pipedrive.
testPayload Test event: Normalized body containing event, resourceId and payload. The provider is added automatically. Leave empty to generate an example.

Initial configuration

Initial catalog configuration example, to adapt before running. Keep secrets in credentials.

json

{
  "credentialId": "",
  "events": [],
  "resourceId": "",
  "testPayload": ""
}

Verification

Test with representative data. Check node output in the inspector and logs, then use editor mapping for downstream fields. A trigger test with a simulated payload does not validate external service delivery.