#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 skill your agent reads, a node you drag onto a canvas, a command you type.
- Official SDK (TypeScript)
- 1Official SDK (TypeScript)
- Client resources
- 22Client 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.
SDK
TypeScript · @zavudev/sdk
A typed client, generated from the spec, so it moves when the API moves. Any other language calls the REST API directly.
REST API
api.zavu.dev
A Bearer token and JSON, from any language. The OpenAPI spec is the contract the SDK is generated from.
Agent skills
zavudev/zavu-skills
Fifteen 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
One SDK. Read the surface.
TypeScript is the official SDK. The resource map below is that client, listed exactly as it ships: every top-level resource, agents, calls and conversations included.
Package
@zavudev/sdk
npm
Install
npm add @zavudev/sdkAny other language: call https://api.zavu.dev with a Bearer token and JSON.
@zavudev/sdk exposes
Select a resource to see what it covers and the path it calls.
Send on any channel, then read status and attachments back.
Path · /v1/messages
#CODE
The same four jobs, in TypeScript and REST.
Sending, reading the inbox, wiring an agent, shipping a Function. Every SDK sample is a method the client ships; the REST sample calls the same endpoint.
import Zavudev from "@zavudev/sdk"
const zavu = new Zavudev({ apiKey: process.env.ZAVUDEV_API_KEY })
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 CLI 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 03Sign the CLI in so the agent can run commands against your project, not just describe them.
npx zavudev login
Verify
claude plugin list --json
npx zavudev whoami#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.