cron and shell

Anything that can send a web request can report to the board. A cron job or shell script uses the REST API with the connection's token and names itself with the X-Kanbero-Agent header.

A job that reports its work

# startCARD=$(curl -s -X POST "$KANBERO_URL/api/v1/cards" \  -H "Authorization: Bearer $KANBERO_TOKEN" \  -H "X-Kanbero-Agent: nightly-backup" \  -H "Content-Type: application/json" \  -d '{"board":"my-board","title":"Nightly backup","column":"doing","source":"cron","external_id":"backup-2026-09-09"}' \  | jq -r .data.id)
# ... the work ...
# finishcurl -s -X POST "$KANBERO_URL/api/v1/cards/$CARD/complete" \  -H "Authorization: Bearer $KANBERO_TOKEN" \  -H "X-Kanbero-Agent: nightly-backup" \  -H "Content-Type: application/json" \  -d '{"summary":"142 files, 1.2 GB"}'

The source and external_id pair makes the create call safe to repeat: the same pair returns the same card instead of a duplicate, and if that card was archived in the meantime it comes back onto the board (unless the call asks for Done, which leaves it archived). A job that runs longer than the stalled window should send a heartbeat now and then, or set stale_after_minutes on the card to its expected length.