Pipedrive CRM
MCPB · PIPEDRIVE-MCP-SERVER-2.5.0.MCPB · 2 COMPONENTS · SCANNED AUG 3
MCP server for Pipedrive CRM. 155 tools for deals, persons, organizations, activities, and more.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score →
Supply Chain Security13
- Malware scan not yet available for this package.Unverified
- CVE data not yet available for this package.Unverified
- No install/post-install scripts declared.Pass
- Only part of the dependency tree could be resolved (94 of 98), so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 11 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability74
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 14161 tokens (~115/item across 123 items; 123 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
mcpb · pipedrive-mcp-server-2.5.0.mcpb
Download bundleEvery change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 3 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Aug 26 +18
- Security disclosure: fail → unverified ▼ functional
- Dependency health: unverified → partial ▲ functional
- Schema quality: unverified → excellent ▲ functional
- Stability: unverified → 0.23 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- 1 Aug 26 −5
- Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
- Capabilities: pass → unverified ▼ functional
- 31 Jul 26 +17
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 −21
- Tool coverage: 100 → unverified ▼ functional
- Dependency health: unverified → partial ▲ functional
- First check of Schema quality: unverified functional
- 27 Jul 26 37
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 3 Aug 2026 · Analysed mcpb/https://github.com/ckalima/pipedrive-mcp-server/releases/download/v2.5.0/[email protected]
Provenance none
Ecosystem: mcpb · Outcome: none
Dependencies 94 packages
94 packages in the resolved dependency tree · 94 deprecated · 29 stale.
The dependency tree was only partially resolved, so these counts may be incomplete.
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.
pipedrive_add_deal_discount ~74
Add an additional discount to a deal.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | number | yes | Discount amount, must be positive (required) |
| description | string | yes | Discount description (required) |
| id | number | yes | The deal ID |
| type | string | yes | Whether amount is a percentage or fixed amount (required) |
No output schema declared.
No examples provided.
pipedrive_add_deal_follower ~51
Add a follower to a deal.
| Name | Type | Req | Description |
|---|---|---|---|
| id | number | yes | The deal ID |
| user_id | number | yes | The ID of the user to add as a follower (required) |
No output schema declared.
No examples provided.
pipedrive_add_deal_installment ~101
Add an installment (payment schedule entry) to a deal. Growth+ plan required; the deal must have at least one one-time product and no recurring products.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | number | yes | Installment amount, must be positive (required) |
| billing_date | string | yes | Billing date in YYYY-MM-DD format (required) |
| description | string | yes | Installment description (required) |
| id | number | yes | The deal ID |
No output schema declared.
No examples provided.
pipedrive_add_deal_product ~241
Attach a single product as a line item to a deal.
| Name | Type | Req | Description |
|---|---|---|---|
| billing_frequency | string | — | Billing frequency for recurring products |
| billing_frequency_cycles | number|null | — | Number of billing cycles (null = unlimited) |
| billing_start_date | string|null | — | Billing start date (YYYY-MM-DD, null to clear) |
| comments | string | — | Free-text comments for this line item |
| discount | number | — | Discount applied to the line item (default 0) |
| discount_type | string | — | Whether discount is a percentage or fixed amount (default percentage) |
| id | number | yes | The deal ID |
| is_enabled | boolean | — | Whether the product is enabled on the deal (default true) |
| item_price | number | yes | Price of one unit (required) |
| product_id | number | yes | The product ID to attach (required) |
| product_variation_id | number|null | — | Product variation ID (null to clear) |
| quantity | number | yes | Quantity of the product (required) |
| tax | number | — | Tax percentage (default 0) |
| tax_method | string | — | How tax is applied |
No output schema declared.
No examples provided.
pipedrive_add_organization_follower ~51
Add a follower to an organization.
| Name | Type | Req | Description |
|---|---|---|---|
| id | number | yes | The organization ID |
| user_id | number | yes | The ID of the user to add as a follower (required) |
No output schema declared.
No examples provided.
pipedrive_add_person_follower ~50
Add a follower to a person.
| Name | Type | Req | Description |
|---|---|---|---|
| id | number | yes | The person ID |
| user_id | number | yes | The ID of the user to add as a follower (required) |
No output schema declared.
No examples provided.
pipedrive_add_product_follower ~50
Add a follower to a product.
| Name | Type | Req | Description |
|---|---|---|---|
| id | number | yes | The product ID |
| user_id | number | yes | The ID of the user to add as a follower (required) |
No output schema declared.
No examples provided.
pipedrive_add_product_variation ~60
Add a variation to a product.
| Name | Type | Req | Description |
|---|---|---|---|
| id | number | yes | The product ID |
| name | string | yes | Product variation name (required, max 255 chars) |
| prices | array | — | Array of price objects per currency |
No output schema declared.
No examples provided.
pipedrive_archive_project ~46
Archive a project by setting its status to archived. (Requires the Projects add-on; Projects API is in public beta.)
| Name | Type | Req | Description |
|---|---|---|---|
| id | number | yes | Project ID to archive |
No output schema declared.
No examples provided.
pipedrive_bulk_add_deal_products ~58
Bulk-add up to 100 line-item products to a deal in one request.
| Name | Type | Req | Description |
|---|---|---|---|
| data | array | yes | Array of 1-100 line-item products to add |
| id | number | yes | The deal ID |
No output schema declared.
No examples provided.
pipedrive_create_activity ~267
Create a new activity in Pipedrive. Subject and type are required.
| Name | Type | Req | Description |
|---|---|---|---|
| attendees | array | — | External attendees (email addresses) |
| busy | boolean | — | Show as busy in calendar |
| deal_id | number | — | Link to deal ID |
| done | boolean | — | Mark as completed |
| due_date | string | — | Due date (YYYY-MM-DD) |
| due_time | string | — | Due time (HH:MM) |
| duration | string | — | Duration (HH:MM) |
| lead_id | string | — | Link to lead ID (UUID format) |
| location | object | — | Activity location (structured object) |
| note | string | — | Activity notes (HTML supported) |
| org_id | number | — | Link to organization ID |
| owner_id | number | — | Owner user ID |
| participants | array | — | Activity participants (person IDs) |
| person_id | number | — | Link to person ID |
| priority | number | — | Activity priority (integer) |
| project_id | number | — | Link to project ID |
| public_description | string | — | Public description for guests |
| subject | string | yes | Activity subject (required) |
| type | string | yes | Activity type: call, meeting, task, deadline, email, lunch (required) |
No output schema declared.
No examples provided.
pipedrive_create_board ~64
Create a new project board. name is required. (Projects add-on; Projects API in public beta.)
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Board name (required, must not be empty) |
| order_nr | number | — | Board order number (integer >= 1) |
No output schema declared.
No examples provided.
pipedrive_create_deal ~231
Create a new deal in Pipedrive. Only title is required; all other fields are optional.
| Name | Type | Req | Description |
|---|---|---|---|
| currency | string | — | 3-letter currency code (e.g., USD, EUR) |
| custom_fields | object | — | Custom field values as object with field keys |
| expected_close_date | string | — | Expected close date (YYYY-MM-DD) |
| label_ids | array | — | Label IDs to attach to deal |
| org_id | number | — | ID of organization to link to deal |
| owner_id | number | — | Owner user ID |
| person_id | number | — | ID of person to link to deal |
| pipeline_id | number | — | Pipeline ID |
| probability | number | — | Success probability (0-100) |
| stage_id | number | — | Stage ID |
| status | string | — | Deal status |
| title | string | yes | Deal title (required) |
| value | number | — | Deal monetary value |
| visible_to | number | — | Visibility: 1=Owner, 3=Group, 5=Subgroups, 7=Company |
No output schema declared.
No examples provided.
pipedrive_create_deal_field ~228
Create a deal custom field. field_name and field_type are required. For enum/set types, options is required. The response data.field_code is the 40-char hash you must keep to update or delete the field later.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string|null | — | Field description (null to clear) |
| field_name | string | yes | Field name (required, 1-255 chars) |
| field_type | string | yes | Field type. Use 'enum' (single choice) or 'set' (multiple choice) for option fields. |
| important_fields | object | — | Important-field highlighting: enabled, stage_ids (always references DEAL stages, even on person/org fields). |
| options | array | — | Field options (required for enum and set field types) |
| required_fields | object | — | Required-field config: enabled, stage_ids (deal stages), statuses (per-pipeline won/lost map). |
| ui_visibility | object | — | UI visibility: add_visible_flag, details_visible_flag, projects_detail_visible_flag, show_in_pipelines{show_in_all, pipeline_ids}. |
No output schema declared.
No examples provided.
pipedrive_create_lead ~153
Create a new lead in Pipedrive. Title is required; link to at least one of person_id or organization_id.
| Name | Type | Req | Description |
|---|---|---|---|
| expected_close_date | string | — | Expected close date (YYYY-MM-DD) |
| label_ids | array | — | Lead label UUIDs |
| organization_id | number | — | Link to organization ID |
| owner_id | number | — | Owner user ID |
| person_id | number | — | Link to person ID |
| title | string | yes | Lead title (required) |
| value | object | — | Monetary value of the lead |
| visible_to | number | — | Visibility: 1=Owner, 3=Group, 5=Subgroups, 7=Company |
No output schema declared.
No examples provided.
pipedrive_create_note ~145
Create a new note in Pipedrive. Content is required. Link to a deal, person, organization, or lead.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | Note content (required, HTML supported) |
| deal_id | number | — | Link to deal ID |
| lead_id | string | — | Link to lead ID (UUID format) |
| org_id | number | — | Link to organization ID |
| person_id | number | — | Link to person ID |
| pinned_to_deal_flag | boolean | — | Pin note to deal |
| pinned_to_organization_flag | boolean | — | Pin note to organization |
| pinned_to_person_flag | boolean | — | Pin note to person |
No output schema declared.
No examples provided.
pipedrive_create_organization ~154
Create a new organization in Pipedrive. Only name is required.
| Name | Type | Req | Description |
|---|---|---|---|
| add_time | string | — | Creation time (RFC3339 format) - backdate the organization |
| address | object | — | Organization address as a structured object (v2). Provide 'value' for the full address. |
| custom_fields | object | — | Custom field values as object with field keys |
| label_ids | array | — | Label IDs to attach to organization |
| name | string | yes | Organization name (required) |
| owner_id | number | — | Owner user ID |
| visible_to | number | — | Visibility: 1=Owner, 3=Group, 5=Subgroups, 7=Company |
No output schema declared.
No examples provided.
pipedrive_create_organization_field ~205
Create an organization custom field. field_name and field_type are required. For enum/set types, options is required. The response data.field_code is the 40-char hash to keep for later updates.
| Name | Type | Req | Description |
|---|---|---|---|
| field_name | string | yes | Field name (required, 1-255 chars) |
| field_type | string | yes | Field type. Use 'enum' (single choice) or 'set' (multiple choice) for option fields. |
| important_fields | object | — | Important-field highlighting: enabled, stage_ids (always references DEAL stages, even on person/org fields). |
| options | array | — | Field options (required for enum and set field types) |
| required_fields | object | — | Required-field config: enabled (person/org fields support only this flag). |
| ui_visibility | object | — | UI visibility: add_visible_flag, details_visible_flag, show_in_add_deal_dialog{show, order}, show_in_add_person_dialog{show, order}. |
No output schema declared.
No examples provided.
pipedrive_create_person ~202
Create a new person (contact) in Pipedrive. Only name is required.
| Name | Type | Req | Description |
|---|---|---|---|
| add_time | string | — | Creation time (RFC3339 format) - backdate the person |
| custom_fields | object | — | Custom field values as object with field keys |
| emails | array | — | Email addresses (array of objects, e.g. [{ value, primary, label }]) |
| label_ids | array | — | Label IDs to attach to person |
| marketing_status | string | — | Marketing status |
| name | string | yes | Person name (required) |
| org_id | number | — | Organization ID to link to |
| owner_id | number | — | Owner user ID |
| phones | array | — | Phone numbers (array of objects, e.g. [{ value, primary, label }]) |
| visible_to | number | — | Visibility: 1=Owner, 3=Group, 5=Subgroups, 7=Company |
No output schema declared.
No examples provided.
pipedrive_create_person_field ~194
Create a person custom field. field_name and field_type are required. For enum/set types, options is required. The response data.field_code is the 40-char hash to keep for later updates.
| Name | Type | Req | Description |
|---|---|---|---|
| field_name | string | yes | Field name (required, 1-255 chars) |
| field_type | string | yes | Field type. Use 'enum' (single choice) or 'set' (multiple choice) for option fields. |
| important_fields | object | — | Important-field highlighting: enabled, stage_ids (always references DEAL stages, even on person/org fields). |
| options | array | — | Field options (required for enum and set field types) |
| required_fields | object | — | Required-field config: enabled (person/org fields support only this flag). |
| ui_visibility | object | — | UI visibility: add_visible_flag, details_visible_flag, show_in_add_deal_dialog{show, order}. |
No output schema declared.
No examples provided.
pipedrive_create_phase ~85
Create a new project phase. name and board_id are required. (Projects add-on; Projects API in public beta.)
| Name | Type | Req | Description |
|---|---|---|---|
| board_id | number | yes | ID of the board this phase belongs to (required) |
| name | string | yes | Phase name (required, must not be empty) |
| order_nr | number | — | Phase order number (integer >= 1) |
No output schema declared.
No examples provided.
pipedrive_create_pipeline ~74
Create a new sales pipeline. Only name is required. Set is_deal_probability_enabled to turn on weighted deal probability for the pipeline.
| Name | Type | Req | Description |
|---|---|---|---|
| is_deal_probability_enabled | boolean | — | Whether deal probability is enabled for this pipeline (default false) |
| name | string | yes | The name of the pipeline (required) |
No output schema declared.
No examples provided.
pipedrive_create_product ~213
Create a new product in Pipedrive. Only name is required.
| Name | Type | Req | Description |
|---|---|---|---|
| billing_frequency | string | — | Billing frequency (default one-time) |
| billing_frequency_cycles | number|null | — | Number of billing cycles (max 208, null = unlimited) |
| category | number | — | Product category ID |
| code | string | — | Product code |
| custom_fields | object | — | Custom field values as object with field keys |
| description | string | — | Product description |
| is_linkable | boolean | — | Whether the product can be linked to deals (default true) |
| name | string | yes | Product name (required) |
| owner_id | number | — | Owner user ID |
| prices | array | — | Array of price objects per currency |
| tax | number | — | Tax percentage (default 0) |
| unit | string | — | Unit of measurement |
| visible_to | number | — | Visibility: 1=Owner, 3=Group, 5=Subgroups, 7=Company |
No output schema declared.
No examples provided.
pipedrive_create_product_field ~159
Create a product custom field. field_name and field_type are required. For enum/set types, options is required. Product fields use a simpler model: no description, important_fields, or required_fields. The response data.field_code is the 40-char hash to keep for later updates.
| Name | Type | Req | Description |
|---|---|---|---|
| field_name | string | yes | Field name (required, 1-255 chars) |
| field_type | string | yes | Field type. Use 'enum' (single choice) or 'set' (multiple choice) for option fields. |
| options | array | — | Field options (required for enum and set field types) |
| ui_visibility | object | — | UI visibility (product fields use a simpler model): add_visible_flag, details_visible_flag. |
No output schema declared.
No examples provided.
pipedrive_create_project ~202
Create a new project in Pipedrive. Requires title, board_id, and phase_id. (Requires the Projects add-on; Projects API is in public beta.)
| Name | Type | Req | Description |
|---|---|---|---|
| board_id | number | yes | Board ID the project belongs to (required) |
| deal_ids | array | — | Deal IDs linked to the project |
| description | string | — | Project description |
| end_date | string | — | Project end date (YYYY-MM-DD) |
| label_ids | array | — | Label IDs to attach to the project |
| org_ids | array | — | Organization IDs linked to the project |
| owner_id | number | — | Owner user ID |
| person_ids | array | — | Person IDs linked to the project |
| phase_id | number | yes | Phase ID within the board (required) |
| start_date | string | — | Project start date (YYYY-MM-DD) |
| status | string | — | Project status |
| title | string | yes | Project title (required) |
No output schema declared.
No examples provided.
pipedrive_create_stage ~155
Create a new stage in a pipeline. name and pipeline_id are required. Use is_deal_rot_enabled and days_to_rotten to configure deal rotting.
| Name | Type | Req | Description |
|---|---|---|---|
| days_to_rotten | number|null | — | Days until a deal not updated in this stage becomes rotten (applies only when is_deal_rot_enabled is set; null to clear) |
| deal_probability | number | — | The success probability percentage of deals in this stage (0-100) |
| is_deal_rot_enabled | boolean | — | Whether deals in this stage can become rotten |
| name | string | yes | The name of the stage (required) |
| pipeline_id | number | yes | The ID of the pipeline to add the stage to (required) |
No output schema declared.
No examples provided.
pipedrive_create_task ~271
Create a new task in a project. title and project_id are required. Use boolean is_done/is_milestone (same field names as the GET response); a milestone task must have a due_date. (Projects add-on; Projects API in public beta.)
| Name | Type | Req | Description |
|---|---|---|---|
| assignee_id | number|null | — | Assignee user ID (null to unassign) |
| assignee_ids | array | — | Array of assignee user IDs (max 10) |
| description | string|null | — | Task description (null to clear) |
| due_date | string|null | — | Task due date (YYYY-MM-DD, null to clear) |
| is_done | boolean | — | Mark as done (true/false) |
| is_milestone | boolean | — | Mark as milestone (true/false); a milestone task must have a due_date |
| parent_task_id | number|null | — | ID of the parent task (null for root-level) |
| priority | number|null | — | Task priority (integer >= 0, or null to unset) |
| project_id | number | yes | ID of the project this task belongs to (required) |
| start_date | string|null | — | Task start date (YYYY-MM-DD, null to clear) |
| title | string | yes | Task title (required, 1-255 chars) |
No output schema declared.
No examples provided.
pipedrive_get_activity ~44
Get detailed information about a specific activity by ID.
| Name | Type | Req | Description |
|---|---|---|---|
| id | number | yes | The activity ID |
| include_fields | string | — | Include additional data in response |
No output schema declared.
No examples provided.
pipedrive_get_board ~43
Get detailed information about a specific project board by ID. (Projects add-on; Projects API in public beta.)
| Name | Type | Req | Description |
|---|---|---|---|
| id | number | yes | The board ID |
No output schema declared.
No examples provided.
pipedrive_get_current_user ~33
Get details of the current user (API key owner). Useful for verifying connection and getting your user ID.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
pipedrive_get_deal ~100
Get detailed information about a specific deal by ID, including all standard and custom fields.
| Name | Type | Req | Description |
|---|---|---|---|
| custom_fields | string | — | Include custom fields in response (comma-separated field keys or 'all') |
| id | number | yes | The deal ID |
| include_fields | string | — | Comma-separated extra fields (v2 enum, e.g. next_activity_id, last_activity_id, products_count, files_count, notes_count, followers_count) |
No output schema declared.
No examples provided.
pipedrive_get_deal_conversion_status ~173
Get the status of a deal-to-lead conversion job. Status contract: 'completed' (terminal, carries lead_id), 'failed'/'rejected' (terminal, stop polling, no lead produced), 'not_started'/'running' (in-progress, re-poll). Only 'completed' carries lead_id, and conversion status is purged after a few days, so a 404 returned after a prior valid status means the status was purged (terminal stop-polling signal, not a transient error). Use a bounded poll budget (e.g. up to ~6 attempts with short backoff), not an unbounded loop.
| Name | Type | Req | Description |
|---|---|---|---|
| conversion_id | string | yes | Conversion job UUID returned by the convert call |
| id | number | yes | The deal ID that was converted |
No output schema declared.
No examples provided.
pipedrive_get_deal_emails ~104
Get email messages linked to a deal (company-wide, all users' emails). Returns metadata for emails from any user's mailbox that are linked to this deal. Note: To get full message body, use pipedrive_get_mail_message, but only for emails in YOUR mailbox.
| Name | Type | Req | Description |
|---|---|---|---|
| id | number | yes | Deal ID |
| limit | number | — | Number of items (1-500) |
| start | number | — | Pagination offset (0-based) |
No output schema declared.
No examples provided.
pipedrive_get_deal_followers_changelog ~59
Get the followers changelog for a deal.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | — | Cursor for pagination |
| id | number | yes | The deal ID |
| limit | number | — | Number of items (1-100) |
No output schema declared.
No examples provided.
pipedrive_get_field ~65
Get details of a specific field by its key. Useful for looking up what a 40-character hash field key means.
| Name | Type | Req | Description |
|---|---|---|---|
| entity_type | string | yes | Entity type the field belongs to |
| key | string | yes | Field key (40-char hash for custom fields) |
No output schema declared.
No examples provided.
pipedrive_get_lead ~31
Get detailed information about a specific lead by UUID.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Lead UUID |
No output schema declared.
No examples provided.
pipedrive_get_lead_conversion_status ~73
Get the status of an async lead-to-deal conversion by conversion ID (Pipedrive v2 GET /leads/{id}/convert/status/{conversion_id}).
| Name | Type | Req | Description |
|---|---|---|---|
| conversion_id | string | yes | Conversion job UUID returned by the convert call |
| id | string | yes | Lead UUID |
No output schema declared.
No examples provided.
pipedrive_get_mail_message ~70
Get full email message with body. Access depends on visibility settings - messages linked to deals/persons you can access should work, even if sent by other users.
| Name | Type | Req | Description |
|---|---|---|---|
| id | number | yes | Mail message ID |
| include_body | boolean | — | Include full email body (default: false) |
No output schema declared.
No examples provided.
pipedrive_get_mail_thread ~58
Get a mail thread with messages. Access depends on visibility settings - threads visible within deals/persons you can access should work. Returns 404 if the thread isn't accessible to you.
| Name | Type | Req | Description |
|---|---|---|---|
| id | number | yes | Mail thread ID |
No output schema declared.
No examples provided.
pipedrive_get_note ~31
Get detailed information about a specific note by ID.
| Name | Type | Req | Description |
|---|---|---|---|
| id | number | yes | The note ID |
No output schema declared.
No examples provided.
pipedrive_get_organization ~66
Get detailed information about a specific organization by ID.
| Name | Type | Req | Description |
|---|---|---|---|
| custom_fields | string | — | Include custom fields in response (comma-separated field keys or 'all') |
| id | number | yes | The organization ID |
| include_fields | string | — | Include additional data in response |
No output schema declared.
No examples provided.
pipedrive_get_organization_followers_changelog ~59
Get the followers changelog for an organization.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | — | Cursor for pagination |
| id | number | yes | The organization ID |
| limit | number | — | Number of items (1-100) |
No output schema declared.
No examples provided.
pipedrive_get_person ~92
Get detailed information about a specific person by ID.
| Name | Type | Req | Description |
|---|---|---|---|
| custom_fields | string | — | Include custom fields in response (comma-separated field keys or 'all') |
| id | number | yes | The person ID |
| include_fields | string | — | Comma-separated extra fields (v2 enum, e.g. next_activity_id, open_deals_count, won_deals_count, notes_count, followers_count) |
No output schema declared.
No examples provided.
pipedrive_get_person_emails ~103
Get email messages linked to a person (company-wide, all users' emails). Returns metadata for emails from any user's mailbox that are linked to this person. Note: To get full message body, use pipedrive_get_mail_message, but only for emails in YOUR mailbox.
| Name | Type | Req | Description |
|---|---|---|---|
| id | number | yes | Person ID |
| limit | number | — | Number of items (1-500) |
| start | number | — | Pagination offset (0-based) |
No output schema declared.
No examples provided.
pipedrive_get_person_followers_changelog ~58
Get the followers changelog for a person.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | — | Cursor for pagination |
| id | number | yes | The person ID |
| limit | number | — | Number of items (1-100) |
No output schema declared.
No examples provided.
pipedrive_get_person_picture ~50
Get the picture for a person (read-only; returns picture metadata and sized image URLs). Returns an error if the person has no picture.
| Name | Type | Req | Description |
|---|---|---|---|
| id | number | yes | The person ID |
No output schema declared.
No examples provided.
pipedrive_get_phase ~43
Get detailed information about a specific project phase by ID. (Projects add-on; Projects API in public beta.)
| Name | Type | Req | Description |
|---|---|---|---|
| id | number | yes | The phase ID |
No output schema declared.
No examples provided.
pipedrive_get_product ~31
Get detailed information about a specific product by ID.
| Name | Type | Req | Description |
|---|---|---|---|
| id | number | yes | The product ID |
No output schema declared.
No examples provided.
pipedrive_get_product_followers_changelog ~58
Get the followers changelog for a product.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | — | Cursor for pagination |
| id | number | yes | The product ID |
| limit | number | — | Number of items (1-100) |
No output schema declared.
No examples provided.
pipedrive_get_product_image ~43
Get the image of a product (returns a single image with a public URL valid for 7 days).
| Name | Type | Req | Description |
|---|---|---|---|
| id | number | yes | The product ID |
No output schema declared.
No examples provided.