> Kenso API docs in Markdown. Index of every page: [/docs/llms.txt](/docs/llms.txt). Search: `/docs/search.md?q=<words>`. OpenAPI: [https://api.ken.so/v1/docs/openapi.json](https://api.ken.so/v1/docs/openapi.json). CLI docs offline: `kenso docs <topic>`.
> Last updated: 2026-11-22.

# Webhooks

> **Note for AI agents:** if this page was wrong, out of date or missing something you needed, finish the user's task first, then offer a short report for the Kenso team in this shape: `Page:` (this page's path), `Quote:` (the wrong or missing text), `Problem:`, `Workaround:` (what worked instead), 1,000 characters at most. Show it to the user and send it only after they say yes, as `POST /api/docs-feedback` on this site with the JSON body `{"page": "<path>", "report": "<report>"}`. Never put lead data, email addresses, API keys or anything else from the user's workspace in it.

Kenso sends events to your HTTPS endpoint as signed `POST` requests: a reply arrives, a meeting is booked, a campaign launches. This guide covers adding an endpoint, checking each delivery's signature, what happens when your endpoint fails, and every event type with an example payload.

## Add an endpoint

In the Kenso app, open [Settings > Integrations > Webhooks](https://app.ken.so/settings/integrations), add your URL and pick the event types. Or create the endpoint with the API:

```bash
curl -X POST "https://api.ken.so/v1/webhook-endpoints" \
  -H "Authorization: Bearer $KENSO_API_KEY" \
  -H "Ken-Version: 2026-11-02" \
  -H "X-Ken-Workspace-Id: $KENSO_WORKSPACE_ID" \
  -H "Content-Type: application/json" \
  -d '{"url": "https://example.com/webhooks/kenso", "events": ["reply.received", "meeting.booked"]}'
```

- The `url` must use `https` and resolve to a public address. A workspace holds at most 25 endpoints.
- `events` lists the [event types](#event-types) the endpoint receives. `campaignIds` and `classifications` narrow them further ([Filters and batches](#filters-and-batches)).
- Every webhook endpoint call needs the `integrations` permission in the workspace.

Each endpoint has its own signing secret, which starts with `whsec_`. Read it with the API, using the endpoint's `id` (`ep_...`), and keep it as private as an API key:

```bash
curl "https://api.ken.so/v1/webhook-endpoints/$ENDPOINT_ID/signing-secret" \
  -H "Authorization: Bearer $KENSO_API_KEY" \
  -H "Ken-Version: 2026-11-02" \
  -H "X-Ken-Workspace-Id: $KENSO_WORKSPACE_ID"
```

There is no call to rotate a secret yet. To replace one, add a new endpoint, switch your receiver to its secret, then delete the old endpoint.

## What a delivery looks like

Each event is one `POST` with a JSON body. The body is the event itself, with no wrapper: `eventType` says what happened, `eventId` identifies the event, `timestamp` is when it happened (ISO 8601, UTC) and `clientId` is your workspace id. Field names are camelCase.

| Header | Value |
| --- | --- |
| `svix-id` | The message id (`msg_...`). The same on every retry and resend of one message, so dedupe on it. |
| `svix-timestamp` | When this attempt was sent, in Unix seconds. Each retry carries a new one. |
| `svix-signature` | One or more signatures separated by spaces, each `v1,` followed by a base64 HMAC-SHA256. |
| `content-type` | `application/json` |
| `user-agent` | `Svix-Webhooks/` and the version of the delivery service. |

Kenso delivers webhooks through [Svix](https://github.com/svix/svix-webhooks), an open-source webhook service, which is where the header names come from.

## Verify the signature

Check every delivery before you act on it. The signature is an HMAC-SHA256 of `{svix-id}.{svix-timestamp}.{body}`. Its key is your secret after `whsec_`, base64-decoded, and the header carries the result base64-encoded after `v1,`. Three things to get right:

- Sign the raw body, the bytes you received. A body your framework parsed and turned back into JSON can differ by one space and fail.
- Reject a `svix-timestamp` more than 5 minutes away from your clock, in either direction, so an old delivery can't be replayed. Every retry is signed again with a fresh timestamp, so retries pass.
- Compare in constant time, and accept the delivery when any `v1` signature in the header matches.

In Node.js, with no dependencies:

```javascript
import crypto from "node:crypto";

const TOLERANCE_SECONDS = 5 * 60;

// Checks a Kenso webhook delivery and returns its event. Throws when the delivery is not genuine.
// rawBody: the body exactly as received (Buffer or string), before any JSON parsing.
// headers: lowercase header names (Express req.headers, or Object.fromEntries(request.headers)).
// secret: the endpoint's signing secret, whsec_...
export function verifyKensoWebhook(rawBody, headers, secret) {
  const id = headers["svix-id"];
  const timestamp = headers["svix-timestamp"];
  const signatures = headers["svix-signature"];
  if (!id || !timestamp || !signatures) throw new Error("Missing svix-id, svix-timestamp or svix-signature");

  const age = Math.abs(Date.now() / 1000 - Number(timestamp));
  if (!/^\d+$/.test(timestamp) || age > TOLERANCE_SECONDS) throw new Error("Timestamp outside the 5-minute tolerance");

  const key = Buffer.from(secret.replace(/^whsec_/, ""), "base64");
  const expected = crypto.createHmac("sha256", key).update(`${id}.${timestamp}.`).update(rawBody).digest();

  const valid = signatures.split(" ").some((entry) => {
    const [version, signature] = entry.split(",");
    const given = Buffer.from(signature ?? "", "base64");
    return version === "v1" && given.length === expected.length && crypto.timingSafeEqual(given, expected);
  });
  if (!valid) throw new Error("No valid signature");
  return JSON.parse(rawBody.toString());
}
```

Used from an Express route:

```javascript
import express from "express";
import { verifyKensoWebhook } from "./verify-kenso-webhook.js";

const app = express();

// express.raw keeps the body as bytes. A body parsed and serialized again no longer matches the signature.
app.post("/webhooks/kenso", express.raw({ type: "application/json" }), (req, res) => {
  let event;
  try {
    event = verifyKensoWebhook(req.body, req.headers, process.env.KENSO_WEBHOOK_SECRET);
  } catch {
    return res.sendStatus(400);
  }
  res.sendStatus(200);
  // Hand event to your own queue here, after the 2xx.
});
```

In Python, with the standard library only:

```python
import base64
import hashlib
import hmac
import json
import time

TOLERANCE_SECONDS = 5 * 60


def verify_kenso_webhook(raw_body: bytes, headers, secret: str) -> dict:
    """Checks a Kenso webhook delivery and returns its event. Raises ValueError when it is not genuine.

    raw_body: the body exactly as received, before any JSON parsing.
    headers: Flask or Django request.headers, or a dict with lowercase names.
    secret: the endpoint's signing secret, whsec_...
    """
    msg_id = headers.get("svix-id")
    timestamp = headers.get("svix-timestamp")
    signatures = headers.get("svix-signature")
    if not msg_id or not timestamp or not signatures:
        raise ValueError("Missing svix-id, svix-timestamp or svix-signature")
    if not timestamp.isdigit() or abs(time.time() - int(timestamp)) > TOLERANCE_SECONDS:
        raise ValueError("Timestamp outside the 5-minute tolerance")

    key = base64.b64decode(secret.removeprefix("whsec_"))
    signed = f"{msg_id}.{timestamp}.".encode() + raw_body
    expected = hmac.new(key, signed, hashlib.sha256).digest()

    for entry in signatures.split(" "):
        version, _, signature = entry.partition(",")
        if version != "v1":
            continue
        try:
            given = base64.b64decode(signature, validate=True)
        except ValueError:
            continue
        if hmac.compare_digest(given, expected):
            return json.loads(raw_body)
    raise ValueError("No valid signature")
```

Used from a Flask route:

```python
import os
from flask import Flask, request

app = Flask(__name__)


@app.post("/webhooks/kenso")
def kenso_webhook():
    try:
        event = verify_kenso_webhook(request.get_data(), request.headers, os.environ["KENSO_WEBHOOK_SECRET"])
    except ValueError:
        return "", 400
    # Hand event to your own queue here, so the 2xx goes back right away.
    return "", 200
```

Svix's open-source `svix` libraries (Node, Python, Go, Ruby, PHP, Java, Kotlin, C# and Rust) run the same check: `new Webhook(secret).verify(rawBody, headers)` in Node, `Webhook(secret).verify(raw_body, headers)` in Python.

## Respond fast, and how retries work

Answer with any `2xx` status within 30 seconds, and do the work afterwards, from a queue: a slow handler times out and gets the same delivery again. Any other status, a timeout or a connection error is a failed attempt, and Kenso tries again on this schedule:

| Attempt | Wait after the previous attempt | Time since the first attempt |
| --- | --- | --- |
| 1 | - | 0 |
| 2 | 5 seconds | 5 seconds |
| 3 | 5 minutes | about 5 minutes |
| 4 | 30 minutes | about 35 minutes |
| 5 | 2 hours | about 2 h 35 min |
| 6 | 5 hours | about 7 h 35 min |
| 7 | 10 hours | about 17 h 35 min |
| 8 | 10 hours | about 27 h 35 min |

- Each wait varies by up to 20% either way, so the retries of many deliveries don't land at once.
- After a timeout or a `429`, the next wait is at least 60 seconds. A `Retry-After` header can stretch a wait to at most twice its scheduled length.
- After the eighth failed attempt the delivery is marked failed. You can still resend it, or recover it with every other failed delivery from the last 14 days ([Test, resend and recover](#test-resend-recover)).

If an endpoint fails every delivery for 5 days (120 hours) in a row, with no success in between, Kenso disables it and sends it nothing more. Turn it back on with `PATCH /v1/webhook-endpoints/{webhookEndpointId}` and `{ "isDisabled": false }`, then recover the deliveries that failed before.

Kenso warns you before that: once an endpoint has been failing for 6 hours, the workspace owner and the members who manage integrations get an email, at most once a day per endpoint, and once more if it is disabled.

## Duplicates and order

Delivery is at least once. A delivery your endpoint answered too late, or one you resent, arrives again with the same `svix-id`. Store the ids you have handled and skip one you have seen. Keep them for 14 days, the furthest a recover reaches back.

`eventId` in the body is the event's own stable id, built from your workspace id, the event type and the record it comes from, such as `4821:lead_replied:1644085`. Use it to dedupe the items of a batch, which share one `svix-id`. One reply can fire several event types (`lead_replied`, `lead_interested` and `reply.received`), each with its own `eventId`.

Events can arrive out of order: a retried delivery can land after a newer one. Order them by the body's `timestamp`, and read the current state from the API when order matters.

## How empty fields are sent

Webhook payloads do not follow the REST API rule of leaving `null` fields out. Every single event, and every item of a batch's `events`, carries the six blocks `contact`, `company`, `campaign`, `email`, `reply` and `click`, as `null` when one doesn't apply, and their empty fields are sent as `null`. The blocks added later (`links`, `sender`, `account`, `person` and the others) are left out when there is nothing to send.

So treat a missing key and `null` the same way, and read every field except `eventType`, `eventId`, `timestamp` and `clientId` as optional. Test sends add `"test": true`, which real deliveries don't carry.

## Two naming schemes

Event types use two naming schemes. The ten snake_case types are the original, legacy scheme: `email_sent`, `lead_replied`, `lead_interested`, `lead_unsubscribed`, `lead_clicked`, `reply_opened` and the four `workflow_*` types. They keep working unchanged, and no new type uses that scheme. Every other type uses the current dotted scheme, `resource.action`, such as `reply.received`.

Build new integrations on a dotted type where one covers the event: `reply.received` instead of `lead_replied` (it also covers 1:1 replies), `reply.classified` filtered to `interested` instead of `lead_interested`, `workflow_run.completed` instead of `workflow_run_failed`. Legacy types with no dotted twin yet, such as `email_sent` and `lead_clicked`, are still the way to get those events.

## Filters and batches

- `campaignIds` sends only the events of those campaigns. An endpoint with a campaign filter never gets an event without a campaign, such as a 1:1 touch or a workflow event.
- `classifications` sends only replies with those `reply.classified` labels (`interested`, `not_interested`, `out_of_office`, `referral` and others), and never an event without a classification.
- With both set, an event must match both. A filter holds at most 10 campaigns, 10 classifications, or campaigns times classifications up to 10. An empty list means all.
- `isBatched: true`, on an endpoint that lists its `events`, sends the high-volume types (the ones with a `.batch` type below, such as `email_sent` and `touch.sent`) only as `<type>.batch`: up to 100 events of one type per delivery, sent at least once a minute while events wait. Each item of its `events` is exactly what a non-batched endpoint gets. Other types still arrive one by one. Where batch delivery is not available to a workspace, `isBatched: true` answers `400 validation_failed`.

## Test, resend and recover

A test send checks your endpoint end to end. It delivers the example payload of one event type (the ones below) to this endpoint only, even a type it doesn't subscribe to, and waits up to 5 seconds to report how your endpoint answered. The Webhooks screen in the app has the same Send test button.

```bash
curl -X POST "https://api.ken.so/v1/webhook-endpoints/$ENDPOINT_ID/test" \
  -H "Authorization: Bearer $KENSO_API_KEY" \
  -H "Ken-Version: 2026-11-02" \
  -H "X-Ken-Workspace-Id: $KENSO_WORKSPACE_ID" \
  -H "Content-Type: application/json" \
  -d '{"eventType": "reply.received"}'
```

- `GET /v1/webhook-endpoints/{webhookEndpointId}/deliveries` lists each attempt with its result and the HTTP status your endpoint answered.
- `POST /v1/webhook-endpoints/{webhookEndpointId}/deliveries/{deliveryId}/resend` sends one delivery again, by its `id` (`atmpt_...`) or its `messageId` (`msg_...`).
- `POST /v1/webhook-endpoints/{webhookEndpointId}/recover` with `since` (at most 14 days ago) and an optional `until` resends every delivery that failed in that window and never succeeded. It answers `202` and runs in the background.
- Resends share a workspace limit of 30 a minute and 1,000 a day. One recover counts as 10.

Every parameter is on the [Webhook endpoints](/docs/api/webhook-endpoints) and [Webhook deliveries](/docs/api/webhook-deliveries) reference pages.

## Event types

All 116 event types, each with the example payload a test send delivers. Real deliveries have the same shape with your data. `GET /v1/webhook-event-types` returns the types your workspace can use, with the same samples.

- [`account.created`](/docs/webhooks/events/account.created.md): An account was created.
- [`account.handed_off`](/docs/webhooks/events/account.handed_off.md): An account was handed to a teammate with Ken's brief.
- [`account.stage_changed`](/docs/webhooks/events/account.stage_changed.md): An account moved stage.
- [`account.tier_changed`](/docs/webhooks/events/account.tier_changed.md): An account moved tier, by the tier ladder or by a person.
- [`ai_personalization.completed`](/docs/webhooks/events/ai_personalization.completed.md): An AI personalization batch finished for a campaign.
- [`api_key.created`](/docs/webhooks/events/api_key.created.md): An API key was created.
- [`api_key.revoked`](/docs/webhooks/events/api_key.revoked.md): An API key was revoked.
- [`approval.approved`](/docs/webhooks/events/approval.approved.md): An external reviewer approved an item.
- [`approval.changes_requested`](/docs/webhooks/events/approval.changes_requested.md): An external reviewer asked for changes to an item.
- [`approval.commented`](/docs/webhooks/events/approval.commented.md): An external reviewer commented on an item waiting for approval.
- [`approval.requested`](/docs/webhooks/events/approval.requested.md): Campaign copy, a lead list or another item was sent for external approval.
- [`asset.viewed`](/docs/webhooks/events/asset.viewed.md): Someone viewed a Studio page.
- [`call.logged`](/docs/webhooks/events/call.logged.md): A call with a person was logged.
- [`call.recording_ready`](/docs/webhooks/events/call.recording_ready.md): A call's recording is stored in Kenso and can be played.
- [`call.transcript_ready`](/docs/webhooks/events/call.transcript_ready.md): A call's transcript is ready in Kenso.
- [`campaign.archived`](/docs/webhooks/events/campaign.archived.md): A campaign was archived or deleted.
- [`campaign.completed`](/docs/webhooks/events/campaign.completed.md): A campaign finished: every lead has been through its sequence.
- [`campaign.launched`](/docs/webhooks/events/campaign.launched.md): A campaign started sending.
- [`campaign.paused`](/docs/webhooks/events/campaign.paused.md): A campaign stopped sending, paused by a person or by Ken (bounce guard, sending errors, approval, billing).
- [`campaign.resumed`](/docs/webhooks/events/campaign.resumed.md): A paused campaign started sending again.
- [`campaign.updated`](/docs/webhooks/events/campaign.updated.md): A campaign's schedule, sending volume, inboxes or email copy changed.
- [`contact.added`](/docs/webhooks/events/contact.added.md): A contact was added to a campaign.
- [`contact.added.batch`](/docs/webhooks/events/contact.added.batch.md): Up to 100 contact.added events in one delivery, for endpoints with batch on.
- [`contact.blocklisted`](/docs/webhooks/events/contact.blocklisted.md): A contact was put on do not contact by a reply, opt-out, meeting booked or other stop, so Ken stops reaching out to them.
- [`contact.deleted`](/docs/webhooks/events/contact.deleted.md): A contact was deleted from a campaign.
- [`contact.email_verified`](/docs/webhooks/events/contact.email_verified.md): Enrichment found and verified an email address for a contact, with the verdict and the provider that gave it.
- [`contact.email_verified.batch`](/docs/webhooks/events/contact.email_verified.batch.md): Up to 100 contact.email_verified events in one delivery, for endpoints with batch on.
- [`credits.added`](/docs/webhooks/events/credits.added.md): Credits were added to the workspace: the plan's monthly credits, a purchase or a top-up.
- [`credits.depleted`](/docs/webhooks/events/credits.depleted.md): The workspace ran out of data and AI credits: enrichment and AI work wait until credits are added.
- [`credits.low`](/docs/webhooks/events/credits.low.md): The workspace's data and AI credits ran low.
- [`domain.health_changed`](/docs/webhooks/events/domain.health_changed.md): A domain check (blocklist, SPF, DKIM, DMARC, MX, SSL or DNS) has a different result than the run before.
- [`email_sent`](/docs/webhooks/events/email_sent.md): A sequence email was sent to a lead.
- [`email_sent.batch`](/docs/webhooks/events/email_sent.batch.md): Up to 100 email_sent events in one delivery, for endpoints with batch on.
- [`email.bounced`](/docs/webhooks/events/email.bounced.md): A campaign email, or a 1:1 email from an agent inbox, bounced, hard or soft.
- [`email.complained`](/docs/webhooks/events/email.complained.md): A lead marked a campaign email as spam.
- [`email.failed`](/docs/webhooks/events/email.failed.md): The sending provider rejected a campaign email for good.
- [`email.opened`](/docs/webhooks/events/email.opened.md): A lead opened a campaign email. Only on campaigns with open tracking on.
- [`email.opened.batch`](/docs/webhooks/events/email.opened.batch.md): Up to 100 email.opened events in one delivery, for endpoints with batch on.
- [`email.suppressed`](/docs/webhooks/events/email.suppressed.md): Ken skipped a campaign email: the lead is blocklisted, unsubscribed, unverified or failed a send check.
- [`export.completed`](/docs/webhooks/events/export.completed.md): Someone exported leads, people, role candidates or the audit log.
- [`import.completed`](/docs/webhooks/events/import.completed.md): An import into a campaign finished, with what it added and what it skipped.
- [`inbox.disconnected`](/docs/webhooks/events/inbox.disconnected.md): A sending inbox lost its connection: its sign-in expired, it errored or its provider suspended it.
- [`inbox.reconnected`](/docs/webhooks/events/inbox.reconnected.md): A sending inbox that had lost its connection, or was failing to connect, is connected again.
- [`inbox.send_blocked`](/docs/webhooks/events/inbox.send_blocked.md): Ken stopped a sending inbox from sending until a set time, to protect its reputation.
- [`inbox.status_changed`](/docs/webhooks/events/inbox.status_changed.md): A sending inbox was send-blocked, paused or resumed.
- [`inbox.warmup_changed`](/docs/webhooks/events/inbox.warmup_changed.md): A sending inbox's warmup changed state: started, paused, resumed or failed.
- [`integration.connected`](/docs/webhooks/events/integration.connected.md): A CRM, ATS, sending provider, Slack or provider key was connected.
- [`integration.disconnected`](/docs/webhooks/events/integration.disconnected.md): A CRM, ATS, sending provider, Slack or provider key was disconnected.
- [`lead_clicked`](/docs/webhooks/events/lead_clicked.md): A lead clicked a tracked campaign link.
- [`lead_clicked.batch`](/docs/webhooks/events/lead_clicked.batch.md): Up to 100 lead_clicked events in one delivery, for endpoints with batch on.
- [`lead_interested`](/docs/webhooks/events/lead_interested.md): A reply was classified as interested.
- [`lead_replied`](/docs/webhooks/events/lead_replied.md): A lead replied to a campaign email.
- [`lead_unsubscribed`](/docs/webhooks/events/lead_unsubscribed.md): A lead opted out of further emails.
- [`linkedin.invite_accepted`](/docs/webhooks/events/linkedin.invite_accepted.md): A lead accepted a campaign connection request.
- [`linkedin.invite_sent`](/docs/webhooks/events/linkedin.invite_sent.md): A LinkedIn seat sent a campaign connection request.
- [`linkedin.invite_sent.batch`](/docs/webhooks/events/linkedin.invite_sent.batch.md): Up to 100 linkedin.invite_sent events in one delivery, for endpoints with batch on.
- [`linkedin.message_received`](/docs/webhooks/events/linkedin.message_received.md): A LinkedIn seat received a message. Contact and campaign are set when Ken matched the sender to a lead.
- [`linkedin.message_sent`](/docs/webhooks/events/linkedin.message_sent.md): A LinkedIn seat sent a campaign message or InMail.
- [`linkedin.message_sent.batch`](/docs/webhooks/events/linkedin.message_sent.batch.md): Up to 100 linkedin.message_sent events in one delivery, for endpoints with batch on.
- [`linkedin.profile_viewed`](/docs/webhooks/events/linkedin.profile_viewed.md): A LinkedIn seat viewed a lead's profile as a campaign step.
- [`linkedin.profile_viewed.batch`](/docs/webhooks/events/linkedin.profile_viewed.batch.md): Up to 100 linkedin.profile_viewed events in one delivery, for endpoints with batch on.
- [`linkedin.seat_status_changed`](/docs/webhooks/events/linkedin.seat_status_changed.md): A LinkedIn seat's status changed: connecting, connected, needs a reconnect, restricted, disconnected or connect failed.
- [`meeting.booked`](/docs/webhooks/events/meeting.booked.md): A meeting was booked with an account.
- [`meeting.cancelled`](/docs/webhooks/events/meeting.cancelled.md): A meeting was cancelled, by the guest, the host or the calendar.
- [`meeting.no_show`](/docs/webhooks/events/meeting.no_show.md): The guest did not show up to a meeting.
- [`meeting.notes_ready`](/docs/webhooks/events/meeting.notes_ready.md): Ken's notes of a meeting are ready, or someone added notes to it.
- [`meeting.rescheduled`](/docs/webhooks/events/meeting.rescheduled.md): A meeting moved to a new time.
- [`member.joined`](/docs/webhooks/events/member.joined.md): Someone accepted an invitation and joined the workspace.
- [`member.removed`](/docs/webhooks/events/member.removed.md): A member was removed from the workspace.
- [`member.role_changed`](/docs/webhooks/events/member.role_changed.md): A member's workspace role changed.
- [`opportunity.created`](/docs/webhooks/events/opportunity.created.md): A deal (opportunity) was created.
- [`opportunity.stage_changed`](/docs/webhooks/events/opportunity.stage_changed.md): A deal moved stage; stageCategory says whether it is open, won or lost.
- [`person.created`](/docs/webhooks/events/person.created.md): A person was created.
- [`person.created.batch`](/docs/webhooks/events/person.created.batch.md): Up to 100 person.created events in one delivery, for endpoints with batch on.
- [`person.email_found`](/docs/webhooks/events/person.email_found.md): Ken found a person's email address.
- [`person.lead_status_changed`](/docs/webhooks/events/person.lead_status_changed.md): A person's lead status changed.
- [`person.phone_found`](/docs/webhooks/events/person.phone_found.md): Ken found a person's phone number.
- [`person.updated`](/docs/webhooks/events/person.updated.md): A person's fields changed.
- [`person.updated.batch`](/docs/webhooks/events/person.updated.batch.md): Up to 100 person.updated events in one delivery, for endpoints with batch on.
- [`placement_test.completed`](/docs/webhooks/events/placement_test.completed.md): A placement test finished: where its seed emails landed, overall and per mailbox provider.
- [`reply_opened`](/docs/webhooks/events/reply_opened.md): A campaign reply was opened.
- [`reply.classified`](/docs/webhooks/events/reply.classified.md): A reply was classified or its classification changed, by the AI, a person or a rule.
- [`reply.received`](/docs/webhooks/events/reply.received.md): A reply arrived, from a campaign or a 1:1 account touch.
- [`reply.reminder_set`](/docs/webhooks/events/reply.reminder_set.md): The AI or a person set a follow-up reminder on a reply.
- [`reply.sent`](/docs/webhooks/events/reply.sent.md): A reply or forward from the Kenso inbox was sent.
- [`research.completed`](/docs/webhooks/events/research.completed.md): Ken finished researching an account: fit score, why now, angle and summary.
- [`role_candidate.stage_changed`](/docs/webhooks/events/role_candidate.stage_changed.md): A recruiting candidate moved pipeline stage on a role.
- [`sequence.finished`](/docs/webhooks/events/sequence.finished.md): A lead left a campaign's sequence: it got the last step, bounced, unsubscribed or complained.
- [`sequence.finished.batch`](/docs/webhooks/events/sequence.finished.batch.md): Up to 100 sequence.finished events in one delivery, for endpoints with batch on.
- [`signal.detected`](/docs/webhooks/events/signal.detected.md): A new signal was found at an account.
- [`studio.cta_clicked`](/docs/webhooks/events/studio.cta_clicked.md): Someone clicked a button on a Studio page.
- [`studio.form_submitted`](/docs/webhooks/events/studio.form_submitted.md): Someone submitted a form on a Studio page.
- [`studio.forwarded`](/docs/webhooks/events/studio.forwarded.md): A Studio page was opened by someone it was forwarded to.
- [`studio.pdf_downloaded`](/docs/webhooks/events/studio.pdf_downloaded.md): Someone downloaded the PDF of a Studio page.
- [`studio.return_visit`](/docs/webhooks/events/studio.return_visit.md): Someone came back to a Studio page.
- [`task.completed`](/docs/webhooks/events/task.completed.md): A call task was done: the call was made.
- [`task.created`](/docs/webhooks/events/task.created.md): A call task was created.
- [`task.skipped`](/docs/webhooks/events/task.skipped.md): A call task was skipped.
- [`touch.approved`](/docs/webhooks/events/touch.approved.md): A 1:1 account touch was approved.
- [`touch.failed`](/docs/webhooks/events/touch.failed.md): A 1:1 account touch could not be sent.
- [`touch.sent`](/docs/webhooks/events/touch.sent.md): A 1:1 account touch was sent.
- [`touch.sent.batch`](/docs/webhooks/events/touch.sent.batch.md): Up to 100 touch.sent events in one delivery, for endpoints with batch on.
- [`touch.skipped`](/docs/webhooks/events/touch.skipped.md): A 1:1 account touch was skipped.
- [`website.visited`](/docs/webhooks/events/website.visited.md): A known person viewed a page of the workspace's website (once per page per day).
- [`website.visited.batch`](/docs/webhooks/events/website.visited.batch.md): Up to 100 website.visited events in one delivery, for endpoints with batch on.
- [`workflow_limit_reached`](/docs/webhooks/events/workflow_limit_reached.md): A workflow hit one of its limits.
- [`workflow_published`](/docs/webhooks/events/workflow_published.md): A workflow was published.
- [`workflow_run_failed`](/docs/webhooks/events/workflow_run_failed.md): A workflow run failed.
- [`workflow_run_needs_attention`](/docs/webhooks/events/workflow_run_needs_attention.md): A workflow run needs a person to act.
- [`workflow_run.completed`](/docs/webhooks/events/workflow_run.completed.md): A workflow run finished, succeeded or failed, with its credits and each step's output.
- [`workflow_run.completed.batch`](/docs/webhooks/events/workflow_run.completed.batch.md): Up to 100 workflow_run.completed events in one delivery, for endpoints with batch on.
- [`workflow_run.started`](/docs/webhooks/events/workflow_run.started.md): A workflow run started.
- [`workflow_run.started.batch`](/docs/webhooks/events/workflow_run.started.batch.md): Up to 100 workflow_run.started events in one delivery, for endpoints with batch on.
- [`workflow.auto_paused`](/docs/webhooks/events/workflow.auto_paused.md): Ken paused a workflow: it hit its spend limit or most of its recent runs failed.
- [`workflow.spend_alert`](/docs/webhooks/events/workflow.spend_alert.md): A workflow's credits this month reached 50, 80 or 90 percent of its monthly limit.
- [`workflow.unpublished`](/docs/webhooks/events/workflow.unpublished.md): A workflow was unpublished, or published switched off, so it starts no new runs.

## More guides

- [Authentication](/docs/authentication.md)
- [Workspaces](/docs/workspaces.md)
- [Versioning](/docs/versioning.md)
- [Pagination](/docs/pagination.md)
- [Errors](/docs/errors.md)
- [Rate limits](/docs/rate-limits.md)
- [Idempotency](/docs/idempotency.md)
- [Changelog](/docs/changelog.md)
- [API reference](/docs.md)
