#INTEGRATIONS
One API.Every entry point.
Zavu is a REST API first. Everything on this page is a different door into the same surface — a typed client, a tool your agent can call, a node you drag onto a canvas, a command you type.
- Official SDKs
- 5Official SDKs
- Client resources
- 16Client resources
- n8n resources
- 11n8n resources
- Webhook events
- 17Webhook events
#THE SURFACE
Six ways in. One API behind them.
No hidden second API, no partial mirror. Each of these is generated from, or written against, the same OpenAPI spec.
SDKs
TypeScript · Python · Ruby · Go · PHP
Typed clients for the whole REST surface. Generated from the spec, so they move when the API moves.
MCP server
@zavudev/sdk-mcp
Run it locally with npx, or point a client at the hosted endpoint. Your assistant calls the API directly.
Agent skills
zavudev/zavu-skills
Thirteen skills that teach a coding agent channel selection, the WhatsApp window, webhook signatures and the deploy loop.
CLI
npx zavudev
Log in, deploy a Function, pull a factory agent, read logs. Every API resource mirrored as a command.
n8n node
n8n-nodes-zavu
A community node plus a trigger node. Eleven resources, and a Custom API Call for anything not wrapped yet.
Vercel
Marketplace integration
Provisions an API key and injects ZAVUDEV_API_KEY and ZAVU_PROJECT_ID into the projects you select.
#SDK EXPLORER
Pick a language. Read the surface.
The install line changes with the language. The resource map below is the Node client, listed exactly as it ships — including the three resources that are not generated yet.
Package
@zavudev/sdk
npm
Install
npm add @zavudev/sdk@zavudev/sdk exposes
Select a resource to see what it covers and the path it calls.
Not generated yet
These three endpoints are live, but the generator has not emitted a client for them. Call them with fetch or curl until it does — the samples below show how.
Send on any channel, then read status and attachments back.
Path · /v1/messages
#CODE
The same four jobs, in your language.
Sending, reading the inbox, wiring an agent, shipping a Function. Where the SDK has no resource yet, the sample is REST — not an invented method.
import Zavudev from "@zavudev/sdk"
const zavu = new Zavudev()
const { message } = await zavu.messages.send({
to: "+14155551234",
text: "Your order #1234 has shipped.",
})
console.log(message.id, message.channel, message.status)#AGENT SETUP
Teach your coding agent the API.
Skills give it judgment — which channel, which window, which error. The MCP server gives it hands. Pick your editor for the exact commands.
Editor
Skills that ship
Loaded on demand by what you are building. zavu-rules is always in context.
- Step 01Add the skills. The installer asks which agents to install to.
npx skills add zavudev/zavu-skills - Step 02Or install them as a plugin from the Zavu marketplace.
claude plugin marketplace add zavudev/zavu-skills claude plugin install zavu-skills@zavu-marketplace --scope user - Step 03Add the MCP server so the agent can call the API, not just describe it.
claude mcp add zavudev --scope user -e ZAVUDEV_API_KEY=<key> -- npx -y @zavudev/sdk-mcp
Verify
claude plugin list --json
claude mcp list#N8N
Drag it onto a canvas.
Two nodes. The trigger starts a workflow on a Zavu event; the action node calls a resource. Choose an event and an operation to see the wiring.
Zavu Trigger
The trigger verifies X-Zavu-Signature and rejects deliveries older than the tolerance you set.
Resource
Operation
Install
npm install n8n-nodes-zavuStart with whichever door you are standing at.
A key works everywhere on this page. Nothing here is a separate plan or a separate product.