Skip to Content
TaresTares agentsDeliver findings

Deliver findings

Every finding lands on the entity’s timeline; the agent’s Deliver findings options also send it where people and systems already look. Each is a toggled row on the agent’s form:

  • Slack channel: the workspace bot posts the full finding to a channel picked from the bot’s own membership list (connect the bot under Settings). The same bot serves trigger subscriptions, where deliveries are also retried and recorded in the delivery ledger.
  • Write-back webhook: every finding is POSTed as JSON to your own automation, with an optional bearer token sent as an Authorization header. The body carries the finding and its run metadata, never a key or token:
{
  "event": "finding",
  "agent": "incident-first-look",
  "trigger": "incident",
  "key": "api-server",
  "finding": "…the incident note…",
  "run_id": "run_9f2c81d4a6b3",
  "dispatch_id": "c0f35f8210…",
  "model": "claude-sonnet-4-6",
  "rounds": 2,
  "tool_calls": 3,
  "started_at": "2026-08-14T12:01:03+00:00",
  "finished_at": "2026-08-14T12:01:35+00:00",
  "duration_s": 32.6,
  "prompt_hash": "1c9f2d"
}

Transient failures are retried; a delivery failing never loses the finding, which is already stored. Delivering a finding is not acting: the boundary stands.

  • Slack incoming webhook: the older per-agent webhook URL still works but is neither retried nor logged, and is used only when no channel is set; prefer the channel.
Last updated on
SkillsAsk