Pipedrive MCP integration for AI agents.
Connect AI agents to Pipedrive through 27 structured actions, including get activity, create activity, and delete activity. Review authentication, inputs, wo…
- ACTION CONTRACTS
- 27
- AUTHENTICATION
- API key
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the Pipedrive integration exposes
The Pipedrive Agent App exposes 27 provider-backed actions for productivity and marketing work. Its current contract lets an authorized agent get one pipedrive activity by activity id, create a pipedrive activity with schedule, attendees, participants, linked entities, and notes, and delete one pipedrive activity by activity id. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses API key. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected Pipedrive account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Pipedrive capabilities.
Showing 12 of 27 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_activityREADGet one Pipedrive activity by activity ID.
INPUTS: activityId
create_activityWRITECreate a Pipedrive activity with schedule, attendees, participants, linked entities, and notes.
delete_activityHIGH IMPACTDelete one Pipedrive activity by activity ID.
INPUTS: activityId
create_dealWRITECreate a Pipedrive deal with title, linked person or organization, value, stage, labels, and custom fields.
create_organizationWRITECreate a Pipedrive organization with address, labels, ownership, visibility, and custom fields.
create_personWRITECreate a Pipedrive person with contact values, labels, ownership, visibility, and custom fields.
delete_dealHIGH IMPACTDelete one Pipedrive deal by deal ID.
INPUTS: dealId
delete_organizationHIGH IMPACTDelete one Pipedrive organization by organization ID.
INPUTS: organizationId
delete_personHIGH IMPACTDelete one Pipedrive person by person ID.
INPUTS: personId
get_dealREADGet one Pipedrive deal by deal ID.
INPUTS: dealId
get_organizationREADGet one Pipedrive organization by organization ID.
INPUTS: organizationId
get_personREADGet one Pipedrive person by person ID.
INPUTS: personId
INPUT CONTRACTS
Know what the action needs before it runs.
get_activity
activityIdOPTIONAL- The Pipedrive activity ID to retrieve.
delete_activity
activityIdOPTIONAL- The Pipedrive activity ID to delete.
delete_deal
dealIdOPTIONAL- The Pipedrive deal ID to delete.
delete_organization
organizationIdOPTIONAL- The Pipedrive organization ID to delete.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Activity
Get one Pipedrive activity by activity ID. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_activityControl Create Activity
Create a Pipedrive activity with schedule, attendees, participants, linked entities, and notes. Resolve the target first, present material changes for confirmation, and make retries idempotent where the provider supports it.
create_activityVerify with Create Activity
Create a Pipedrive activity with schedule, attendees, participants, linked entities, and notes. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
create_activitySAFETY BOUNDARY
Operate Pipedrive with explicit limits
- Authorize Pipedrive with API key and grant only the provider access required by the selected actions.
- 12 actions are change-capable by name. Confirm the target identity and material parameters before allowing a write.
- Treat `delete_activity`, `delete_deal`, and `delete_organization` as high-impact operations and require an explicit approval boundary.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in Pipedrive rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Pipedrive task completed successfully.
CONNECTION MODEL
API key
Pipedrive API token used with the x-api-token header. Find it in Settings > Personal preferences > API: https://pipedrive.readme.io/docs/how-to-find-the-api-token
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 15
- WRITE SIGNALS
- 8
- HIGH IMPACT
- 4
- REVIEW SIGNALS
- 0
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by Pipedrive.