Webhooks, API keys & Zapier
Push every Knockt event to your own backend or no-code tools, and log sales or mark installs over the API.
4 min read · Updated June 23, 2026
Beyond the chat channels, Knockt is open by default: every meaningful event can fire a signed webhook, and a workspace API key lets your own scripts or automations read and write.
Outbound webhooks
Add a Custom (JSON) channel in Settings → Integrations and Knockt POSTs each event as JSON — sale.logged, sale.installed, payout.sent, dispute.filed, period.closed, period.approved, goal.hit, and rep.onboarded — to any HTTPS endpoint. Each request carries an x-knockt-signature HMAC so you can verify it really came from Knockt.
API keys
Generate a key under Settings → Integrations → API keys. It's shown once — copy it and keep it safe. Send it on every request in the x-knockt-key header. With it you can:
- Log a sale — create a deal for one of your reps.
- Mark a sale installed — flip a deal to Installed by its id or CRM deal id.
- Subscribe to events — register a URL to receive any of the events above.
Heads up
An API key acts for your whole workspace. Store it as a secret, never commit it to code, and revoke it from Settings if it's ever exposed — revoking takes effect immediately.
Zapier, Make & n8n
Point any of these at Knockt today: use a Custom (JSON) channel as a trigger, and call the API (with your key) as an action. A native Zapier app — Knockt in the Zapier directory with one-click triggers and actions — is on the way; until it's listed, the API-key path does the same thing.
Related
Get alerts in Slack, Discord, Teams & Google Chat
Send sale, install, payout, and pay-period alerts to your team's chat — and choose which events each channel gets.
Sync installs from your CRM
Connect any CRM — JobNimbus, GoHighLevel, HubSpot, Salesforce — so an install confirms the matching deal in Knockt automatically. Enterprise.
Log your first sale
How a rep records a deal from the field, and what happens to the numbers when they do.