Clarify connects to the rest of your stack several ways, from no-code automation to a full API. This playbook maps each option to what you're trying to do.
Automate inside Clarify: agents
Start here for automation that lives in Clarify - background workers that update records, route leads, and post recaps on a trigger, with no external setup.
No-code automation: Zapier
Connect Clarify to 7,000+ apps without writing code. Trigger a Zap when a record is created, updated, or added to a list, and create, update, or find records - or pull a meeting transcript into another tool.
Use Clarify from your AI assistant: MCP
The Clarify MCP connects your CRM to Claude, ChatGPT, and other AI assistants, so you can query and update Clarify in plain language from those tools.
Bring your tools into Rep: Rep connectors
The reverse direction - let Rep use external tools like Linear, Notion, Outreach, Stripe, and Slack (or any custom MCP server) from inside a Clarify conversation. Available to every workspace.
Build a custom integration: the API
For a fully custom integration, the Clarify API exposes records, workspace users, and meeting data. It's generally available on every plan — workspace admins create API keys in Settings → Workspace → API keys, and the developer guides live at developer.clarify.ai/docs.
Which should I use?
Automation with no external tools - agents
Connecting to another SaaS app, no code - Zapier
Working from Claude or ChatGPT - Clarify MCP
Want Rep to use your other tools - Rep connectors
Building something custom in code - the API
Good to know
MCP and Rep connectors point in opposite directions. The Clarify MCP lets external AI tools read and update Clarify; Rep connectors let Rep reach out to your external tools.
API keys are workspace-level and Admin-only - Members need an admin to create one. Access to meeting and recording data follows your workspace's email and meeting visibility settings.