[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6FSP9P7RYYC1ZEXJETYSBEB":3,"skill-same:01M6FSP9P7RYYC1ZEXJETYSBEB":74},{"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":23,"publishedAt":43,"linkOnly":44,"markdownContent":45,"markdownBody":46,"frontMatter":47,"refName":52,"commitSha":53,"skillDirectory":54,"forksCount":14,"repositoryHtmlUrl":55,"repositoryHomepageUrl":6,"ownerHtmlUrl":56,"ownerBlogUrl":57,"ownerDescription":58,"updatedAt":59,"install":60,"resources":73},"01M6FSP9P7RYYC1ZEXJETYSBEB","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.","reikiplanet\u002Fdaoskills","reikiplanet","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F96377599?v=4","01M6CVWCMD740YHQDK7E9QYBW4","Reiki Planet","01M6CVWCS4KXVA2CWFVJ43EAXK",0,"MIT","https:\u002F\u002Fgithub.com\u002Freikiplanet\u002Fdaoskills\u002Fblob\u002Fmaster\u002Fautomation\u002Fpipedrive-automation\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42],"automation","pipedrive","pipedrive automation","pipeline management","MCP","contacts","organizations","via","composio","crm","community","operations","management","automate","first","Tools","pipeline","search","notes","2026-11-10 10:12:30",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]\nrisk: unknown\nsource: community\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## 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## When to Use\nThis skill is applicable to execute the workflow or actions described in the overview.\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## 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## When to Use\nThis skill is applicable to execute the workflow or actions described in the overview.\n",{"name":5,"risk":48,"source":34,"requires":49,"description":7},"unknown",{"mcp":50},[51],"rube","master","dff58085da947e81e8418c922055644bf0082b1b","automation\u002Fpipedrive-automation","https:\u002F\u002Fgithub.com\u002Freikiplanet\u002Fdaoskills","https:\u002F\u002Fgithub.com\u002Freikiplanet","https:\u002F\u002Fwww.reiki-planet.com","Reiki Planet Game","2026-03-29 06:02:29",{"source":8,"skillName":5,"commands":61,"prompt":71,"zipAvailable":72},[62,65,68],{"tool":63,"command":64},"npx","npx skills add reikiplanet\u002Fdaoskills --skill pipedrive-automation",{"tool":66,"command":67},"bunx","bunx skills add reikiplanet\u002Fdaoskills --skill pipedrive-automation",{"tool":69,"command":70},"pnpm","pnpm dlx skills add reikiplanet\u002Fdaoskills --skill pipedrive-automation","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Freikiplanet\u002Fdaoskills\u002Fblob\u002Fmaster\u002Fautomation\u002Fpipedrive-automation\u002FSKILL.md",true,[],[75,101,113,128,148,171],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":43},"01M6G614JTEQJHPT8AKK3YQ18S","web-games","Web browser game development principles. Framework selection, WebGPU, optimization, PWA.","https:\u002F\u002Fgithub.com\u002Freikiplanet\u002Fdaoskills\u002Fblob\u002Fmaster\u002Fweb-games\u002FSKILL.md",[],[82,83,84,85,86,87,34,88,89,90,91,92,93,94,95,96,97,98,99,100],"games","web games","web","grep","principles","selection","framework selection","edit","write","read","pwa","game","web browser","game development","Optimization","framework","browser","development","webgpu",{"skillNo":102,"name":103,"nameZh":6,"description":104,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":105,"categories":106,"keywords":107,"publishedAt":43},"01M6G611H2YGV0GZFP90D38ZMJ","vr-ar","VR\u002FAR development principles. Comfort, interaction, performance requirements.","https:\u002F\u002Fgithub.com\u002Freikiplanet\u002Fdaoskills\u002Fblob\u002Fmaster\u002Fvr-ar\u002FSKILL.md",[],[108,109,99,110,111,34,89,90,91,85,112,86],"ar","vr ar","interaction","requirements","performance",{"skillNo":114,"name":115,"nameZh":6,"description":116,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":117,"categories":118,"keywords":119,"publishedAt":43},"01M6G60XNMHAMV1SV0EJ1CX0AY","templates","Project scaffolding templates for new applications. Use when creating new projects from scratch. Contains 12 templates for various tech stacks.","https:\u002F\u002Fgithub.com\u002Freikiplanet\u002Fdaoskills\u002Fblob\u002Fmaster\u002Ftemplates\u002FSKILL.md",[],[115,120,121,122,123,124,34,125,91,126,127,85],"project scaffolding","From Scratch","tech","project","scaffolding","use","projects","applications",{"skillNo":129,"name":130,"nameZh":6,"description":131,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":132,"categories":133,"keywords":134,"publishedAt":43},"01M6G60T0GATMK3Q5H8GDC1Z8S","wcag-audit-patterns","Conduct WCAG 2.2 accessibility audits with automated testing, manual verification, and remediation guidance. Use when auditing websites for accessibility, fixing WCAG violations, or implementing ac...","https:\u002F\u002Fgithub.com\u002Freikiplanet\u002Fdaoskills\u002Fblob\u002Fmaster\u002Fskills\u002Fsecurity\u002Fwcag-audit-patterns\u002FSKILL.md",[],[135,136,137,138,139,34,140,141,142,143,125,144,145,146,147],"wcag audit patterns","wcag audit","patterns","WCAG","audit","manual","with","automated testing","guidance","remediation","verification","accessibility","testing",{"skillNo":149,"name":150,"nameZh":6,"description":151,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":152,"categories":153,"keywords":154,"publishedAt":43},"01M6G60PMCHW1FRZ63F931QK3R","vulnerability-scanner","Advanced vulnerability analysis principles. OWASP 2025, Supply Chain Security, attack surface mapping, risk prioritization.","https:\u002F\u002Fgithub.com\u002Freikiplanet\u002Fdaoskills\u002Fblob\u002Fmaster\u002Fskills\u002Fsecurity\u002Fvulnerability-scanner\u002FSKILL.md",[],[155,156,157,158,159,160,161,162,34,91,85,163,86,164,165,166,167,168,169,170],"scanner","vulnerability scanner","vulnerability","prioritization","2025","mapping","chain","supply chain","Bash","analysis","risk","owasp","supply chain security","security","supply","advanced",{"skillNo":172,"name":173,"nameZh":6,"description":174,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":175,"categories":176,"keywords":177,"publishedAt":43},"01M6G60JZBB8DK0W3DSG1WNMZK","threat-modeling-expert","Expert in threat modeling methodologies, security architecture review, and risk assessment. Masters STRIDE, PASTA, attack trees, and security requirement extraction. Use for security architecture r...","https:\u002F\u002Fgithub.com\u002Freikiplanet\u002Fdaoskills\u002Fblob\u002Fmaster\u002Fskills\u002Fsecurity\u002Fthreat-modeling-expert\u002FSKILL.md",[],[178,179,180,181,182,183,184,185,168,125,186,187,188,34,189,190,191,165,192,193],"modeling","threat modeling expert","threat modeling","expert","threat","risk assessment","architecture review","architecture","security architecture review","trees","security architecture","security requirement extraction","assessment","extraction","review","stride"]