Documentation

Getting started

Create your account and get going in minutes

Key concepts

The building blocks of Historis

Connect your assistant

Your assistant reads your history and writes things down for you

Historis works entirely without AI. But if you already use an assistant like Claude or ChatGPT, you can connect it: it reads your history to catch you up, and writes things down for you. Everything it writes is marked ◆, the mark of entries added by an assistant: dated, signed, correctable. You choose what each assistant can read or write, and every action it takes shows up in the activity log.

{
  "mcpServers": {
    "historis": {
      "url": "https://api.historis.app/mcp"
    }
  }
}

Rules

Reusable instructions your assistant follows

A rule is a short instruction written in plain language and saved once for your whole organization. Historis stores and indexes your rules but never runs them itself: when your assistant works on something that matches, it finds the relevant rule and applies it, marking what it did with ◆. Because rules live with your organization, every teammate's assistant follows the same playbook.

MCP Tools Reference

All tools available to your agent

Incoming webhooks

Let your other apps push events into Historis automatically.

An incoming webhook is a URL you can POST to. Whenever something happens in another tool — a payment, a form submission, a closed deal — that tool sends a small JSON payload to your webhook URL and Historis turns it into an event. No code required on the Historis side.

Example request

curl -X POST https://api.historis.app/api/webhooks/ingest/YOUR_ENDPOINT_ID \
  -H "Authorization: Bearer whk_YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: pi_3abc123" \
  -d '{
    "content": "Payment received — 450 EUR",
    "status": "open",
    "tags": ["payment"],
    "person": { "name": "Pierre Dupont", "email": "pierre@example.com" },
    "metadata": { "external_id": "pi_3abc123", "source": "stripe" }
  }'

• Only content is required. status, tags, person (name, email) and metadata are optional — a person is matched by email, or created automatically.
• Idempotency: send an Idempotency-Key header (or metadata.external_id) so a retried delivery is de-duplicated instead of creating a second event.
• The token is a secret: send it over HTTPS in the Authorization header, never in the URL. Revoke an endpoint anytime to cut it off instantly.
• Works with anything that can POST JSON — Zapier, Make, n8n, or your own backend.

Authentication

How access works

FAQ