Integrations & API
Plugs into what you already run.
Context in. Actions out. Your code in the loop.
Buzz reads from your tools through MCP, writes back through the same connectors, and everything it does is reachable from a typed API — so Buzzer fits your stack instead of replacing it.
Connectors, via MCP
Anything with an MCP server is a tool Buzz can use: Stripe, Linear, GitHub, HubSpot, Notion, your own. Each tool is switched on per agent, and gated by who’s asking.
REST API & SDK
Conversations, messages, contacts, companies, knowledge — all behind scoped API keys, with an OpenAPI spec and a zero-dependency TypeScript SDK.
curl https://app.usebuzzer.com/api/v1/conversations \
-H "Authorization: Bearer bzk_live_…"
{ "items": [{ "id": "c_2381", "status": "open",
"subject": "Duplicate seat on invoice", … }] }Buzzer as an MCP server
Point Claude, Cursor or your own agent at Buzzer and ask questions about your customers in plain language. OAuth-scoped, read-only, workspace-bound.
// claude_desktop_config.json
"buzzer": {
"url": "https://app.usebuzzer.com/api/mcp"
}
> "Which enterprise customers wrote in
about SSO this week?"Connect the tools you run.
Channels in, context in, fixes out.
Channels
Where your customers already are.
Live chat
Our widget on your site and in your app.
Email
Forward support@ and reply from the inbox.
Slack
Mention Buzz in a channel; it answers in the thread.
WhatsAppComing soon
Business messages in the same queue.
Context
What Buzz reads before it drafts.
Stripe
Plan, invoices, and failed payments on the thread.
HubSpot
Deal stage and owner next to every contact.
Shopify
Orders and fulfilment status inline.
Notion
Internal docs as a knowledge source.
Intercom
Import your history and help centre.
BigQuery
Usage data when the answer lives in a warehouse.
Engineering
Close the loop with the people who fix things.
Linear
File and follow issues from a conversation.
GitHub
Link PRs; notify customers when they ship.
Sentry
Match reports to errors automatically.
Jira
Same loop, for teams on Atlassian.
Vercel
Deploy status when someone asks “is it fixed?”
Not on the list? If it has an MCP server or an API, it’s a connector. Add it by URL.
API
Everything in the inbox, in your code.
Scoped keys. Typed clients. Real docs.
Sync conversations to your warehouse, create contacts from your signup flow, search the knowledge base from your own app. The API is the same one our inbox uses.
Scoped API keys
Read or write, per resource. Rotate without downtime.
OpenAPI + TypeScript SDK
Generated from the same schemas the server validates with.
Rate limits you can see
Separate budgets for reads and writes, returned in headers.
import { createBuzzerApiClient } from '@usebuzzer/sdk'
const buzzer = createBuzzerApiClient({ apiKey: process.env.BUZZER_KEY })
// Create the contact when they sign up…
await buzzer.contacts.create({
email: 'elena@globex.com',
attributes: { plan: 'enterprise', seats: 40 },
})
// …and search the docs from your own app.
const hits = await buzzer.kb.search({ q: 'webhook retries' })POST https://hooks.acme.com/buzzer
X-Buzzer-Signature: sha256=…
{
"type": "conversation.resolved",
"conversation": { "id": "c_2381", "labels": ["billing"] },
"resolution": "Refunded duplicate seat",
"customer": { "id": "p_elena", "company": "Globex" }
}Webhooks
Know when things happen.
Signed, retried, yours to route.
Subscribe to the events that matter — a conversation resolved, a label added, a rating left, a feature request filed — and trigger whatever you like on your side. Or feed them straight back into a custom agent.
Every webhook is also an agent trigger. Custom agents
Lloyd Humphreys
Founder, Buzzer
Bring your stack.
Thirty minutes. Tell us what Buzz should be able to see and we’ll wire it up live.
Book 30 minutes with Lloyd