Pipedrive
Manage Pipedrive deals, persons, organizations, activities, notes and leads.
About
Pipedrive ships in the w6w first-party pack. It declares 14 actions, 2 health checks, and the host runs its code in a sandbox that never sees the credential.
- App id
io.w6w.pipedrive- Version
- 0.1.3
- Author
- w6w
- Licence
- MIT
- Categories
- Customer Relationship Management
Overview
Pipedrive brings core CRM data into a workflow — deals, people, organizations, activities, notes and leads — across the six resources a sales process touches most. Deal actions create, read, update and delete deals, with a dedicated bulk-read action for pulling many at once, while person and organization actions manage the contacts and companies behind those deals.
Activity and note actions let a workflow log a scheduled task or a piece of context against a deal or contact, and a lead action creates a new lead before it has been qualified into a full deal.
This is a focused CRUD surface on Pipedrive’s most-used resources — search endpoints, file attachments and Pipedrive’s own webhook triggers are deliberately left out, keeping the action set to the operations a sales workflow reaches for most often.
Build with Pipedrive
Three routes to the same 14 actions. The Workflow tab is generated from Pipedrive's own manifest and carries its real ids, so it is copy-pasteable; the Code and CLI examples are the same call for any action on any app, so every app-specific value in them is a blank you fill in.
Create Activity
activity-create Create a new activity and optionally link it to a deal, person or organization.
Get Many Deals
deal-get-many List deals, optionally filtered by status, owner, stage or a saved filter.
Get Many Organizations
organization-get-many List organizations, optionally filtered by owner, saved filter or first character.
Get Many Persons
person-get-many List persons, optionally filtered by owner, saved filter or first character.
A workflow step names the app and the action, and the editor fills in the
connection when you pick one. This is the Step shape from the
workflow spec, carrying Pipedrive's real ids.
{
"manifestVersion": "2",
"name": "pipedrive-example",
"steps": [
{
"id": "activity-create",
"uses": {
"app": "io.w6w.pipedrive",
"action": "activity-create",
"connection": "conn_YOUR_CONNECTION_ID"
},
"with": {
"subject": "<subject>",
"type": "<type>"
}
}
]
}Here are some of the things you can do
-
Create Activity
performactivity-create -
Create Deal
performdeal-create -
Get Deal
readdeal-get -
Get Many Deals
readdeal-get-many -
Update Deal
performdeal-update
+9 more actions available
Every app-specific value here is a blank you have to fill in. An
app action is reached through the connection that authenticates it, so the
address is a connection id, not the app id — and connections belong to your account,
so a public page cannot know yours. Create one for Pipedrive, then fill in
the three blanks: conn_YOUR_CONNECTION_ID, the action key, and the
parameters that action declares. The call itself is real — the shape is transcribed
from the studio's own snippet builder, which prints the same kind of blanks — but
nothing in it is specific to Pipedrive. The Workflow tab is where this app's
real ids are.
npm install @w6w/sdkyarn add @w6w/sdkpnpm add @w6w/sdkdeno add npm:@w6w/sdkimport { W6wClient, isActionRun } from "@w6w/sdk";
// Reads W6W_BASE_URL and W6W_TOKEN from the environment when omitted.
const client = new W6wClient();
const envelope = await client.run({
urn: "conn_YOUR_CONNECTION_ID",
action: "deal-create",
payload: {
title: "<value>",
// value: "<value>",
// currency: "<value>",
// userId: "<value>",
// personId: "<value>",
// orgId: "<value>",
// pipelineId: "<value>",
// stageId: "<value>",
// status: "<value>",
// expectedCloseDate: "<value>",
// probability: "<value>",
// visibleTo: "<value>",
},
});
if (isActionRun(envelope)) console.log(envelope.value);npm install -g @w6w/cliw6w run conn_YOUR_CONNECTION_ID --action deal-create --payload '{"title":"<value>"}'Give an AI agent Pipedrive — without giving it Pipedrive's credentials. One MCP endpoint exposes every app, function and workflow the caller is entitled to, as tools it can discover and run. Access is granted per team while we onboard.
One tool call{
"name": "w6w_invoke",
"arguments": {
"ref": "app:io.w6w.pipedrive#activity-create",
"input": {
"subject": "<subject>",
"type": "<type>"
}
}
}
Every tool names its target with a single ref. The
app: form above doesn't name a connection at all — the
host resolves which of the caller's Pipedrive connections to sign
with, and refuses rather than guesses when the answer is ambiguous.
What the agent gets
Credentials it can't read
The token is attached host-side, at the moment of the call. It is never a tool argument, never in the model's context, and never in a transcript — so a prompt injection has nothing to exfiltrate.
A tool surface scoped to the caller
Tools are derived per end user from what that person has actually connected and is entitled to — not one shared bot identity carrying the union of everyone's access.
A durable workflow in one call
Multi-step work runs on the workflow engine and returns a run handle the agent can poll — retries, branching and state survive the conversation that started them.
Health-aware discovery
Pipedrive's declared health checks are on the surface too, so an agent can tell "the vendor is down" from "your credential expired" before it burns a retry on either.
The MCP surface is part of the hosted platform. Pipedrive itself is MIT, and the runtime that executes it is source-available (FSL).
Health checks
Pipedrive declares its own checks, so its health is a property of the app rather than something the host guesses at.
Pipedrive platform status
API rate-limit headroom
Per-2-second burst and daily token-budget allowances remaining, read off the `x-ratelimit-*` and `x-daily-requests-left` response headers.