Automate Pipedrive CRM Operations

Automates Pipedrive CRM workflows - deal management, contact and organization operations, activity scheduling, notes, and pipeline/stage queries - through Composio's Pipedrive toolkit accessed via Rube MCP.

Use this skill when creating or updating a sales deal, managing contacts and organizations, scheduling calls/meetings/tasks linked to CRM records, attaching notes to deals or contacts, or querying pipelines and stages. Not a fit for CRMs other than Pipedrive, or for tasks unrelated to CRM data management.

Setup requires Rube MCP connected, an active Pipedrive connection verified via RUBE_MANAGE_CONNECTIONS with toolkit pipedrive, OAuth completion if not active, and calling RUBE_SEARCH_TOOLS first for current schemas.

Creating and managing deals resolves organization and person IDs (searching or creating if not found), resolves pipeline and stage IDs via PIPEDRIVE_GET_ALL_PIPELINES/PIPEDRIVE_GET_ALL_STAGES, then creates the deal with title as the only required field (value, currency, org_id, person_id, stage_id, status, expected_close_date all optional) - noting that setting status to "lost" also requires lost_reason. Managing contacts covers searching before creating persons/organizations to avoid duplicates, with email/phone stored as arrays of labeled objects (not plain strings), visible_to controlling visibility (1=owner only, 3=entire company), and organization creation potentially auto-merging with an existing record (checked via response.additional_data.didMerge).

Scheduling activities requires both subject and type (call, meeting, task, email) matching an existing ActivityTypes key, with due_date/due_time/duration fields and a done flag as integer 0/1 rather than boolean. Managing notes requires HTML content plus at least one entity link (deal_id, person_id, org_id, lead_id, or project_id). Querying pipelines and stages covers listing all pipelines/stages, getting deal summaries per pipeline, and listing deals within a specific pipeline or stage, with totals_convert_currency controlling currency-converted totals.

Common patterns include resolving display names to numeric IDs before every operation (organization/person/pipeline/stage name lookups), and offset-based pagination using start/limit with additional_data.pagination.more_items_in_collection and next_start to page through results. Known pitfalls cover ID format differences (numeric IDs for most entities, UUID strings for leads, long hash keys for custom fields), per-company rate limits requiring paced bulk operations, array-typed email/phone fields, numeric visible_to/done values, silent organization auto-merge, and nested response structures (response.data.data, response.data.items).

Accessed via Rube MCP wrapping Composio's Pipedrive toolkit, covering Pipedrive's Deals, Persons, Organizations, Activities, Notes, and Pipelines/Stages APIs.

Sales operations teams automating Pipedrive CRM workflows through an MCP-connected agent who need the exact tool sequence, ID resolution steps, and parameter quirks rather than trial-and-error API calls.

PIPEDRIVE_ADD_A_DEAL: title="New Deal", value=5000, org_id=42, stage_id=3