Zendesk Sell
Manage contacts, leads, deals, notes and tasks in Zendesk Sell (formerly Base CRM), over the Sell API v2.
About
Zendesk Sell ships in the w6w first-party pack. It declares 31 actions, 2 health checks, and the host runs its code in a sandbox that never sees the credential.
- App id
io.w6w.zendesk-sell- Version
- 0.1.1
- Author
- w6w
- Licence
- MIT
- Categories
- Customer Relationship Management · Marketing
Overview
Zendesk Sell — the CRM product built from the acquired Base CRM (getbase.com), now sold as part of Zendesk but running on its own, entirely separate API surface from Zendesk Support. This app covers Sell’s core sales-pipeline objects: contacts (people and organizations), leads and their conversion into contacts/deals, deals, the notes and tasks attached to any of those three, and a read of the users and account behind a connection.
The Sell API is reached at api.getbase.com, not any zendesk.com host — the vendor’s old developers.getbase.com reference now redirects into Zendesk’s unified developer docs, but the wire endpoint itself never moved. Authentication is OAuth 2.0 (Authorization Code, the vendor’s own recommended “Multi-User Application” flow), with read/write/profile scopes.
Health checks track Zendesk’s own status dashboard — which does carry a dedicated Sales/Sell component (service id 63, slug “sell”), confirmed against its (undocumented) internal API rather than assumed from the page’s name — plus the derived credential check. The vendor exposes no readable per-token rate-limit headroom, so that quota is declared unavailable rather than guessed.
Build with Zendesk Sell
Three routes to the same 31 actions. The Workflow tab is generated from Zendesk Sell'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 Contact
contact-create Create a contact. Provide name for an organization, or lastName for an individual.
Upsert Contact
contact-upsert Find a contact by filter and update it, or create one if no filter matches. Prefer this over Create when a workflow might run more than once for the same contact.
Delete Deal
deal-delete Delete a deal and remove all of its associated contacts in one call. Cannot be undone.
Update Deal
deal-update Update an existing deal. Tags are replaced wholesale — supply the entire set.
Upsert Deal
deal-upsert Find a deal by filter and update it, or create one if no filter matches. Prefer this over Create when a workflow might run more than once for the same deal.
Convert Lead
lead-convert Convert a lead into a contact (individual and/or organization) and, by default, a deal.
Update Lead
lead-update Update an existing lead. Tags are replaced wholesale — supply the entire set.
Upsert Lead
lead-upsert Find a lead by filter and update it, or create one if no filter matches. Prefer this over Create when a workflow might run more than once for the same lead.
Create Task
task-create Create a floating task, or a related task attached to a lead, contact or deal.
List Tasks
task-list List tasks, optionally filtered. Returns both floating and related tasks unless narrowed.
List Users
user-list List the users on this Sell account. Read-only — Sell's Users API has no write.
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 Zendesk Sell's real ids.
{
"manifestVersion": "2",
"name": "zendesk-sell-example",
"steps": [
{
"id": "contact-get",
"uses": {
"app": "io.w6w.zendesk-sell",
"action": "contact-get",
"connection": "conn_YOUR_CONNECTION_ID"
},
"with": {
"id": "<id>"
}
}
]
}Here are some of the things you can do
-
Get Contact
readcontact-get -
Get Account
readaccount-get -
Create Contact
performcontact-create -
List Contacts
readcontact-list -
Update Contact
performcontact-update
+26 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 Zendesk Sell, 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 Zendesk Sell. 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: "contact-get",
payload: {
id: "<value>",
},
});
if (isActionRun(envelope)) console.log(envelope.value);npm install -g @w6w/cliw6w run conn_YOUR_CONNECTION_ID --action contact-get --payload '{"id":"<value>"}'Give an AI agent Zendesk Sell — without giving it Zendesk Sell'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.zendesk-sell#contact-get",
"input": {
"id": "<id>"
}
}
}
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 Zendesk Sell 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
Zendesk Sell'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. Zendesk Sell itself is MIT, and the runtime that executes it is source-available (FSL).
Health checks
Zendesk Sell declares its own checks, so its health is a property of the app rather than something the host guesses at.
Zendesk Sell platform status
Open incidents scoped to the Sales/Sell component (service id 63, slug "sell") of status.zendesk.com's incident log. See this file's module doc for why that host has no documented status API and how this check treats it defensively.