Skip to main content
Glama

webhooks_create

Create a webhook to receive real-time HTTP POST notifications from Pipedrive when specified events occur, such as added deals or updated persons.

Instructions

Create a new webhook to receive real-time notifications from Pipedrive.

Creates a webhook that will send HTTP POST requests to your endpoint when specified events occur.

Required fields:

  • subscription_url: The HTTPS endpoint that will receive webhook notifications

  • event_action: The action that triggers the webhook

  • event_object: The object type that triggers the webhook

Webhook triggers (event_action + event_object):

  • Event Actions: added, updated, deleted, merged, * (all)

  • Event Objects: activity, activityType, deal, note, organization, person, pipeline, product, stage, user, * (all)

Common webhook combinations:

  • New deals: { "event_action": "added", "event_object": "deal" }

  • Updated persons: { "event_action": "updated", "event_object": "person" }

  • Deleted organizations: { "event_action": "deleted", "event_object": "organization" }

  • All events: { "event_action": "", "event_object": "" }

  • All deal events: { "event_action": "*", "event_object": "deal" }

Security:

  • Use HTTPS URLs for security

  • Optionally add HTTP Basic Auth with http_auth_user and http_auth_password

  • Both auth fields must be provided together

Version:

  • version: "2.0" (recommended, default) or "1.0" (legacy)

  • v2.0 includes more data and better structure

Workflow tips:

  1. Set up your endpoint first to handle POST requests

  2. Create the webhook with appropriate event filters

  3. Test with webhooks/list to verify creation

  4. Monitor last_delivery_time and last_http_status for debugging

  5. Your endpoint should return 200-299 status code to acknowledge receipt

Example payloads:

  • Simple webhook: { "subscription_url": "https://example.com/webhook", "event_action": "added", "event_object": "deal" }

  • With auth: { "subscription_url": "https://example.com/webhook", "event_action": "updated", "event_object": "person", "http_auth_user": "user", "http_auth_password": "pass" }

  • All events: { "subscription_url": "https://example.com/webhook", "event_action": "", "event_object": "", "name": "All Events Webhook" }

Important notes:

  • Pipedrive will send a test request immediately after creation

  • Your endpoint must be accessible from Pipedrive servers

  • Webhooks that repeatedly fail may be automatically disabled

  • See Pipedrive documentation for webhook payload structure

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
subscription_urlYesHTTPS URL endpoint that will receive webhook notifications (required)
event_actionYesAction that triggers the webhook: added, updated, deleted, merged, or * (all) (required)
event_objectYesObject type that triggers the webhook (required)
user_idNoID of the user this webhook is associated with
http_auth_userNoHTTP Basic Auth username (must be provided with http_auth_password)
http_auth_passwordNoHTTP Basic Auth password (must be provided with http_auth_user)
versionNoWebhook version (default: 2.0, recommended)
nameNoOptional name to identify this webhook
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations provided, but the description fully discloses behavioral traits: immediate test request, endpoint accessibility requirement, automatic disabling on repeated failures, and security considerations. No contradictions with annotations since none exist.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Description is lengthy but well-structured with clear sections (Required fields, Webhook triggers, Security, Version, Workflow tips, Example payloads, Important notes). Every section adds necessary information; front-loaded with purpose. Slightly verbose but justified by complexity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given 8 parameters (3 required) and no output schema, the description covers all aspects: purpose, usage, parameter details with examples, behavioral notes, and workflow. No gaps remain for an agent to correctly invoke the tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, baseline is 3, but the description adds significant value beyond schema: provides common combinations, clarifies auth fields must be together, explains version defaults, and includes example payloads for all major use cases.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description explicitly states 'Create a new webhook to receive real-time notifications', clearly identifying the verb and resource. It distinguishes from sibling tools webhooks_delete and webhooks_list by focusing on creation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides explicit when-to-use guidance with required fields, event combinations, security tips, and workflow steps. Implicitly differentiates from listing and deleting by focusing only on creation.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/iamsamuelfraga/mcp-pipedrive'

If you have feedback or need assistance with the MCP directory API, please join our Discord server