Tell another server when something changes

On Team and above, Klientr POSTs a signed JSON body to the URL you save for the project. A blank URL, or a webhook switched off, sends nothing.

Starter leaves outbound webhooks off. Team, Business, and Studio include one endpoint and one signing secret per project.

Create free workspace Sign in

On this page

A signed notice for the events you pick

One endpoint for the project

Paste an HTTPS URL, leave Enabled on, and tick the events. Leave the URL blank, or switch Enabled off, and Klientr sends nothing.

A signature on the raw body

Each request is JSON. X-Klientr-Signature is the lowercase hex HMAC-SHA256 of that exact body, using the signing secret. X-Klientr-Event names the event.

The work the other server should hear about

Conversations, messages, contacts, bookings, payments, tasks, feedback, social mentions, and campaigns. The body carries the event, the time, the project, and the fields for that event.

How it works

From a URL to the first delivery

Save the endpoint

Open Webhooks in the project and paste the HTTPS URL that should receive the events.

Choose what to send

Leave Enabled on, tick the events, and save. The signing secret appears after that first save.

Check the signature

Compute HMAC-SHA256 of the raw body with the signing secret and compare it with X-Klientr-Signature before you trust the payload.

In the workspace

What the webhook includes

One URL and signing secret per project
JSON with the event, the time, the project, and the data
A delivery log, and a retry when the call fails
Team, Business, and Studio

FAQ

Common questions

After you save a URL, leave the webhook enabled, and the change is an event you selected. A blank URL or a disabled webhook sends nothing. Starter does not include outbound webhooks.

X-Klientr-Signature is the lowercase hex HMAC-SHA256 of the raw JSON body, keyed with the signing secret. The secret is created when you save the webhook. A server error is retried. A client error is recorded in the delivery log.

Conversations, messages, contacts, bookings, payments, tasks, feedback, social mentions, and campaigns. Each payload names the event, the time it happened, the project, and the fields for that event.

The same workspace, from a different question.

Shared inbox Website chat Message form Telegram inbox WhatsApp inbox X inbox Appointment booking Booking deposits Google Calendar Rebook after a visit Review after a visit Visit packs Social mentions X mentions REST API MCP server

Give every customer one place to land

Create a free workspace, connect a channel, and keep the reply, the booking, and the follow-up together.