pipedrive

# Pipedrive ## Freshness Last updated: `2026-06-24`. If the current date is more than 7 days after the last updated date, reinstall this skill from skills.sh or ClawHub before relying on endpoints, schemas, setup steps, or examples. ## What This Tool Does Put your Pipedrive CRM on autopilot. Connect your account and let your AI assistant turn inbound interest into closed deals — capturing leads, creating contacts and organizations, building deals and advancing them through your pipeline, scheduling follow-up calls, logging notes, and attaching proposals automatically. Ask in plain language to find any record, surface stalled deals, route a lead to the right rep, or trigger downstream automations the moment something changes — and skip the manual data entry that eats your selling time. ## Product Instructions ### Pipedrive Manage deals, persons, organizations, activities, products, leads, notes, pipelines, stages, and file attachments in Pipedrive. #### Base rules - Connection and access checks are handled by the platform. - Writes require the matching permission scope: `add` for create, `edit` for update, `delete` for delete. Reads are allowed by default. - `data` is a pass-through JSON body for writes. Convenience fields (`title`, `name`, `value`, `subject`, `content`) are merged underneath `data`; keys in `data` win. - `options` is a pass-through query-param dict. It can only fill gaps — the dispatcher's params always win. It cannot change the URL or HTTP verb. - Pagination: v2 actions use `cursor` + `limit` (max 500). v1 actions use `start` + `limit`. Responses expose `additional_data.next_cursor` (v2) or `additional_data.pagination` (v1). - Every response is wrapped in `{"action": "...", "result": <raw Pipedrive body>}`. #### Public aliases - `organization_id` is the public AgentPMT field. The connector maps it to Pipedrive `org_id` for deal, person, activity, notes, and files actions that require `org_id`. Lead and search actions that document `organization_id` keep that spelling. - `include` is the public AgentPMT field for extra returned fields. The connector maps it to Pipedrive `include_fields`. - Deal `value` can be sent as a number or as `{ "amount": 5000, "currency": "USD" }`. The object form is accepted for compatibility and normalized to numeric `value` plus `currency` for deal create/update. Lead `value` remains `{ "amount": 5000, "currency": "USD" }`. - `data` wins over convenience fields. If raw `data` supplies `org_id`, `value`, or `currency`, that raw intent is preserved. Unsupported `organization_id` in a body is normalized to `org_id` only for actions that require `org_id`. #### Discovery flow 1. `who_am_i` — confirm connection, company, locale. 2. `list_fields` with `module` in `{deals, persons, organizations, activities, products}` — discover field names and hash keys for custom fields. 3. `list_pipelines` + `list_stages` — find `pipeline_id` / `stage_id`. 4. `search_records` or `item_search` — look up records by term. 5. Read → update → verify. #### Generic CRUD (deal / person / organization / activity / product) All five core resources share a single set of six verbs and a `resource` parameter. ```json {"action":"list_records","resource":"deal","limit":50,"pipeline_id":1,"status":"open"} {"action":"get_record","resource":"deal","deal_id":42,"include":["products_count"]} {"action":"create_record","resource":"deal","title":"Acme website","value":{"amount":5000,"currency":"USD"},"person_id":10} {"action":"create_record","resource":"deal","title":"Acme website","value":5000,"data":{"currency":"USD"},"person_id":10,"organization_id":20} {"action":"update_record","resource":"deal","deal_id":42,"data":{"stage_id":3,"status":"won"}} {"action":"delete_record","resource":"deal","deal_id":42} {"action":"search_records","resource":"deal","term":"Acme","fields":["title"],"limit":25} {"action":"create_record","resource":"person","name":"Jane Doe","data":{"emails":[{"value":"jane@acme.com","primary":true}]}} {"action":"search_records","resource":"person","term":"jane@acme.com","fields":["email"]} {"action":"create_record","resource":"organization","name":"Acme Corp","data":{"address":"1 Main St"}} {"action":"create_record","resource":"activity","subject":"Intro call","data":{"type":"call","due_date":"2026-05-01","due_time":"15:00","deal_id":42}} {"action":"create_record","resource":"product","name":"Consulting hour","data":{"prices":[{"currency":"USD","price":250}]}} ``` Required primary field for `create_record` by resource: - `deal` → `title` - `person` / `organization` / `product` → `name` - `activity` → `subject` `search_records` is not supported for `activity` (use `list_records` with filters). #### Leads `list_leads`, `get_lead`, `create_lead`, `update_lead`, `delete_lead` run on v1 (UUIDs). `search_leads` and `convert_lead` run on v2. ```json {"action":"list_leads","limit":50,"owner_id":3} {"action":"get_lead","lead_id":"a1b2c3d4-..."} {"action":"create_lead","title":"Acme — inbound","person_id":10,"value":{"amount":1000,"currency":"USD"}} {"action":"update_lead","lead_id":"a1b2c3d4-...","data":{"label_ids":["hot"]}} {"action":"delete_lead","lead_id":"a1b2c3d4-..."} {"action":"search_leads","term":"Acme"} {"action":"convert_lead","lead_id":"a1b2c3d4-..."} ``` #### Notes ```json {"action":"list_notes","deal_id":42,"limit":50} {"action":"get_note","note_id":123} {"action":"create_note","content":"Called Jane — follow up Tuesday","deal_id":42} {"action":"update_note","note_id":123,"content":"Updated summary"} {"action":"delete_note","note_id":123} ``` #### Pipelines & stages (read-only) ```json {"action":"list_pipelines"} {"action":"get_pipeline","pipeline_id":1} {"action":"list_stages","pipeline_id":1} {"action":"get_stage","stage_id":3} ``` #### Global search & metadata ```json {"action":"item_search","term":"Acme","item_types":["deal","person","organization"]} {"action":"list_fields","module":"deals"} {"action":"list_users"} {"action":"who_am_i"} ``` #### Files File actions integrate with the AgentPMT File Manager. Upload bytes to File Manager first (via the file-management tool), then pass the resulting `file_id` here for `upload_file`. For `download_file`, Pipedrive-hosted bytes are pulled from Pipedrive and stored in File Manager under the caller's budget; the response returns the new File Manager `file_id` and a signed URL. Google Drive remote attachments created by `link_remote_file` are not Pipedrive-hosted bytes: use `get_file` or `list_files` to read `remote_id`, then use the Google Drive tool's `download_file_to_storage` action with that file id. ```json {"action":"list_files","deal_id":42} {"action":"get_file","pipedrive_file_id":7} {"action":"download_file","pipedrive_file_id":7} {"action":"upload_file","file_id":"<file-manager-file-id>","deal_id":42,"file_name_override":"proposal.pdf"} {"action":"link_remote_file","remote_location":"googledrive","remote_id":"<drive-file-id>","deal_id":42} {"action":"update_file","pipedrive_file_id":7,"file_name_override":"proposal-v2.pdf","file_description":"Signed version"} {"action":"delete_file","pipedrive_file_id":7} ``` `upload_file` requires **exactly one** association id: `deal_id`, `person_id`, `organization_id`, `activity_id`, `lead_id`, or `product_id`. `link_remote_file` uses Pipedrive's remote-file item contract and supports **exactly one** of `deal_id`, `person_id`, or `organization_id`. #### Webhooks Subscribe an external `subscription_url` (n8n webhook, Zapier, your own server) to Pipedrive change events. Pipedrive POSTs to that URL when matching records are created, changed, or deleted. - `event_action`: `create`, `change`, `delete`, or `*` (all). - `event_object`: `activity`, `deal`, `lead`, `note`, `organization`, `person`, `pipeline`, `product`, `stage`, `user`, or `*`. - Combine action + object for the event you want (e.g. `create` + `deal` fires on every new deal). - `webhook_version` is `"2.0"` by default — prefer 2.0 for new subscriptions. ```json {"action":"list_webhooks"} {"action":"create_webhook","subscription_url":"<https-webhook-url>","event_action":"change","event_object":"deal","webhook_name":"deal-change-relay"} {"action":"create_webhook","subscription_url":"<https-webhook-url>","event_action":"*","event_object":"lead"} {"action":"delete_webhook","webhook_id":123} ``` `create_webhook` requires `add` permission. `delete_webhook` requires `delete` permission. `list_webhooks` is read-only. #### Response shape Every call returns: ```json {"action":"<action>","result":{"success":true,"data":..., "additional_data":...}} ``` `additional_data.next_cursor` (v2) / `additional_data.pagination.next_start` (v1) drive pagination. ## When To Use - Use this skill for `Pipedrive` on AgentPMT. - Use it when an agent needs this specific tool's behavior, schema, inputs, outputs, and invocation shape. - Search and activation keywords: pipedrive, capture and convert inbound leads, create and update deals contacts and organizations, move deals through pipeline stages, schedule follow up calls and log notes, convert lead, lead id, data.