Deliver ONE digest of everything pending in this workspace to its paired Telegram destination. Counts per queue (overdue with no signal, expectation date past with no signal, waiting on a human decision, delegations delivered and not resolved, attention requests pending), then the top items of the first three queues, at most 7 lines, each with what it is, how many days it has been waiting and its next command taken from timing.available_commands, then a closing line with the total that did not fit. The top items carry exactly the correlated buttons they would carry as an ordinary nudge; the digest never invents an operation. It is recorded in channel_deliveries with source_object_type 'workspace' and trigger 'digest', does NOT consume the 3-per-rolling-day nudge cap, and is capped at ONE digest per channel per day. A scheduled digest also runs weekly, on Monday, at the start of the channel's own local window; this endpoint is the explicit trigger and ignores the window. HONESTY: an overdue line states the expectation and that no signal was recorded, never that a commitment failed or that the other side did not answer; when no expected signal source was declared, the line says so. With nothing pending, no message is sent.

post/workspace/channels/telegram/digest

Request

  • Base URL: https://forbiz.io/api/public/agent
  • URL: https://forbiz.io/api/public/agent/workspace/channels/telegram/digest
  • Auth: HTTP bearer

Response

Digest result. delivered=false with reason 'nothing_pending' when the workspace has nothing pending.

okboolean
channel_idstring
deliveredboolean
delivery_idstring
countsobject
lines_showninteger
not_showninteger
reasonstring

Changes

No recorded changes to this operation across all 1 revision of this API.