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 (RUBESEARCHTOOLS available)
• Active Pipedrive connection via RUBEMANAGECONNECTIONS with toolkit pipedrive
• Always call RUBESEARCHTOOLS 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.

1. Verify Rube MCP is available by confirming RUBESEARCHTOOLS responds
2. Call RUBEMANAGECONNECTIONS with toolkit pipedrive
3. If connection is not ACTIVE, follow the returned auth link to complete Pipedrive OAuth
4. 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:

1. PIPEDRIVESEARCHORGANIZATIONS - Find existing org to link to the deal [Optional]
2. PIPEDRIVEADDAN_ORGANIZATION - Create organization if none found [Optional]
3. PIPEDRIVESEARCHPERSONS - Find existing contact to link [Optional]
4. PIPEDRIVEADDA_PERSON - Create contact if none found [Optional]
5. PIPEDRIVEGETALL_PIPELINES - Resolve pipeline ID [Prerequisite]
6. PIPEDRIVEGETALL_STAGES - Resolve stage ID within the pipeline [Prerequisite]
7. PIPEDRIVEADDADEAL - Create the deal with title, value, orgid, personid, stageid [Required]
8. PIPEDRIVEUPDATEA_DEAL - Modify deal properties after creation [Optional]
9. PIPEDRIVEADDAPRODUCTTOADEAL - 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")
• pipelineid / stageid: Numeric IDs for pipeline placement
• orgid / personid: Link to organization and contact
• status: "open", "won", or "lost"
• expectedclosedate: Format YYYY-MM-DD

Pitfalls:

• title is the only required field for PIPEDRIVEADDA_DEAL; all others are optional
• Custom fields appear as long hash keys in responses; use dealFields endpoint to map them
• PIPEDRIVEUPDATEA_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:

1. PIPEDRIVESEARCHPERSONS - Search for existing person by name, email, or phone [Prerequisite]
2. PIPEDRIVEADDA_PERSON - Create new contact if not found [Required]
3. PIPEDRIVEUPDATEA_PERSON - Modify existing contact details [Optional]
4. PIPEDRIVEGETDETAILSOFA_PERSON - Retrieve full contact record [Optional]
5. PIPEDRIVESEARCHORGANIZATIONS - Search for existing organization [Prerequisite]
6. PIPEDRIVEADDAN_ORGANIZATION - Create new organization if not found [Required]
7. PIPEDRIVEUPDATEAN_ORGANIZATION - Modify organization properties [Optional]
8. PIPEDRIVEGETDETAILSOFAN_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 SEARCHPERSONS / SEARCHORGANIZATIONS (minimum 2 characters)

Pitfalls:

• PIPEDRIVEADDANORGANIZATION may auto-merge with an existing org; check response.additionaldata.didMerge
• Email and phone fields are arrays of objects, not plain strings: [{"value": "[email protected]", "label": "work", "primary": true}]
• PIPEDRIVESEARCHPERSONS wildcards like * or @ are NOT supported; use PIPEDRIVEGETALL_PERSONS to list all
• Deletion via PIPEDRIVEDELETEAPERSON or PIPEDRIVEDELETEANORGANIZATION 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:

1. PIPEDRIVESEARCHPERSONS or PIPEDRIVEGETDETAILSOFA_DEAL - Resolve linked entity IDs [Prerequisite]
2. PIPEDRIVEADDAN_ACTIVITY - Create the activity with subject, type, due date [Required]
3. PIPEDRIVEUPDATEAN_ACTIVITY - Modify activity details or mark as done [Optional]
4. PIPEDRIVEGETDETAILSOFAN_ACTIVITY - Retrieve activity record [Optional]
5. PIPEDRIVEGETALLACTIVITIESASSIGNEDTOAPARTICULARUSER - 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)
• dealid / personid / org_id: Link to related entities
• done: 0 = not done, 1 = done

Pitfalls:

• Both subject and type are required for PIPEDRIVEADDAN_ACTIVITY
• type must match an existing ActivityTypes key_string in the account
• done is an integer (0 or 1), not a boolean
• Response includes moreactivitiesscheduledincontext 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:

1. PIPEDRIVESEARCHPERSONS or PIPEDRIVEGETDETAILSOFA_DEAL - Resolve entity ID [Prerequisite]
2. PIPEDRIVEADDA_NOTE - Create note with HTML content linked to an entity [Required]
3. PIPEDRIVEUPDATEA_NOTE - Modify note content [Optional]
4. PIPEDRIVEGETALL_NOTES - List notes filtered by entity [Optional]
5. PIPEDRIVEGETALLCOMMENTSFORANOTE - Retrieve comments on a note [Optional]

Key parameters:

• content: Note body in HTML format (required)
• dealid / personid / orgid / leadid / project_id: At least one entity link required
• pinnedtodealflag / pinnedtopersonflag: Filter pinned notes when listing

Pitfalls:

• content is required and supports HTML; plain text works but is sanitized server-side
• At least one of dealid, personid, orgid, leadid, or project_id must be provided
• PIPEDRIVEGETALL_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:

1. PIPEDRIVEGETALL_PIPELINES - List all pipelines and their IDs [Required]
2. PIPEDRIVEGETONE_PIPELINE - Get details and deal summary for a specific pipeline [Optional]
3. PIPEDRIVEGETALL_STAGES - List all stages, optionally filtered by pipeline [Required]
4. PIPEDRIVEGETONE_STAGE - Get details for a specific stage [Optional]
5. PIPEDRIVEGETDEALSINA_PIPELINE - List all deals across stages in a pipeline [Optional]
6. PIPEDRIVEGETDEALSINA_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
• totalsconvertcurrency: 3-letter currency code or "default_currency" for converted totals
• get_summary: Set to 1 for deal summary in pipeline responses

Pitfalls:

• PIPEDRIVEGETALL_PIPELINES takes no parameters; returns all pipelines
• PIPEDRIVEGETALLSTAGES returns stages for ALL pipelines unless pipelineid is specified
• Deal counts in pipeline summaries use perstagesconverted only when totalsconvertcurrency is set

Common Patterns

ID Resolution

Always resolve display names to numeric IDs before operations:

• Organization name -> orgid: PIPEDRIVESEARCH_ORGANIZATIONS with term param
• Person name -> personid: PIPEDRIVESEARCH_PERSONS with term param
• Pipeline name -> pipelineid: PIPEDRIVEGETALLPIPELINES then match by name
• Stage name -> stageid: PIPEDRIVEGETALLSTAGES with pipeline_id then match by name

Pagination

Most list endpoints use offset-based pagination:

• Use start (offset) and limit (page size) parameters
• Check additionaldata.pagination.moreitemsincollection to know if more pages exist
• Use additionaldata.pagination.nextstart 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
• PIPEDRIVEGETALLPERSONS and PIPEDRIVEGETALLORGANIZATIONS 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
• PIPEDRIVESEARCHPERSONS 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

When to Use

This skill is applicable to execute the workflow or actions described in the overview.

Example

User request:

Automate Pipedrive CRM operations including deals, contacts, organizations, activities, notes, and pipeline management via Rube MCP (Composio).

Limitations

• Use this skill only when the task clearly matches the scope described above.
• Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
• Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.