CoNote
CoNoteWebhook

A URL for everything else you want on the timeline.

When a tool isn’t on the list — your CI pipeline, a cron job, a price change, a ten-line script — the Webhook gives you one URL to POST to. Anything that can send JSON can write an event to your timeline.

Start your logbookSee all integrations
Webhookpublished a change
Your timelineToday

Nightly backup completed — 4.2 GB

Webhook· 02:00

Deployed storefront v2.4.0 (main → 3a7f2c1)

GitHub· 09:41

What it watches

What the Webhook accepts.

The same path your own scripts use — no separate API-key system to manage.

  • One unguessable URL per webhook, secured with a shared secret
  • POST readable JSON — title, date, category — and it lands as an entry
  • Wire up CI pipelines, Zapier, cron jobs, or your own code in a few lines
  • Deduplicated by an external id, so a retry never double-logs

On the timeline

What lands on your timeline.

The events no off-the-shelf integration would ever catch — exactly as you describe them.

Tuesday, June 9

  • CI pipeline deployed api-gateway v3.1.0

    03:14 · Webhook

  • Price change pushed — Pro plan $29 → $39

    11:30 · Webhook

Sound familiar?

The day you’ll wish it was written down.

#engineeringWednesday, 09:00
TB

Tom09:00

Did the nightly data job run last night?
NW

Nadja09:04

Not sure — it fails silently. We’d only know if something downstream broke.
TB

Tom09:07

So there’s no record of whether it ran or not.

The job runs in the dark.

With the Webhook, a three-line script posts it — “Price change pushed, Pro $29 → $39” — and it’s on the timeline the moment it happens.

Setup

Live in a few lines.

  1. 01

    Create a webhook

    CoNote gives you an unguessable URL and a shared secret.

  2. 02

    POST your event

    Send JSON with a title, date, and category — from CI, a cron job, or a script.

  3. 03

    It’s on the timeline

    The event appears instantly, beside everything else that happened that day.

Questions

Custom event logging, answered.

A small JSON payload with a title, an event date, and a category — optionally an external id for deduplication. Anything that can make an HTTP POST can send it.

Each webhook has its own unguessable URL and a shared secret that every request must carry. Requests without the right secret are rejected, and the endpoint is rate-limited.

The things no off-the-shelf integration covers — a CI pipeline marking a deploy, a cron job reporting it ran, a price or config change, a manual note from a script. If it can POST, it can land on the timeline.

The Webhook is the programmatic path — the same one your own code and scripts use. There’s no separate key system to manage; you create a webhook and POST to it.

Keep digging

Track the rest of your stack.

Open the logbook.

Free plan, no card. Connect your first source and the timeline fills itself.

Start your logbook