« tlly.dev

Playbooks · Integrations

Push and webhooks

Your own systems POST numbers to a write-only address. tlly does not receive arbitrary vendor webhooks as series.

What you can track

Any number you can compute yourself: database counts, a server’s daily peak, a vendor that only offers webhooks, a spreadsheet script. The push address accepts dated points. It does not parse Stripe, Shopify or other vendors’ webhook bodies. If a vendor pushes a webhook, a small step you run (Zapier, Make, n8n, a function) must turn that event into the JSON below.

Inbound vendor webhooks are not a tlly source type. Outbound alerts are separate: set_alert_webhook and the alert email, which tlly sends when a panel changes colour or a job starts failing. A panel alerts once per crossing, and a repeat crossing within an hour does not notify again. At most 12 alert emails and 60 outbound webhooks per account per hour; both counts are kept across a restart, and the next email says how many were held back.

Credential

The push URL is the credential. It looks like https://tlly.dev/push/push_…. Anyone with it can add points. It is write-only: it cannot read data or change jobs. The owner creates it under Data sources → “Your systems push to tlly”.

Where to get it

Members area, Data sources, create the push address, and copy it. It is shown to the owner. Agents do not receive the token from list_secrets.

tlly job

There is no fetch job. POST JSON:

{"series":"signups","date":"2026-10-26","value":42}

Also {"series":"signups","points":[{"date":"2026-10-26","value":42}]} or an array of either, up to 20 series, body at most 2 MB. Then chart the series name.

Gotchas

Alert ideas

Once the series exists, set a threshold on the panel. The push itself does not alert.

Verification

Checked against push.go and the members-area copy in this repo. No third-party webhook schema is claimed.