To use the API with little or no code, ConverZAP has ready-made integrations. They all use the same key (czk_live_…) from Settings → Public API and follow the same API rules (scopes, plan, 24-hour window).
TypeScript SDK
npm install @converzap/sdkimport { ConverZap } from "@converzap/sdk";
const cz = new ConverZap({ apiKey: process.env.CONVERZAP_API_KEY! });
const contact = await cz.upsertContact({ body: { name: "Ana", phone: "+5511987654321", labels: ["lead"] } });
for await (const deal of cz.paginate(cz.listDeals, { query: { status: "open" } })) console.log(deal.title);One typed method per endpoint, zero dependencies (Node 18+, Deno, Bun and edge). Errors are ConverZapError with a stable code; verifyWebhook checks webhook signatures.
n8n
In Settings → Community Nodes → Install, install n8n-nodes-converzap and create the ConverZAP API credential with your key.
- ConverZAP: contacts, conversations, messages (text, template, note, scheduled), deals, campaigns, automations and AI agents. Can be used as a tool by an n8n AI Agent.
- ConverZAP Polling Trigger: new contact, contact updated, new deal, new conversation, conversation needs a human — on every plan with API access.
- ConverZAP Trigger (instant): message received/sent/status and conversation events, on plans with webhooks. The webhook is created and removed automatically when the workflow is activated/deactivated.
Zapier (coming soon)
The ConverZAP app is under review by Zapier. Meanwhile, use Webhooks by Zapier ("Custom Request") with the header Authorization: Bearer czk_live_… to call any endpoint. Planned triggers: new contact, new deal, new conversation and conversation needs a human. Actions: create/update contact, add labels, send text or template, internal note, create and move deal, enroll in automation.
Make (coming soon)
The ConverZAP app for Make is being prepared. Meanwhile, use the HTTP → Make a request module with the header Authorization: Bearer czk_live_….
Good practices
- One key per integration, with only the scopes it needs — you can revoke one without stopping the others.
- Message sends already include an
Idempotency-Key: re-running a step never sends twice.