Checked 31 August 2026
The Clarify API, MCP and Zapier, and which one you want
Three ways to reach Clarify programmatically, and picking the wrong one costs you a rebuild rather than an afternoon. The short version: Zapier for rules, webhooks for events, the API when the mapping has judgement in it. MCP is a fourth thing entirely and it is not automation.
Two key types, and the difference is not permissions
It is identity, which changes what the key can read.
Personal key
Acts on your behalf and reaches exactly the data you can see in Clarify. Any workspace member can create one. This is the type MCP needs, because the assistant is standing in for you.
Workspace key
A shared key scoped to the workspace's public data. It carries no user identity, which changes what meeting and email data it can read. Admins only.
That last clause is the one that bites. A workspace key is the obvious choice for a server side integration, and then the meeting data you expected is thinner than it looked in the UI, because the UI was showing you things your own identity grants. Test the read you actually need before building on it.
Keys live in Settings, Workspace, API keys. The key is shown once and never again. If the type dropdown is missing, only one type is available to your role: members get Personal, and admins on a workspace where Personal is not yet switched on get Workspace.
Source: docs.clarify.ai, Clarify API, read 31 August 2026.
Which one to reach for
Zapier, when the rule fits in a sentence
Three triggers: New Record Created, Record Updated, and Record Added to List. Twelve actions, including create, update, delete, labels, comments, four search actions, and Get Meeting Recording Transcript, which is the one people miss.
The app is on version 2.1.2 and authenticates through WorkOS. It asks for your workspace slug, meaning
Minutes, no codeacmerather than "Acme Inc.", and one connection covers one workspace.Webhooks, when something else has to react in real time
Outbound HTTP events to any endpoint you control. Use this instead of Zapier the moment you have more than a handful of rules, or when a missed event matters, because a pile of Zaps is a pile of things to maintain.
A day, needs somewhere to receiveThe API, when the mapping is genuinely yours
Read and write records, People, Companies, Deals and Custom Objects, plus workspace users and meeting data. This is the right answer when field mapping carries business logic rather than being a copy.
Scoped per caseMCP, which is not automation at all
It lets Claude, ChatGPT and other assistants query and act on your CRM in conversation. It runs when a person asks it to, so it is a working surface rather than a pipeline. Do not design a scheduled process around it.
Setup in minutes
Sources: Zapier, Clarify API and Clarify MCP, all read 31 August 2026.
Two directions people confuse
Both involve MCP and they point opposite ways.
Your assistant reaches into Clarify
The Clarify connector sits in Claude's connector directory. Add it, authenticate, and you can ask what deals to focus on this week or have it turn today's meetings into follow up tasks.
Needs a Personal key. On a Claude Business plan a workspace admin has to add the connector first.
Clarify's agent reaches into your tools
The other way round. Connect Linear, Notion, Stripe, Apollo, Intercom or Outreach and Rep uses them from inside a Clarify conversation, with your permissions.
Each person connects their own account through OAuth, and any MCP server can be added as a custom connector.
Common questions
Does Clarify have a REST API?
Yes, read and write, covering records (People, Companies, Deals and Custom Objects), workspace users and meeting data. Keys are created in Settings, Workspace, API keys.
Personal key or Workspace key?
Personal acts as you and sees what you see, and is what MCP requires. Workspace is shared, admin created, and scoped to public workspace data with no user identity, which reduces what meeting and email data it can read. Choose on identity, not on convenience.
Does Clarify have Zapier triggers, or only actions?
Triggers as well: New Record Created, Record Updated, and Record Added to List. That matters, because a CRM with actions but no triggers can only be written to, never reacted to.
Can I get meeting transcripts out programmatically?
Yes. There is a Get Meeting Recording Transcript action in Zapier, and meeting data is reachable through the API. Note the Workspace key caveat above if the transcripts come back thinner than expected.
What is my workspace slug?
The short identifier rather than the display name, so acme and not
"Acme Inc.". Zapier asks for it during authentication and one connection maps to
one workspace, so multiple workspaces need multiple connections.
Are there webhooks?
Yes, outbound HTTP webhooks to push and receive real time events. This is the piece to design around if you want other systems reacting to Clarify rather than polling it.
Where we come in
We build the integration you would otherwise maintain forever
Zapier is the right answer more often than engineers expect and the wrong one more often than operators expect. We pick the level that matches how much judgement the mapping actually carries, then build it.
- The right key type chosen on identity rather than convenience
- Zapier where a rule fits in a sentence, and code where it does not
- Webhooks so other systems react instead of polling
- The whole thing documented, so it survives you being on holiday
Free, no call required
The Clarify setup guide
Not ready to talk to anyone? Take this instead. One email, nothing else unless you ask for it.