Webhooks

Jotless can post every recap to your own website, CRM or admin as soon as it's written. Each delivery carries the recap as structured data and as a finished report in your company's look, so you can store the data, show the report, or both.

Webhooks are part of Pro. On the free plan nothing is sent.

Set it up

  1. In the app, open Settings, then For developers.
  2. Paste your endpoint's address and tap Save. It must be a public https:// address. Addresses on a private network, localhost and addresses with a user name or password are refused.
  3. Tap Make signing secret and copy it into your server's settings. It starts with jlsec_. New secret replaces it, and the old one stops working at once.
  4. Tap Send test. Your endpoint gets a test delivery and the app shows whether it answered.
  5. Optional: to send one project somewhere else, open the project, tap •••, and fill in Webhook for this project. It uses the same signing secret.

Events and payloads

EventWhen it's sent
minutes.writtenRight after a recap is written: when you tap Write recap or Rewrite, or on its own after a Pro background transcript.
minutes.sentWhen you email the recap to the project's people. Carries recipients, the number of people it went to.
testWhen you tap Send test. Sample content, report.url is null.

Each delivery is a POST with a JSON body and these headers:

HeaderValue
Content-Typeapplication/json
User-AgentJotless-Webhook/1
X-Jotless-EventThe event name, as above
X-Jotless-DeliveryA unique id, also in the body as id. A retry reuses it, so skip ids you've already handled.
X-Jotless-Signaturet=<unix seconds>,v1=<hex>, see below
{
  "id": "6f0d2c1e-…",
  "event": "minutes.written",
  "createdAt": "2026-11-20T15:41:07.000Z",
  "project": { "id": "q8Zr…", "name": "Ortega Residence" },
  "meeting": {
    "id": "m31x…",
    "title": "Framing walk",
    "startedAt": "2026-11-20T15:00:00.000Z",
    "durationMinutes": 32,
    "words": 4210,
    "speakers": { "0": "Marcus Hayden", "1": "Elena Ortega" }
  },
  "minutes": {
    "headline": "Framing passed. Drywall starts Monday.",
    "summary": "…",
    "timeline":  [{ "minute": 6, "title": "Kitchen window", "detail": "…" }],
    "decisions": [{ "text": "Kitchen window change order approved", "detail": "$1,840, signed by both owners" }],
    "actions":   [{ "task": "Send the revised schedule to the owners", "owner": "Marcus", "due": "Friday" }],
    "numbers":   [{ "label": "Change order", "value": "$1,840" }],
    "questions": ["Which bath tile, once both bids are in?"],
    "nextMeeting": "Thursday, December 4"
  },
  "report": {
    "url": "https://jotless.app/r/…",
    "html": "<!doctype html>…",
    "text": "…"
  }
}

Answer with any 2xx within 10 seconds. Anything else, a timeout or a redirect counts as a failure and is retried once straight away with the same id. Redirects aren't followed, so give the final address. Do slow work after you answer.

Verify the signature

v1 is the hex HMAC-SHA256 of <t>.<raw body>, keyed with your signing secret. Check it against the raw bytes of the body, before any JSON parsing, and reject timestamps more than five minutes from now.

Node (Express)

import crypto from "node:crypto";
import express from "express";

const app = express();

app.post("/hooks/jotless", express.raw({ type: "application/json" }), (req, res) => {
  const header = req.get("X-Jotless-Signature") || "";
  const t = /t=(\d+)/.exec(header)?.[1];
  const v1 = /v1=([0-9a-f]{64})/.exec(header)?.[1];
  if (!t || !v1 || Math.abs(Date.now() / 1000 - Number(t)) > 300) return res.sendStatus(401);

  const expected = crypto.createHmac("sha256", process.env.JOTLESS_SECRET)
    .update(`${t}.`).update(req.body)   // req.body is the raw Buffer
    .digest("hex");
  if (!crypto.timingSafeEqual(Buffer.from(v1), Buffer.from(expected))) return res.sendStatus(401);

  const event = JSON.parse(req.body);
  // event.minutes: store it. event.report.html: show it.
  res.sendStatus(200);
});

PHP

<?php
$body   = file_get_contents('php://input');
$header = $_SERVER['HTTP_X_JOTLESS_SIGNATURE'] ?? '';
preg_match('/t=(\d+)/', $header, $t);
preg_match('/v1=([0-9a-f]{64})/', $header, $v1);
if (!$t || !$v1 || abs(time() - (int)$t[1]) > 300) { http_response_code(401); exit; }

$expected = hash_hmac('sha256', $t[1] . '.' . $body, getenv('JOTLESS_SECRET'));
if (!hash_equals($expected, $v1[1])) { http_response_code(401); exit; }

$event = json_decode($body, true);
// $event['minutes'] to store; $event['report']['html'] to show.
http_response_code(200);

Test deliveries

Send test posts a test event to your account's address, signed with your secret, with the same shape as a real one: a sample project, a one-line recap and a branded report made from your current brand settings. report.url is null because there's no meeting behind it.

The app lists your five most recent deliveries under Settings, For developers, with the event, the time and the error if one failed. A delivery shows as failed when your endpoint didn't answer 2xx within 10 seconds, twice.

Show the branded report

See a sample report for a made-up builder.

Your brand

In the app, Settings, Brand: company name, logo, header colour, accent colour, a font style (sans, serif, modern or classic), a footer line, and the name and reply-to address emails come from. They apply to the emails, the hosted report and the webhook HTML at once. The fonts are email-safe system families, so the report looks the same in Outlook, Gmail and Apple Mail.

Need something else?

Zapier, Make and most CRMs accept webhooks directly. For anything else, email support@rendevo.io.