[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7BY28EBJ5TSZGE6XSAT617P":3,"skill-same:01M7BY28EBJ5TSZGE6XSAT617P":51},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":28,"commitSha":29,"skillDirectory":30,"forksCount":31,"repositoryHtmlUrl":32,"repositoryHomepageUrl":33,"ownerHtmlUrl":34,"ownerBlogUrl":6,"ownerDescription":35,"updatedAt":36,"install":37,"resources":50},"01M7BY28EBJ5TSZGE6XSAT617P","pipedrive-automation",null,"Automate Pipedrive CRM operations including deals, contacts, organizations, activities, notes, and pipeline management via Rube MCP (Composio). Always search tools first for current schemas.","YYC-Cube\u002FYYC3-Knowledge-Base","YYC-Cube","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F235006543?v=4","01M79J2PH4SWD2X0825X6PN748","yyc3","01M79J2PHVK3F6ZBYT8K2SCZCW",1,"MIT","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-Skills-技能包\u002FYYC3-Skills-技能包-all-skills\u002Fskills\u002Fpipedrive-automation\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: pipedrive-automation\ndescription: Automate Pipedrive CRM operations including deals, contacts, organizations, activities, notes, and pipeline management via Rube MCP (Composio). Always search tools first for current schemas.\nrequires:\n  mcp: [rube]\ncategory: crm\n---\n\n# Pipedrive Automation via Rube MCP\n\nAutomate Pipedrive CRM workflows including deal management, contact and organization operations, activity scheduling, notes, and pipeline\u002Fstage queries through Composio's Pipedrive toolkit.\n\n**Toolkit docs**: [composio.dev\u002Ftoolkits\u002Fpipedrive](https:\u002F\u002Fcomposio.dev\u002Ftoolkits\u002Fpipedrive)\n\n## Prerequisites\n\n- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)\n- Active Pipedrive connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `pipedrive`\n- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas\n\n## Setup\n\n**Get Rube MCP**: Add `https:\u002F\u002Frube.app\u002Fmcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.\n\n\n1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds\n2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `pipedrive`\n3. If connection is not ACTIVE, follow the returned auth link to complete Pipedrive OAuth\n4. Confirm connection status shows ACTIVE before running any workflows\n\n## Core Workflows\n\n### 1. Create and Manage Deals\n\n**When to use**: User wants to create a new deal, update an existing deal, or review deal details in the sales pipeline.\n\n**Tool sequence**:\n1. `PIPEDRIVE_SEARCH_ORGANIZATIONS` - Find existing org to link to the deal [Optional]\n2. `PIPEDRIVE_ADD_AN_ORGANIZATION` - Create organization if none found [Optional]\n3. `PIPEDRIVE_SEARCH_PERSONS` - Find existing contact to link [Optional]\n4. `PIPEDRIVE_ADD_A_PERSON` - Create contact if none found [Optional]\n5. `PIPEDRIVE_GET_ALL_PIPELINES` - Resolve pipeline ID [Prerequisite]\n6. `PIPEDRIVE_GET_ALL_STAGES` - Resolve stage ID within the pipeline [Prerequisite]\n7. `PIPEDRIVE_ADD_A_DEAL` - Create the deal with title, value, org_id, person_id, stage_id [Required]\n8. `PIPEDRIVE_UPDATE_A_DEAL` - Modify deal properties after creation [Optional]\n9. `PIPEDRIVE_ADD_A_PRODUCT_TO_A_DEAL` - Attach line items\u002Fproducts [Optional]\n\n**Key parameters**:\n- `title`: Deal title (required for creation)\n- `value`: Monetary value of the deal\n- `currency`: 3-letter ISO currency code (e.g., \"USD\")\n- `pipeline_id` \u002F `stage_id`: Numeric IDs for pipeline placement\n- `org_id` \u002F `person_id`: Link to organization and contact\n- `status`: \"open\", \"won\", or \"lost\"\n- `expected_close_date`: Format YYYY-MM-DD\n\n**Pitfalls**:\n- `title` is the only required field for `PIPEDRIVE_ADD_A_DEAL`; all others are optional\n- Custom fields appear as long hash keys in responses; use dealFields endpoint to map them\n- `PIPEDRIVE_UPDATE_A_DEAL` requires the numeric `id` of the deal\n- Setting `status` to \"lost\" requires also providing `lost_reason`\n\n### 2. Manage Contacts (Persons and Organizations)\n\n**When to use**: User wants to create, update, search, or list contacts and companies in Pipedrive.\n\n**Tool sequence**:\n1. `PIPEDRIVE_SEARCH_PERSONS` - Search for existing person by name, email, or phone [Prerequisite]\n2. `PIPEDRIVE_ADD_A_PERSON` - Create new contact if not found [Required]\n3. `PIPEDRIVE_UPDATE_A_PERSON` - Modify existing contact details [Optional]\n4. `PIPEDRIVE_GET_DETAILS_OF_A_PERSON` - Retrieve full contact record [Optional]\n5. `PIPEDRIVE_SEARCH_ORGANIZATIONS` - Search for existing organization [Prerequisite]\n6. `PIPEDRIVE_ADD_AN_ORGANIZATION` - Create new organization if not found [Required]\n7. `PIPEDRIVE_UPDATE_AN_ORGANIZATION` - Modify organization properties [Optional]\n8. `PIPEDRIVE_GET_DETAILS_OF_AN_ORGANIZATION` - Retrieve full org record [Optional]\n\n**Key parameters**:\n- `name`: Required for both person and organization creation\n- `email`: Array of objects with `value`, `label`, `primary` fields for persons\n- `phone`: Array of objects with `value`, `label`, `primary` fields for persons\n- `org_id`: Link a person to an organization\n- `visible_to`: 1 = owner only, 3 = entire company\n- `term`: Search term for SEARCH_PERSONS \u002F SEARCH_ORGANIZATIONS (minimum 2 characters)\n\n**Pitfalls**:\n- `PIPEDRIVE_ADD_AN_ORGANIZATION` may auto-merge with an existing org; check `response.additional_data.didMerge`\n- Email and phone fields are arrays of objects, not plain strings: `[{\"value\": \"test@example.com\", \"label\": \"work\", \"primary\": true}]`\n- `PIPEDRIVE_SEARCH_PERSONS` wildcards like `*` or `@` are NOT supported; use `PIPEDRIVE_GET_ALL_PERSONS` to list all\n- Deletion via `PIPEDRIVE_DELETE_A_PERSON` or `PIPEDRIVE_DELETE_AN_ORGANIZATION` is soft-delete with 30-day retention, then permanent\n\n### 3. Schedule and Track Activities\n\n**When to use**: User wants to create calls, meetings, tasks, or other activities linked to deals, contacts, or organizations.\n\n**Tool sequence**:\n1. `PIPEDRIVE_SEARCH_PERSONS` or `PIPEDRIVE_GET_DETAILS_OF_A_DEAL` - Resolve linked entity IDs [Prerequisite]\n2. `PIPEDRIVE_ADD_AN_ACTIVITY` - Create the activity with subject, type, due date [Required]\n3. `PIPEDRIVE_UPDATE_AN_ACTIVITY` - Modify activity details or mark as done [Optional]\n4. `PIPEDRIVE_GET_DETAILS_OF_AN_ACTIVITY` - Retrieve activity record [Optional]\n5. `PIPEDRIVE_GET_ALL_ACTIVITIES_ASSIGNED_TO_A_PARTICULAR_USER` - List user's activities [Optional]\n\n**Key parameters**:\n- `subject`: Activity title (required)\n- `type`: Activity type key string, e.g., \"call\", \"meeting\", \"task\", \"email\" (required)\n- `due_date`: Format YYYY-MM-DD\n- `due_time`: Format HH:MM\n- `duration`: Format HH:MM (e.g., \"00:30\" for 30 minutes)\n- `deal_id` \u002F `person_id` \u002F `org_id`: Link to related entities\n- `done`: 0 = not done, 1 = done\n\n**Pitfalls**:\n- Both `subject` and `type` are required for `PIPEDRIVE_ADD_AN_ACTIVITY`\n- `type` must match an existing ActivityTypes key_string in the account\n- `done` is an integer (0 or 1), not a boolean\n- Response includes `more_activities_scheduled_in_context` in additional_data\n\n### 4. Add and Manage Notes\n\n**When to use**: User wants to attach notes to deals, persons, organizations, leads, or projects.\n\n**Tool sequence**:\n1. `PIPEDRIVE_SEARCH_PERSONS` or `PIPEDRIVE_GET_DETAILS_OF_A_DEAL` - Resolve entity ID [Prerequisite]\n2. `PIPEDRIVE_ADD_A_NOTE` - Create note with HTML content linked to an entity [Required]\n3. `PIPEDRIVE_UPDATE_A_NOTE` - Modify note content [Optional]\n4. `PIPEDRIVE_GET_ALL_NOTES` - List notes filtered by entity [Optional]\n5. `PIPEDRIVE_GET_ALL_COMMENTS_FOR_A_NOTE` - Retrieve comments on a note [Optional]\n\n**Key parameters**:\n- `content`: Note body in HTML format (required)\n- `deal_id` \u002F `person_id` \u002F `org_id` \u002F `lead_id` \u002F `project_id`: At least one entity link required\n- `pinned_to_deal_flag` \u002F `pinned_to_person_flag`: Filter pinned notes when listing\n\n**Pitfalls**:\n- `content` is required and supports HTML; plain text works but is sanitized server-side\n- At least one of `deal_id`, `person_id`, `org_id`, `lead_id`, or `project_id` must be provided\n- `PIPEDRIVE_GET_ALL_NOTES` returns notes across all entities by default; filter with entity ID params\n\n### 5. Query Pipelines and Stages\n\n**When to use**: User wants to view sales pipelines, stages, or deals within a pipeline\u002Fstage.\n\n**Tool sequence**:\n1. `PIPEDRIVE_GET_ALL_PIPELINES` - List all pipelines and their IDs [Required]\n2. `PIPEDRIVE_GET_ONE_PIPELINE` - Get details and deal summary for a specific pipeline [Optional]\n3. `PIPEDRIVE_GET_ALL_STAGES` - List all stages, optionally filtered by pipeline [Required]\n4. `PIPEDRIVE_GET_ONE_STAGE` - Get details for a specific stage [Optional]\n5. `PIPEDRIVE_GET_DEALS_IN_A_PIPELINE` - List all deals across stages in a pipeline [Optional]\n6. `PIPEDRIVE_GET_DEALS_IN_A_STAGE` - List deals in a specific stage [Optional]\n\n**Key parameters**:\n- `id`: Pipeline or stage ID (required for single-item endpoints)\n- `pipeline_id`: Filter stages by pipeline\n- `totals_convert_currency`: 3-letter currency code or \"default_currency\" for converted totals\n- `get_summary`: Set to 1 for deal summary in pipeline responses\n\n**Pitfalls**:\n- `PIPEDRIVE_GET_ALL_PIPELINES` takes no parameters; returns all pipelines\n- `PIPEDRIVE_GET_ALL_STAGES` returns stages for ALL pipelines unless `pipeline_id` is specified\n- Deal counts in pipeline summaries use `per_stages_converted` only when `totals_convert_currency` is set\n\n## Common Patterns\n\n### ID Resolution\nAlways resolve display names to numeric IDs before operations:\n- **Organization name -> org_id**: `PIPEDRIVE_SEARCH_ORGANIZATIONS` with `term` param\n- **Person name -> person_id**: `PIPEDRIVE_SEARCH_PERSONS` with `term` param\n- **Pipeline name -> pipeline_id**: `PIPEDRIVE_GET_ALL_PIPELINES` then match by name\n- **Stage name -> stage_id**: `PIPEDRIVE_GET_ALL_STAGES` with `pipeline_id` then match by name\n\n### Pagination\nMost list endpoints use offset-based pagination:\n- Use `start` (offset) and `limit` (page size) parameters\n- Check `additional_data.pagination.more_items_in_collection` to know if more pages exist\n- Use `additional_data.pagination.next_start` as the `start` value for the next page\n- Default limit is ~500 for some endpoints; set explicitly for predictable paging\n\n## Known Pitfalls\n\n### ID Formats\n- All entity IDs (deal, person, org, activity, pipeline, stage) are numeric integers\n- Lead IDs are UUID strings, not integers\n- Custom field keys are long alphanumeric hashes (e.g., \"a1b2c3d4e5f6...\")\n\n### Rate Limits\n- Pipedrive enforces per-company API rate limits; bulk operations should be paced\n- `PIPEDRIVE_GET_ALL_PERSONS` and `PIPEDRIVE_GET_ALL_ORGANIZATIONS` can return large datasets; always paginate\n\n### Parameter Quirks\n- Email and phone on persons are arrays of objects, not plain strings\n- `visible_to` is numeric: 1 = owner only, 3 = entire company, 5 = specific groups\n- `done` on activities is integer 0\u002F1, not boolean true\u002Ffalse\n- Organization creation may auto-merge duplicates silently; check `didMerge` in response\n- `PIPEDRIVE_SEARCH_PERSONS` requires minimum 2 characters and does not support wildcards\n\n### Response Structure\n- Custom fields appear as hash keys in responses; map them via the respective Fields endpoints\n- Responses often nest data under `response.data.data` in wrapped executions\n- Search results are under `response.data.items`, not top-level\n\n## Quick Reference\n\n| Task | Tool Slug | Key Params |\n|------|-----------|------------|\n| Create deal | `PIPEDRIVE_ADD_A_DEAL` | `title`, `value`, `org_id`, `stage_id` |\n| Update deal | `PIPEDRIVE_UPDATE_A_DEAL` | `id`, `status`, `value`, `stage_id` |\n| Get deal details | `PIPEDRIVE_GET_DETAILS_OF_A_DEAL` | `id` |\n| Search persons | `PIPEDRIVE_SEARCH_PERSONS` | `term`, `fields` |\n| Add person | `PIPEDRIVE_ADD_A_PERSON` | `name`, `email`, `phone`, `org_id` |\n| Update person | `PIPEDRIVE_UPDATE_A_PERSON` | `id`, `name`, `email` |\n| Get person details | `PIPEDRIVE_GET_DETAILS_OF_A_PERSON` | `id` |\n| List all persons | `PIPEDRIVE_GET_ALL_PERSONS` | `start`, `limit`, `filter_id` |\n| Search organizations | `PIPEDRIVE_SEARCH_ORGANIZATIONS` | `term`, `fields` |\n| Add organization | `PIPEDRIVE_ADD_AN_ORGANIZATION` | `name`, `visible_to` |\n| Update organization | `PIPEDRIVE_UPDATE_AN_ORGANIZATION` | `id`, `name`, `address` |\n| Get org details | `PIPEDRIVE_GET_DETAILS_OF_AN_ORGANIZATION` | `id` |\n| Add activity | `PIPEDRIVE_ADD_AN_ACTIVITY` | `subject`, `type`, `due_date`, `deal_id` |\n| Update activity | `PIPEDRIVE_UPDATE_AN_ACTIVITY` | `id`, `done`, `due_date` |\n| Get activity details | `PIPEDRIVE_GET_DETAILS_OF_AN_ACTIVITY` | `id` |\n| List user activities | `PIPEDRIVE_GET_ALL_ACTIVITIES_ASSIGNED_TO_A_PARTICULAR_USER` | `user_id`, `start`, `limit` |\n| Add note | `PIPEDRIVE_ADD_A_NOTE` | `content`, `deal_id` or `person_id` |\n| List notes | `PIPEDRIVE_GET_ALL_NOTES` | `deal_id`, `person_id`, `start`, `limit` |\n| List pipelines | `PIPEDRIVE_GET_ALL_PIPELINES` | (none) |\n| Get pipeline details | `PIPEDRIVE_GET_ONE_PIPELINE` | `id` |\n| List stages | `PIPEDRIVE_GET_ALL_STAGES` | `pipeline_id` |\n| Deals in pipeline | `PIPEDRIVE_GET_DEALS_IN_A_PIPELINE` | `id`, `stage_id` |\n| Deals in stage | `PIPEDRIVE_GET_DEALS_IN_A_STAGE` | `id`, `start`, `limit` |\n| Add product to deal | `PIPEDRIVE_ADD_A_PRODUCT_TO_A_DEAL` | `id`, `product_id`, `item_price` |\n\n---\n*Powered by [Composio](https:\u002F\u002Fcomposio.dev)*\n","# Pipedrive Automation via Rube MCP\n\nAutomate Pipedrive CRM workflows including deal management, contact and organization operations, activity scheduling, notes, and pipeline\u002Fstage queries through Composio's Pipedrive toolkit.\n\n**Toolkit docs**: [composio.dev\u002Ftoolkits\u002Fpipedrive](https:\u002F\u002Fcomposio.dev\u002Ftoolkits\u002Fpipedrive)\n\n## Prerequisites\n\n- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)\n- Active Pipedrive connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `pipedrive`\n- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas\n\n## Setup\n\n**Get Rube MCP**: Add `https:\u002F\u002Frube.app\u002Fmcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.\n\n\n1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds\n2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `pipedrive`\n3. If connection is not ACTIVE, follow the returned auth link to complete Pipedrive OAuth\n4. Confirm connection status shows ACTIVE before running any workflows\n\n## Core Workflows\n\n### 1. Create and Manage Deals\n\n**When to use**: User wants to create a new deal, update an existing deal, or review deal details in the sales pipeline.\n\n**Tool sequence**:\n1. `PIPEDRIVE_SEARCH_ORGANIZATIONS` - Find existing org to link to the deal [Optional]\n2. `PIPEDRIVE_ADD_AN_ORGANIZATION` - Create organization if none found [Optional]\n3. `PIPEDRIVE_SEARCH_PERSONS` - Find existing contact to link [Optional]\n4. `PIPEDRIVE_ADD_A_PERSON` - Create contact if none found [Optional]\n5. `PIPEDRIVE_GET_ALL_PIPELINES` - Resolve pipeline ID [Prerequisite]\n6. `PIPEDRIVE_GET_ALL_STAGES` - Resolve stage ID within the pipeline [Prerequisite]\n7. `PIPEDRIVE_ADD_A_DEAL` - Create the deal with title, value, org_id, person_id, stage_id [Required]\n8. `PIPEDRIVE_UPDATE_A_DEAL` - Modify deal properties after creation [Optional]\n9. `PIPEDRIVE_ADD_A_PRODUCT_TO_A_DEAL` - Attach line items\u002Fproducts [Optional]\n\n**Key parameters**:\n- `title`: Deal title (required for creation)\n- `value`: Monetary value of the deal\n- `currency`: 3-letter ISO currency code (e.g., \"USD\")\n- `pipeline_id` \u002F `stage_id`: Numeric IDs for pipeline placement\n- `org_id` \u002F `person_id`: Link to organization and contact\n- `status`: \"open\", \"won\", or \"lost\"\n- `expected_close_date`: Format YYYY-MM-DD\n\n**Pitfalls**:\n- `title` is the only required field for `PIPEDRIVE_ADD_A_DEAL`; all others are optional\n- Custom fields appear as long hash keys in responses; use dealFields endpoint to map them\n- `PIPEDRIVE_UPDATE_A_DEAL` requires the numeric `id` of the deal\n- Setting `status` to \"lost\" requires also providing `lost_reason`\n\n### 2. Manage Contacts (Persons and Organizations)\n\n**When to use**: User wants to create, update, search, or list contacts and companies in Pipedrive.\n\n**Tool sequence**:\n1. `PIPEDRIVE_SEARCH_PERSONS` - Search for existing person by name, email, or phone [Prerequisite]\n2. `PIPEDRIVE_ADD_A_PERSON` - Create new contact if not found [Required]\n3. `PIPEDRIVE_UPDATE_A_PERSON` - Modify existing contact details [Optional]\n4. `PIPEDRIVE_GET_DETAILS_OF_A_PERSON` - Retrieve full contact record [Optional]\n5. `PIPEDRIVE_SEARCH_ORGANIZATIONS` - Search for existing organization [Prerequisite]\n6. `PIPEDRIVE_ADD_AN_ORGANIZATION` - Create new organization if not found [Required]\n7. `PIPEDRIVE_UPDATE_AN_ORGANIZATION` - Modify organization properties [Optional]\n8. `PIPEDRIVE_GET_DETAILS_OF_AN_ORGANIZATION` - Retrieve full org record [Optional]\n\n**Key parameters**:\n- `name`: Required for both person and organization creation\n- `email`: Array of objects with `value`, `label`, `primary` fields for persons\n- `phone`: Array of objects with `value`, `label`, `primary` fields for persons\n- `org_id`: Link a person to an organization\n- `visible_to`: 1 = owner only, 3 = entire company\n- `term`: Search term for SEARCH_PERSONS \u002F SEARCH_ORGANIZATIONS (minimum 2 characters)\n\n**Pitfalls**:\n- `PIPEDRIVE_ADD_AN_ORGANIZATION` may auto-merge with an existing org; check `response.additional_data.didMerge`\n- Email and phone fields are arrays of objects, not plain strings: `[{\"value\": \"test@example.com\", \"label\": \"work\", \"primary\": true}]`\n- `PIPEDRIVE_SEARCH_PERSONS` wildcards like `*` or `@` are NOT supported; use `PIPEDRIVE_GET_ALL_PERSONS` to list all\n- Deletion via `PIPEDRIVE_DELETE_A_PERSON` or `PIPEDRIVE_DELETE_AN_ORGANIZATION` is soft-delete with 30-day retention, then permanent\n\n### 3. Schedule and Track Activities\n\n**When to use**: User wants to create calls, meetings, tasks, or other activities linked to deals, contacts, or organizations.\n\n**Tool sequence**:\n1. `PIPEDRIVE_SEARCH_PERSONS` or `PIPEDRIVE_GET_DETAILS_OF_A_DEAL` - Resolve linked entity IDs [Prerequisite]\n2. `PIPEDRIVE_ADD_AN_ACTIVITY` - Create the activity with subject, type, due date [Required]\n3. `PIPEDRIVE_UPDATE_AN_ACTIVITY` - Modify activity details or mark as done [Optional]\n4. `PIPEDRIVE_GET_DETAILS_OF_AN_ACTIVITY` - Retrieve activity record [Optional]\n5. `PIPEDRIVE_GET_ALL_ACTIVITIES_ASSIGNED_TO_A_PARTICULAR_USER` - List user's activities [Optional]\n\n**Key parameters**:\n- `subject`: Activity title (required)\n- `type`: Activity type key string, e.g., \"call\", \"meeting\", \"task\", \"email\" (required)\n- `due_date`: Format YYYY-MM-DD\n- `due_time`: Format HH:MM\n- `duration`: Format HH:MM (e.g., \"00:30\" for 30 minutes)\n- `deal_id` \u002F `person_id` \u002F `org_id`: Link to related entities\n- `done`: 0 = not done, 1 = done\n\n**Pitfalls**:\n- Both `subject` and `type` are required for `PIPEDRIVE_ADD_AN_ACTIVITY`\n- `type` must match an existing ActivityTypes key_string in the account\n- `done` is an integer (0 or 1), not a boolean\n- Response includes `more_activities_scheduled_in_context` in additional_data\n\n### 4. Add and Manage Notes\n\n**When to use**: User wants to attach notes to deals, persons, organizations, leads, or projects.\n\n**Tool sequence**:\n1. `PIPEDRIVE_SEARCH_PERSONS` or `PIPEDRIVE_GET_DETAILS_OF_A_DEAL` - Resolve entity ID [Prerequisite]\n2. `PIPEDRIVE_ADD_A_NOTE` - Create note with HTML content linked to an entity [Required]\n3. `PIPEDRIVE_UPDATE_A_NOTE` - Modify note content [Optional]\n4. `PIPEDRIVE_GET_ALL_NOTES` - List notes filtered by entity [Optional]\n5. `PIPEDRIVE_GET_ALL_COMMENTS_FOR_A_NOTE` - Retrieve comments on a note [Optional]\n\n**Key parameters**:\n- `content`: Note body in HTML format (required)\n- `deal_id` \u002F `person_id` \u002F `org_id` \u002F `lead_id` \u002F `project_id`: At least one entity link required\n- `pinned_to_deal_flag` \u002F `pinned_to_person_flag`: Filter pinned notes when listing\n\n**Pitfalls**:\n- `content` is required and supports HTML; plain text works but is sanitized server-side\n- At least one of `deal_id`, `person_id`, `org_id`, `lead_id`, or `project_id` must be provided\n- `PIPEDRIVE_GET_ALL_NOTES` returns notes across all entities by default; filter with entity ID params\n\n### 5. Query Pipelines and Stages\n\n**When to use**: User wants to view sales pipelines, stages, or deals within a pipeline\u002Fstage.\n\n**Tool sequence**:\n1. `PIPEDRIVE_GET_ALL_PIPELINES` - List all pipelines and their IDs [Required]\n2. `PIPEDRIVE_GET_ONE_PIPELINE` - Get details and deal summary for a specific pipeline [Optional]\n3. `PIPEDRIVE_GET_ALL_STAGES` - List all stages, optionally filtered by pipeline [Required]\n4. `PIPEDRIVE_GET_ONE_STAGE` - Get details for a specific stage [Optional]\n5. `PIPEDRIVE_GET_DEALS_IN_A_PIPELINE` - List all deals across stages in a pipeline [Optional]\n6. `PIPEDRIVE_GET_DEALS_IN_A_STAGE` - List deals in a specific stage [Optional]\n\n**Key parameters**:\n- `id`: Pipeline or stage ID (required for single-item endpoints)\n- `pipeline_id`: Filter stages by pipeline\n- `totals_convert_currency`: 3-letter currency code or \"default_currency\" for converted totals\n- `get_summary`: Set to 1 for deal summary in pipeline responses\n\n**Pitfalls**:\n- `PIPEDRIVE_GET_ALL_PIPELINES` takes no parameters; returns all pipelines\n- `PIPEDRIVE_GET_ALL_STAGES` returns stages for ALL pipelines unless `pipeline_id` is specified\n- Deal counts in pipeline summaries use `per_stages_converted` only when `totals_convert_currency` is set\n\n## Common Patterns\n\n### ID Resolution\nAlways resolve display names to numeric IDs before operations:\n- **Organization name -> org_id**: `PIPEDRIVE_SEARCH_ORGANIZATIONS` with `term` param\n- **Person name -> person_id**: `PIPEDRIVE_SEARCH_PERSONS` with `term` param\n- **Pipeline name -> pipeline_id**: `PIPEDRIVE_GET_ALL_PIPELINES` then match by name\n- **Stage name -> stage_id**: `PIPEDRIVE_GET_ALL_STAGES` with `pipeline_id` then match by name\n\n### Pagination\nMost list endpoints use offset-based pagination:\n- Use `start` (offset) and `limit` (page size) parameters\n- Check `additional_data.pagination.more_items_in_collection` to know if more pages exist\n- Use `additional_data.pagination.next_start` as the `start` value for the next page\n- Default limit is ~500 for some endpoints; set explicitly for predictable paging\n\n## Known Pitfalls\n\n### ID Formats\n- All entity IDs (deal, person, org, activity, pipeline, stage) are numeric integers\n- Lead IDs are UUID strings, not integers\n- Custom field keys are long alphanumeric hashes (e.g., \"a1b2c3d4e5f6...\")\n\n### Rate Limits\n- Pipedrive enforces per-company API rate limits; bulk operations should be paced\n- `PIPEDRIVE_GET_ALL_PERSONS` and `PIPEDRIVE_GET_ALL_ORGANIZATIONS` can return large datasets; always paginate\n\n### Parameter Quirks\n- Email and phone on persons are arrays of objects, not plain strings\n- `visible_to` is numeric: 1 = owner only, 3 = entire company, 5 = specific groups\n- `done` on activities is integer 0\u002F1, not boolean true\u002Ffalse\n- Organization creation may auto-merge duplicates silently; check `didMerge` in response\n- `PIPEDRIVE_SEARCH_PERSONS` requires minimum 2 characters and does not support wildcards\n\n### Response Structure\n- Custom fields appear as hash keys in responses; map them via the respective Fields endpoints\n- Responses often nest data under `response.data.data` in wrapped executions\n- Search results are under `response.data.items`, not top-level\n\n## Quick Reference\n\n| Task | Tool Slug | Key Params |\n|------|-----------|------------|\n| Create deal | `PIPEDRIVE_ADD_A_DEAL` | `title`, `value`, `org_id`, `stage_id` |\n| Update deal | `PIPEDRIVE_UPDATE_A_DEAL` | `id`, `status`, `value`, `stage_id` |\n| Get deal details | `PIPEDRIVE_GET_DETAILS_OF_A_DEAL` | `id` |\n| Search persons | `PIPEDRIVE_SEARCH_PERSONS` | `term`, `fields` |\n| Add person | `PIPEDRIVE_ADD_A_PERSON` | `name`, `email`, `phone`, `org_id` |\n| Update person | `PIPEDRIVE_UPDATE_A_PERSON` | `id`, `name`, `email` |\n| Get person details | `PIPEDRIVE_GET_DETAILS_OF_A_PERSON` | `id` |\n| List all persons | `PIPEDRIVE_GET_ALL_PERSONS` | `start`, `limit`, `filter_id` |\n| Search organizations | `PIPEDRIVE_SEARCH_ORGANIZATIONS` | `term`, `fields` |\n| Add organization | `PIPEDRIVE_ADD_AN_ORGANIZATION` | `name`, `visible_to` |\n| Update organization | `PIPEDRIVE_UPDATE_AN_ORGANIZATION` | `id`, `name`, `address` |\n| Get org details | `PIPEDRIVE_GET_DETAILS_OF_AN_ORGANIZATION` | `id` |\n| Add activity | `PIPEDRIVE_ADD_AN_ACTIVITY` | `subject`, `type`, `due_date`, `deal_id` |\n| Update activity | `PIPEDRIVE_UPDATE_AN_ACTIVITY` | `id`, `done`, `due_date` |\n| Get activity details | `PIPEDRIVE_GET_DETAILS_OF_AN_ACTIVITY` | `id` |\n| List user activities | `PIPEDRIVE_GET_ALL_ACTIVITIES_ASSIGNED_TO_A_PARTICULAR_USER` | `user_id`, `start`, `limit` |\n| Add note | `PIPEDRIVE_ADD_A_NOTE` | `content`, `deal_id` or `person_id` |\n| List notes | `PIPEDRIVE_GET_ALL_NOTES` | `deal_id`, `person_id`, `start`, `limit` |\n| List pipelines | `PIPEDRIVE_GET_ALL_PIPELINES` | (none) |\n| Get pipeline details | `PIPEDRIVE_GET_ONE_PIPELINE` | `id` |\n| List stages | `PIPEDRIVE_GET_ALL_STAGES` | `pipeline_id` |\n| Deals in pipeline | `PIPEDRIVE_GET_DEALS_IN_A_PIPELINE` | `id`, `stage_id` |\n| Deals in stage | `PIPEDRIVE_GET_DEALS_IN_A_STAGE` | `id`, `start`, `limit` |\n| Add product to deal | `PIPEDRIVE_ADD_A_PRODUCT_TO_A_DEAL` | `id`, `product_id`, `item_price` |\n\n---\n*Powered by [Composio](https:\u002F\u002Fcomposio.dev)*\n",{"name":5,"category":24,"requires":25,"description":7},"crm",{"mcp":26},[27],"rube","main","87afe6ce96220accf50a345dea46784c8c9f210e","YYC3-Skills-技能包\u002FYYC3-Skills-技能包-all-skills\u002Fskills\u002Fpipedrive-automation",0,"https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base","https:\u002F\u002Fkb.yyc3.top\u002F","https:\u002F\u002Fgithub.com\u002FYYC-Cube","万象归元于云枢 | 深栈智启新纪元","2026-11-10 10:37:32",{"source":8,"skillName":5,"commands":38,"prompt":48,"zipAvailable":49},[39,42,45],{"tool":40,"command":41},"npx","npx skills add YYC-Cube\u002FYYC3-Knowledge-Base --skill pipedrive-automation",{"tool":43,"command":44},"bunx","bunx skills add YYC-Cube\u002FYYC3-Knowledge-Base --skill pipedrive-automation",{"tool":46,"command":47},"pnpm","pnpm dlx skills add YYC-Cube\u002FYYC3-Knowledge-Base --skill pipedrive-automation","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-Skills-技能包\u002FYYC3-Skills-技能包-all-skills\u002Fskills\u002Fpipedrive-automation\u002FSKILL.md",true,[],[52,59,66,73,80,87],{"skillNo":53,"name":54,"nameZh":6,"description":55,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":56,"categories":57,"keywords":58,"publishedAt":19},"01M7CTDWHERCXPQCP0K03A86AS","vercel-sandbox","Run agent-browser + Chrome inside Vercel Sandbox microVMs for browser automation from any Vercel-deployed app. Use when the user needs browser automation in a Vercel app (Next.js, SvelteKit, Nuxt, Remix, Astro, etc.), wants to run headless Chrome without binary size limits, needs persistent browser sessions across commands, or wants ephemeral isolated browser environments. Triggers include \"Vercel Sandbox browser\", \"microVM Chrome\", \"agent-browser in sandbox\", \"browser automation on Vercel\", or any task requiring Chrome in a Vercel Sandbox.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Fvercel-sandbox\u002FSKILL.md",[],[],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":19},"01M7CTD8D2BNJY54S65M47HEJA","slack","Interact with Slack workspaces using browser automation. Use when the user needs to check unread channels, navigate Slack, send messages, extract data, find information, search conversations, or automate any Slack task. Triggers include \"check my Slack\", \"what channels have unreads\", \"send a message to\", \"search Slack for\", \"extract from Slack\", \"find who said\", or any task requiring programmatic Slack interaction.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Fslack\u002FSKILL.md",[],[],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":19},"01M7CTCSSB8ZP3Q58C3YZDZK1W","electron","Automate Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify, etc.) using agent-browser via Chrome DevTools Protocol. Use when the user needs to interact with an Electron app, automate a desktop app, connect to a running app, control a native app, or test an Electron application. Triggers include \"automate Slack app\", \"control VS Code\", \"interact with Discord app\", \"test this Electron app\", \"connect to desktop app\", or any task requiring automation of a native Electron application.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Felectron\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":19},"01M7CTCBJY76688V4DCZGWFHGQ","dogfood","Systematically explore and test a web application to find bugs, UX issues, and other problems. Use when asked to \"dogfood\", \"QA\", \"exploratory test\", \"find issues\", \"bug hunt\", \"test this app\u002Fsite\u002Fplatform\", or review the quality of a web application. Produces a structured report with full reproduction evidence -- step-by-step screenshots, repro videos, and detailed repro steps for every issue -- so findings can be handed directly to the responsible teams.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Fdogfood\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":19},"01M7CTC4H0FFGVEAQR9PA4GA1A","agent-browser","Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to \"open a website\", \"fill out a form\", \"click a button\", \"take a screenshot\", \"scrape data from a page\", \"test this web app\", \"login to a site\", \"automate browser actions\", or any task requiring programmatic web interaction.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Fagent-browser\u002FSKILL.md",[],[],{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":19},"01M7CTBKVFYBG78FDSABSDJTTQ","shadcn","Manages shadcn components and projects — adding, searching, fixing, debugging, styling, and composing UI, including chat interfaces. Provides project context, component docs, and usage examples. Applies when working with shadcn\u002Fui, component registries, presets, --preset codes, or any project with a components.json file. Also triggers for \"shadcn init\", \"create an app with --preset\", \"switch to --preset\", and for building a design system or applying a DESIGN.md or brand spec to shadcn\u002Fui.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-UI-界面组件\u002FYYC3-UI-界面组件-ui\u002Fskills\u002Fshadcn\u002FSKILL.md",[],[]]