Pipedrive Automation via Rube MCP
Automate Pipedrive CRM workflows including deal management, contact and organization operations, activity scheduling, notes, and pipeline/stage queries through Composio's Pipedrive toolkit.
Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Pipedrive connection via
RUBE_MANAGE_CONNECTIONS with toolkit pipedrive
- Always call
RUBE_SEARCH_TOOLS first to get current tool schemas
Setup
Get Rube MCP: Add https://rube.app/mcp as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.
- Verify Rube MCP is available by confirming
RUBE_SEARCH_TOOLS responds
- Call
RUBE_MANAGE_CONNECTIONS with toolkit pipedrive
- If connection is not ACTIVE, follow the returned auth link to complete Pipedrive OAuth
- Confirm connection status shows ACTIVE before running any workflows
Core Workflows
1. Create and Manage Deals
When to use: User wants to create a new deal, update an existing deal, or review deal details in the sales pipeline.
Tool sequence:
PIPEDRIVE_SEARCH_ORGANIZATIONS - Find existing org to link to the deal [Optional]
PIPEDRIVE_ADD_AN_ORGANIZATION - Create organization if none found [Optional]
PIPEDRIVE_SEARCH_PERSONS - Find existing contact to link [Optional]
PIPEDRIVE_ADD_A_PERSON - Create contact if none found [Optional]
PIPEDRIVE_GET_ALL_PIPELINES - Resolve pipeline ID [Prerequisite]
PIPEDRIVE_GET_ALL_STAGES - Resolve stage ID within the pipeline [Prerequisite]
PIPEDRIVE_ADD_A_DEAL - Create the deal with title, value, org_id, person_id, stage_id [Required]
PIPEDRIVE_UPDATE_A_DEAL - Modify deal properties after creation [Optional]
PIPEDRIVE_ADD_A_PRODUCT_TO_A_DEAL - Attach line items/products [Optional]
Key parameters:
title: Deal title (required for creation)
value: Monetary value of the deal
currency: 3-letter ISO currency code (e.g., "USD")
pipeline_id / stage_id: Numeric IDs for pipeline placement
org_id / person_id: Link to organization and contact
status: "open", "won", or "lost"
expected_close_date: Format YYYY-MM-DD
Pitfalls:
title is the only required field for PIPEDRIVE_ADD_A_DEAL; all others are optional
- Custom fields appear as long hash keys in responses; use dealFields endpoint to map them
PIPEDRIVE_UPDATE_A_DEAL requires the numeric id of the deal
- Setting
status to "lost" requires also providing lost_reason
2. Manage Contacts (Persons and Organizations)
When to use: User wants to create, update, search, or list contacts and companies in Pipedrive.
Tool sequence:
PIPEDRIVE_SEARCH_PERSONS - Search for existing person by name, email, or phone [Prerequisite]
PIPEDRIVE_ADD_A_PERSON - Create new contact if not found [Required]
PIPEDRIVE_UPDATE_A_PERSON - Modify existing contact details [Optional]
PIPEDRIVE_GET_DETAILS_OF_A_PERSON - Retrieve full contact record [Optional]
PIPEDRIVE_SEARCH_ORGANIZATIONS - Search for existing organization [Prerequisite]
PIPEDRIVE_ADD_AN_ORGANIZATION - Create new organization if not found [Required]
PIPEDRIVE_UPDATE_AN_ORGANIZATION - Modify organization properties [Optional]
PIPEDRIVE_GET_DETAILS_OF_AN_ORGANIZATION - Retrieve full org record [Optional]
Key parameters:
name: Required for both person and organization creation
email: Array of objects with value, label, primary fields for persons
phone: Array of objects with value, label, primary fields for persons
org_id: Link a person to an organization
visible_to: 1 = owner only, 3 = entire company
term: Search term for SEARCH_PERSONS / SEARCH_ORGANIZATIONS (minimum 2 characters)
Pitfalls:
PIPEDRIVE_ADD_AN_ORGANIZATION may auto-merge with an existing org; check response.additional_data.didMerge
- Email and phone fields are arrays of objects, not plain strings:
[{"value": "test@example.com", "label": "work", "primary": true}]
PIPEDRIVE_SEARCH_PERSONS wildcards like * or @ are NOT supported; use PIPEDRIVE_GET_ALL_PERSONS to list all
- Deletion via
PIPEDRIVE_DELETE_A_PERSON or PIPEDRIVE_DELETE_AN_ORGANIZATION is soft-delete with 30-day retention, then permanent
3. Schedule and Track Activities
When to use: User wants to create calls, meetings, tasks, or other activities linked to deals, contacts, or organizations.
Tool sequence:
PIPEDRIVE_SEARCH_PERSONS or PIPEDRIVE_GET_DETAILS_OF_A_DEAL - Resolve linked entity IDs [Prerequisite]
PIPEDRIVE_ADD_AN_ACTIVITY - Create the activity with subject, type, due date [Required]
PIPEDRIVE_UPDATE_AN_ACTIVITY - Modify activity details or mark as done [Optional]
PIPEDRIVE_GET_DETAILS_OF_AN_ACTIVITY - Retrieve activity record [Optional]
PIPEDRIVE_GET_ALL_ACTIVITIES_ASSIGNED_TO_A_PARTICULAR_USER - List user's activities [Optional]
Key parameters:
subject: Activity title (required)
type: Activity type key string, e.g., "call", "meeting", "task", "email" (required)
due_date: Format YYYY-MM-DD
due_time: Format HH:MM
duration: Format HH:MM (e.g., "00:30" for 30 minutes)
deal_id / person_id / org_id: Link to related entities
done: 0 = not done, 1 = done
Pitfalls:
- Both
subject and type are required for PIPEDRIVE_ADD_AN_ACTIVITY
type must match an existing ActivityTypes key_string in the account
done is an integer (0 or 1), not a boolean
- Response includes
more_activities_scheduled_in_context in additional_data
4. Add and Manage Notes
When to use: User wants to attach notes to deals, persons, organizations, leads, or projects.
Tool sequence:
PIPEDRIVE_SEARCH_PERSONS or PIPEDRIVE_GET_DETAILS_OF_A_DEAL - Resolve entity ID [Prerequisite]
PIPEDRIVE_ADD_A_NOTE - Create note with HTML content linked to an entity [Required]
PIPEDRIVE_UPDATE_A_NOTE - Modify note content [Optional]
PIPEDRIVE_GET_ALL_NOTES - List notes filtered by entity [Optional]
PIPEDRIVE_GET_ALL_COMMENTS_FOR_A_NOTE - Retrieve comments on a note [Optional]
Key parameters:
content: Note body in HTML format (required)
deal_id / person_id / org_id / lead_id / project_id: At least one entity link required
pinned_to_deal_flag / pinned_to_person_flag: Filter pinned notes when listing
Pitfalls:
content is required and supports HTML; plain text works but is sanitized server-side
- At least one of
deal_id, person_id, org_id, lead_id, or project_id must be provided
PIPEDRIVE_GET_ALL_NOTES returns notes across all entities by default; filter with entity ID params
5. Query Pipelines and Stages
When to use: User wants to view sales pipelines, stages, or deals within a pipeline/stage.
Tool sequence:
PIPEDRIVE_GET_ALL_PIPELINES - List all pipelines and their IDs [Required]
PIPEDRIVE_GET_ONE_PIPELINE - Get details and deal summary for a specific pipeline [Optional]
PIPEDRIVE_GET_ALL_STAGES - List all stages, optionally filtered by pipeline [Required]
PIPEDRIVE_GET_ONE_STAGE - Get details for a specific stage [Optional]
PIPEDRIVE_GET_DEALS_IN_A_PIPELINE - List all deals across stages in a pipeline [Optional]
PIPEDRIVE_GET_DEALS_IN_A_STAGE - List deals in a specific stage [Optional]
Key parameters:
id: Pipeline or stage ID (required for single-item endpoints)
pipeline_id: Filter stages by pipeline
totals_convert_currency: 3-letter currency code or "default_currency" for converted totals
get_summary: Set to 1 for deal summary in pipeline responses
Pitfalls:
PIPEDRIVE_GET_ALL_PIPELINES takes no parameters; returns all pipelines
PIPEDRIVE_GET_ALL_STAGES returns stages for ALL pipelines unless pipeline_id is specified
- Deal counts in pipeline summaries use
per_stages_converted only when totals_convert_currency is set
Common Patterns
ID Resolution
Always resolve display names to numeric IDs before operations:
- Organization name -> org_id:
PIPEDRIVE_SEARCH_ORGANIZATIONS with term param
- Person name -> person_id:
PIPEDRIVE_SEARCH_PERSONS with term param
- Pipeline name -> pipeline_id:
PIPEDRIVE_GET_ALL_PIPELINES then match by name
- Stage name -> stage_id:
PIPEDRIVE_GET_ALL_STAGES with pipeline_id then match by name
Pagination
Most list endpoints use offset-based pagination:
- Use
start (offset) and limit (page size) parameters
- Check
additional_data.pagination.more_items_in_collection to know if more pages exist
- Use
additional_data.pagination.next_start as the start value for the next page
- Default limit is ~500 for some endpoints; set explicitly for predictable paging
Known Pitfalls
ID Formats
- All entity IDs (deal, person, org, activity, pipeline, stage) are numeric integers
- Lead IDs are UUID strings, not integers
- Custom field keys are long alphanumeric hashes (e.g., "a1b2c3d4e5f6...")
Rate Limits
- Pipedrive enforces per-company API rate limits; bulk operations should be paced
PIPEDRIVE_GET_ALL_PERSONS and PIPEDRIVE_GET_ALL_ORGANIZATIONS can return large datasets; always paginate
Parameter Quirks
- Email and phone on persons are arrays of objects, not plain strings
visible_to is numeric: 1 = owner only, 3 = entire company, 5 = specific groups
done on activities is integer 0/1, not boolean true/false
- Organization creation may auto-merge duplicates silently; check
didMerge in response
PIPEDRIVE_SEARCH_PERSONS requires minimum 2 characters and does not support wildcards
Response Structure
- Custom fields appear as hash keys in responses; map them via the respective Fields endpoints
- Responses often nest data under
response.data.data in wrapped executions
- Search results are under
response.data.items, not top-level
Quick Reference
| Task |
Tool Slug |
Key Params |
| Create deal |
PIPEDRIVE_ADD_A_DEAL |
title, value, org_id, stage_id |
| Update deal |
PIPEDRIVE_UPDATE_A_DEAL |
id, status, value, stage_id |
| Get deal details |
PIPEDRIVE_GET_DETAILS_OF_A_DEAL |
id |
| Search persons |
PIPEDRIVE_SEARCH_PERSONS |
term, fields |
| Add person |
PIPEDRIVE_ADD_A_PERSON |
name, email, phone, org_id |
| Update person |
PIPEDRIVE_UPDATE_A_PERSON |
id, name, email |
| Get person details |
PIPEDRIVE_GET_DETAILS_OF_A_PERSON |
id |
| List all persons |
PIPEDRIVE_GET_ALL_PERSONS |
start, limit, filter_id |
| Search organizations |
PIPEDRIVE_SEARCH_ORGANIZATIONS |
term, fields |
| Add organization |
PIPEDRIVE_ADD_AN_ORGANIZATION |
name, visible_to |
| Update organization |
PIPEDRIVE_UPDATE_AN_ORGANIZATION |
id, name, address |
| Get org details |
PIPEDRIVE_GET_DETAILS_OF_AN_ORGANIZATION |
id |
| Add activity |
PIPEDRIVE_ADD_AN_ACTIVITY |
subject, type, due_date, deal_id |
| Update activity |
PIPEDRIVE_UPDATE_AN_ACTIVITY |
id, done, due_date |
| Get activity details |
PIPEDRIVE_GET_DETAILS_OF_AN_ACTIVITY |
id |
| List user activities |
PIPEDRIVE_GET_ALL_ACTIVITIES_ASSIGNED_TO_A_PARTICULAR_USER |
user_id, start, limit |
| Add note |
PIPEDRIVE_ADD_A_NOTE |
content, deal_id or person_id |
| List notes |
PIPEDRIVE_GET_ALL_NOTES |
deal_id, person_id, start, limit |
| List pipelines |
PIPEDRIVE_GET_ALL_PIPELINES |
(none) |
| Get pipeline details |
PIPEDRIVE_GET_ONE_PIPELINE |
id |
| List stages |
PIPEDRIVE_GET_ALL_STAGES |
pipeline_id |
| Deals in pipeline |
PIPEDRIVE_GET_DEALS_IN_A_PIPELINE |
id, stage_id |
| Deals in stage |
PIPEDRIVE_GET_DEALS_IN_A_STAGE |
id, start, limit |
| Add product to deal |
PIPEDRIVE_ADD_A_PRODUCT_TO_A_DEAL |
id, product_id, item_price |
When to Use
This skill is applicable to execute the workflow or actions described in the overview.
🏰 Rei Skills — Curated by Rootcastle Engineering & Innovation | Batuhan Ayrıbaş
Engineering Beyond Boundaries | admin@rootcastle.com
1---2name: pipedrive-automation3description: "Automate Pipedrive CRM operations including deals, contacts, organizations, activities, notes, and pipeline management via Rube MCP (Composio). Always search tools first for current schemas."4requires:5 mcp: [rube]6risk: unknown7source: rootcastle-rei8metadata:9 source: https://skillmd.com/skills/rootcastleco/pipedrive-automation10---1112# Pipedrive Automation via Rube MCP1314Automate Pipedrive CRM workflows including deal management, contact and organization operations, activity scheduling, notes, and pipeline/stage queries through Composio's Pipedrive toolkit.1516## Prerequisites1718- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)19- Active Pipedrive connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `pipedrive`20- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas2122## Setup2324**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.2526271. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds282. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `pipedrive`293. If connection is not ACTIVE, follow the returned auth link to complete Pipedrive OAuth304. Confirm connection status shows ACTIVE before running any workflows3132## Core Workflows3334### 1. Create and Manage Deals3536**When to use**: User wants to create a new deal, update an existing deal, or review deal details in the sales pipeline.3738**Tool sequence**:391. `PIPEDRIVE_SEARCH_ORGANIZATIONS` - Find existing org to link to the deal [Optional]402. `PIPEDRIVE_ADD_AN_ORGANIZATION` - Create organization if none found [Optional]413. `PIPEDRIVE_SEARCH_PERSONS` - Find existing contact to link [Optional]424. `PIPEDRIVE_ADD_A_PERSON` - Create contact if none found [Optional]435. `PIPEDRIVE_GET_ALL_PIPELINES` - Resolve pipeline ID [Prerequisite]446. `PIPEDRIVE_GET_ALL_STAGES` - Resolve stage ID within the pipeline [Prerequisite]457. `PIPEDRIVE_ADD_A_DEAL` - Create the deal with title, value, org_id, person_id, stage_id [Required]468. `PIPEDRIVE_UPDATE_A_DEAL` - Modify deal properties after creation [Optional]479. `PIPEDRIVE_ADD_A_PRODUCT_TO_A_DEAL` - Attach line items/products [Optional]4849**Key parameters**:50- `title`: Deal title (required for creation)51- `value`: Monetary value of the deal52- `currency`: 3-letter ISO currency code (e.g., "USD")53- `pipeline_id` / `stage_id`: Numeric IDs for pipeline placement54- `org_id` / `person_id`: Link to organization and contact55- `status`: "open", "won", or "lost"56- `expected_close_date`: Format YYYY-MM-DD5758**Pitfalls**:59- `title` is the only required field for `PIPEDRIVE_ADD_A_DEAL`; all others are optional60- Custom fields appear as long hash keys in responses; use dealFields endpoint to map them61- `PIPEDRIVE_UPDATE_A_DEAL` requires the numeric `id` of the deal62- Setting `status` to "lost" requires also providing `lost_reason`6364### 2. Manage Contacts (Persons and Organizations)6566**When to use**: User wants to create, update, search, or list contacts and companies in Pipedrive.6768**Tool sequence**:691. `PIPEDRIVE_SEARCH_PERSONS` - Search for existing person by name, email, or phone [Prerequisite]702. `PIPEDRIVE_ADD_A_PERSON` - Create new contact if not found [Required]713. `PIPEDRIVE_UPDATE_A_PERSON` - Modify existing contact details [Optional]724. `PIPEDRIVE_GET_DETAILS_OF_A_PERSON` - Retrieve full contact record [Optional]735. `PIPEDRIVE_SEARCH_ORGANIZATIONS` - Search for existing organization [Prerequisite]746. `PIPEDRIVE_ADD_AN_ORGANIZATION` - Create new organization if not found [Required]757. `PIPEDRIVE_UPDATE_AN_ORGANIZATION` - Modify organization properties [Optional]768. `PIPEDRIVE_GET_DETAILS_OF_AN_ORGANIZATION` - Retrieve full org record [Optional]7778**Key parameters**:79- `name`: Required for both person and organization creation80- `email`: Array of objects with `value`, `label`, `primary` fields for persons81- `phone`: Array of objects with `value`, `label`, `primary` fields for persons82- `org_id`: Link a person to an organization83- `visible_to`: 1 = owner only, 3 = entire company84- `term`: Search term for SEARCH_PERSONS / SEARCH_ORGANIZATIONS (minimum 2 characters)8586**Pitfalls**:87- `PIPEDRIVE_ADD_AN_ORGANIZATION` may auto-merge with an existing org; check `response.additional_data.didMerge`88- Email and phone fields are arrays of objects, not plain strings: `[{"value": "test@example.com", "label": "work", "primary": true}]`89- `PIPEDRIVE_SEARCH_PERSONS` wildcards like `*` or `@` are NOT supported; use `PIPEDRIVE_GET_ALL_PERSONS` to list all90- Deletion via `PIPEDRIVE_DELETE_A_PERSON` or `PIPEDRIVE_DELETE_AN_ORGANIZATION` is soft-delete with 30-day retention, then permanent9192### 3. Schedule and Track Activities9394**When to use**: User wants to create calls, meetings, tasks, or other activities linked to deals, contacts, or organizations.9596**Tool sequence**:971. `PIPEDRIVE_SEARCH_PERSONS` or `PIPEDRIVE_GET_DETAILS_OF_A_DEAL` - Resolve linked entity IDs [Prerequisite]982. `PIPEDRIVE_ADD_AN_ACTIVITY` - Create the activity with subject, type, due date [Required]993. `PIPEDRIVE_UPDATE_AN_ACTIVITY` - Modify activity details or mark as done [Optional]1004. `PIPEDRIVE_GET_DETAILS_OF_AN_ACTIVITY` - Retrieve activity record [Optional]1015. `PIPEDRIVE_GET_ALL_ACTIVITIES_ASSIGNED_TO_A_PARTICULAR_USER` - List user's activities [Optional]102103**Key parameters**:104- `subject`: Activity title (required)105- `type`: Activity type key string, e.g., "call", "meeting", "task", "email" (required)106- `due_date`: Format YYYY-MM-DD107- `due_time`: Format HH:MM108- `duration`: Format HH:MM (e.g., "00:30" for 30 minutes)109- `deal_id` / `person_id` / `org_id`: Link to related entities110- `done`: 0 = not done, 1 = done111112**Pitfalls**:113- Both `subject` and `type` are required for `PIPEDRIVE_ADD_AN_ACTIVITY`114- `type` must match an existing ActivityTypes key_string in the account115- `done` is an integer (0 or 1), not a boolean116- Response includes `more_activities_scheduled_in_context` in additional_data117118### 4. Add and Manage Notes119120**When to use**: User wants to attach notes to deals, persons, organizations, leads, or projects.121122**Tool sequence**:1231. `PIPEDRIVE_SEARCH_PERSONS` or `PIPEDRIVE_GET_DETAILS_OF_A_DEAL` - Resolve entity ID [Prerequisite]1242. `PIPEDRIVE_ADD_A_NOTE` - Create note with HTML content linked to an entity [Required]1253. `PIPEDRIVE_UPDATE_A_NOTE` - Modify note content [Optional]1264. `PIPEDRIVE_GET_ALL_NOTES` - List notes filtered by entity [Optional]1275. `PIPEDRIVE_GET_ALL_COMMENTS_FOR_A_NOTE` - Retrieve comments on a note [Optional]128129**Key parameters**:130- `content`: Note body in HTML format (required)131- `deal_id` / `person_id` / `org_id` / `lead_id` / `project_id`: At least one entity link required132- `pinned_to_deal_flag` / `pinned_to_person_flag`: Filter pinned notes when listing133134**Pitfalls**:135- `content` is required and supports HTML; plain text works but is sanitized server-side136- At least one of `deal_id`, `person_id`, `org_id`, `lead_id`, or `project_id` must be provided137- `PIPEDRIVE_GET_ALL_NOTES` returns notes across all entities by default; filter with entity ID params138139### 5. Query Pipelines and Stages140141**When to use**: User wants to view sales pipelines, stages, or deals within a pipeline/stage.142143**Tool sequence**:1441. `PIPEDRIVE_GET_ALL_PIPELINES` - List all pipelines and their IDs [Required]1452. `PIPEDRIVE_GET_ONE_PIPELINE` - Get details and deal summary for a specific pipeline [Optional]1463. `PIPEDRIVE_GET_ALL_STAGES` - List all stages, optionally filtered by pipeline [Required]1474. `PIPEDRIVE_GET_ONE_STAGE` - Get details for a specific stage [Optional]1485. `PIPEDRIVE_GET_DEALS_IN_A_PIPELINE` - List all deals across stages in a pipeline [Optional]1496. `PIPEDRIVE_GET_DEALS_IN_A_STAGE` - List deals in a specific stage [Optional]150151**Key parameters**:152- `id`: Pipeline or stage ID (required for single-item endpoints)153- `pipeline_id`: Filter stages by pipeline154- `totals_convert_currency`: 3-letter currency code or "default_currency" for converted totals155- `get_summary`: Set to 1 for deal summary in pipeline responses156157**Pitfalls**:158- `PIPEDRIVE_GET_ALL_PIPELINES` takes no parameters; returns all pipelines159- `PIPEDRIVE_GET_ALL_STAGES` returns stages for ALL pipelines unless `pipeline_id` is specified160- Deal counts in pipeline summaries use `per_stages_converted` only when `totals_convert_currency` is set161162## Common Patterns163164### ID Resolution165Always resolve display names to numeric IDs before operations:166- **Organization name -> org_id**: `PIPEDRIVE_SEARCH_ORGANIZATIONS` with `term` param167- **Person name -> person_id**: `PIPEDRIVE_SEARCH_PERSONS` with `term` param168- **Pipeline name -> pipeline_id**: `PIPEDRIVE_GET_ALL_PIPELINES` then match by name169- **Stage name -> stage_id**: `PIPEDRIVE_GET_ALL_STAGES` with `pipeline_id` then match by name170171### Pagination172Most list endpoints use offset-based pagination:173- Use `start` (offset) and `limit` (page size) parameters174- Check `additional_data.pagination.more_items_in_collection` to know if more pages exist175- Use `additional_data.pagination.next_start` as the `start` value for the next page176- Default limit is ~500 for some endpoints; set explicitly for predictable paging177178## Known Pitfalls179180### ID Formats181- All entity IDs (deal, person, org, activity, pipeline, stage) are numeric integers182- Lead IDs are UUID strings, not integers183- Custom field keys are long alphanumeric hashes (e.g., "a1b2c3d4e5f6...")184185### Rate Limits186- Pipedrive enforces per-company API rate limits; bulk operations should be paced187- `PIPEDRIVE_GET_ALL_PERSONS` and `PIPEDRIVE_GET_ALL_ORGANIZATIONS` can return large datasets; always paginate188189### Parameter Quirks190- Email and phone on persons are arrays of objects, not plain strings191- `visible_to` is numeric: 1 = owner only, 3 = entire company, 5 = specific groups192- `done` on activities is integer 0/1, not boolean true/false193- Organization creation may auto-merge duplicates silently; check `didMerge` in response194- `PIPEDRIVE_SEARCH_PERSONS` requires minimum 2 characters and does not support wildcards195196### Response Structure197- Custom fields appear as hash keys in responses; map them via the respective Fields endpoints198- Responses often nest data under `response.data.data` in wrapped executions199- Search results are under `response.data.items`, not top-level200201## Quick Reference202203| Task | Tool Slug | Key Params |204|------|-----------|------------|205| Create deal | `PIPEDRIVE_ADD_A_DEAL` | `title`, `value`, `org_id`, `stage_id` |206| Update deal | `PIPEDRIVE_UPDATE_A_DEAL` | `id`, `status`, `value`, `stage_id` |207| Get deal details | `PIPEDRIVE_GET_DETAILS_OF_A_DEAL` | `id` |208| Search persons | `PIPEDRIVE_SEARCH_PERSONS` | `term`, `fields` |209| Add person | `PIPEDRIVE_ADD_A_PERSON` | `name`, `email`, `phone`, `org_id` |210| Update person | `PIPEDRIVE_UPDATE_A_PERSON` | `id`, `name`, `email` |211| Get person details | `PIPEDRIVE_GET_DETAILS_OF_A_PERSON` | `id` |212| List all persons | `PIPEDRIVE_GET_ALL_PERSONS` | `start`, `limit`, `filter_id` |213| Search organizations | `PIPEDRIVE_SEARCH_ORGANIZATIONS` | `term`, `fields` |214| Add organization | `PIPEDRIVE_ADD_AN_ORGANIZATION` | `name`, `visible_to` |215| Update organization | `PIPEDRIVE_UPDATE_AN_ORGANIZATION` | `id`, `name`, `address` |216| Get org details | `PIPEDRIVE_GET_DETAILS_OF_AN_ORGANIZATION` | `id` |217| Add activity | `PIPEDRIVE_ADD_AN_ACTIVITY` | `subject`, `type`, `due_date`, `deal_id` |218| Update activity | `PIPEDRIVE_UPDATE_AN_ACTIVITY` | `id`, `done`, `due_date` |219| Get activity details | `PIPEDRIVE_GET_DETAILS_OF_AN_ACTIVITY` | `id` |220| List user activities | `PIPEDRIVE_GET_ALL_ACTIVITIES_ASSIGNED_TO_A_PARTICULAR_USER` | `user_id`, `start`, `limit` |221| Add note | `PIPEDRIVE_ADD_A_NOTE` | `content`, `deal_id` or `person_id` |222| List notes | `PIPEDRIVE_GET_ALL_NOTES` | `deal_id`, `person_id`, `start`, `limit` |223| List pipelines | `PIPEDRIVE_GET_ALL_PIPELINES` | (none) |224| Get pipeline details | `PIPEDRIVE_GET_ONE_PIPELINE` | `id` |225| List stages | `PIPEDRIVE_GET_ALL_STAGES` | `pipeline_id` |226| Deals in pipeline | `PIPEDRIVE_GET_DEALS_IN_A_PIPELINE` | `id`, `stage_id` |227| Deals in stage | `PIPEDRIVE_GET_DEALS_IN_A_STAGE` | `id`, `start`, `limit` |228| Add product to deal | `PIPEDRIVE_ADD_A_PRODUCT_TO_A_DEAL` | `id`, `product_id`, `item_price` |229230## When to Use231This skill is applicable to execute the workflow or actions described in the overview.232233---234235> 🏰 **Rei Skills** — Curated by [Rootcastle Engineering & Innovation](https://www.rootcastle.com) | Batuhan Ayrıbaş 236> Engineering Beyond Boundaries | admin@rootcastle.com