Kasar
Kasar

CRM webhooks and API: Kasar plugs into your tools

An address receives calls from your forms and your software, and Kasar writes the record or starts a workflow. In the other direction, every CRM event goes out to your system, signed, and the REST API reads and writes your objects.

01

What comes in: one endpoint per system

In the workspace settings, the “What comes in” section creates inbound endpoints. Each one accepts a POST with a JSON or form body, up to 256 KB, and does one of two things. “Write a record” creates or updates a record in the target object, recognising an existing one through its identity rule. “Publish an event” touches no data: it wakes the automations subscribed to it.

02

What goes out: your events, signed

The “What goes out” section declares the systems Kasar calls. You tick the events you want, and each one leaves the moment it happens, with no workflow to build. With “HMAC signature”, every delivery follows the Standard Webhooks specification: webhook-id, webhook-timestamp and webhook-signature headers, which any compliant library can verify. Each delivery gets up to five attempts in total, at growing intervals.

03

The REST API for your own code

An integration key, prefixed ksr_svc_, opens API v1 with rights ticked object by object: Read, Write, Delete. The same routes serve every object, custom ones included. PUT creates or updates by identity, and the X-Idempotency-Key header makes a retry harmless for twenty-four hours.

When it helps

The website form starts the sequence

The contact form posts to an endpoint. A workflow with the “Incoming webhook” trigger runs “Create or update” on the contact, then “Add to a list”. The sequence tied to that list writes to them: anyone added after it started enters too.

A signed contract decrements stock

When the deal is marked won, the “HTTP request” block calls your ERP with a POST and a JSON body carrying the order lines. The ERP removes the quantities sold. Its status code and response stay readable by the next blocks of the workflow.

A data warehouse that stays current

The reporting tool loads existing data once through GET on /api/v1, then subscribes to creations, updates and deletions. It deduplicates on webhook-id, which stays the same when Kasar redelivers, and rereads a record through the API whenever it needs the relations.

Setting it up, step by step

  1. 1

    Open Settings, “Workspace” group, “API and webhooks” tab. It is open to admins and to roles holding the “Manage webhooks” capability.

  2. 2

    To receive, click “New endpoint”, pick “Write a record” or “Publish an event”, then copy the address: it is displayed only once.

  3. 3

    Have your tool send a real call, open the endpoint and click “Capture” to list every received path with its type and a sample.

  4. 4

    Under “The mapping”, click “Add a mapping” to link a CRM field to a received path, then click “Save the mapping”.

  5. 5

    To send, click “New destination”, fill in the “Base URL” and the authentication, then use “Choose events” and “Send a test call”.

  6. 6

    For the API, create a key with “New integration”, tick its rights and copy it when “Copy the key now” appears. The keys section is reserved for administrators.

What Kasar captures, and where it goes

  • Records written by an endpoint, in the object you chose, deduplicated by that object’s identity rule.

  • The body of every inbound call, available in the workflow listening to the endpoint and filterable through “Received payload”.

  • A log per endpoint and per destination: time, response code, duration in milliseconds, and the received body on the endpoint side.

  • Outbound events in the type, timestamp, data format, with the record in the exact shape the API serves.

  • Your APIs’ responses, HTTP status and body, picked up by the blocks placed after an “HTTP request”.

Automations that go with it

Incoming webhook

What the workflow does
“Create or update” the contact from the received body, then “Distribute / assign” to give it an owner on the sales team.

Opportunity won

What the workflow does
“HTTP request” with a POST to your ERP destination, which opens the delivery project and reserves the quantities sold.

Record created

What the workflow does
“Condition” on the account type, then “HTTP request” to your support tool to open the new customer’s space there.

Triggers and blocks carry their exact names from the Kasar automation editor.

Frequently asked questions

An endpoint suits a tool that can push a webhook, such as a form or a line-of-business app: you map its fields to yours without writing code. The API suits a program you build: it gets back the created ID, or an error naming the field at fault.

Pick “HMAC signature” on the destination. Kasar generates the signing secret and shows it only once. The webhook-signature header holds v1, then the HMAC SHA-256 of the ID, the timestamp and the body, base64 encoded. Reject any timestamp that is too old.

Kasar waits twenty seconds for the response, then retries up to four times at growing intervals. Network errors and 5xx, 408 or 429 responses are retried; other 4xx responses are final. The destination shows “Failing” and still keeps receiving.

A “Write a record” endpoint answers 200 even when its mapping is not set, so the sending tool does not switch its webhook off. The reason sits in the endpoint log, next to the received body. Most often the structure was never captured or the mapping never saved.

Yes, via MCP: Claude or ChatGPT assembles the automation with crm_manage_automations, tries it without writing anything, then publishes it once you confirm. Leo, for its part, suggests a mapping from the paths an endpoint has actually received.

Sources

Connect your tools, keep your habits

Connect your mailbox and calendar in two minutes, the history flows in on its own.

Start for free