Notifications
Notifications direct eligible people back to the authoritative run page. They never grant signing or human-response authority.
Destinations
Section titled “Destinations”Organisation owners/admins can link Slack, Discord, or Telegram destinations. Keep the existing linked identity and sink configuration when authorising new workflow agents; agent reauthorisation does not relink notification providers.
Automatic lifecycle notifications
Section titled “Automatic lifecycle notifications”txcast emits sanitized, idempotent lifecycle messages for actionable human effects, transaction review/signing, execution outcomes, failures, cancellation, and other coordination state. Recipient selection comes from current organisation access and the frozen effect/account authority.
Authored notification effect
Section titled “Authored notification effect”A program may call notification.send only when its capability envelope
allows the requested channels and audience. The effect accepts bounded title
and body text, is sanitized and deduplicated, and returns an outbox identity
after acceptance.
Authored code receives no provider credentials or linked identity secrets. Delivery retries happen through txcast’s notification outbox. One run may create at most 100 authored notification effects.
Delivery and privacy
Section titled “Delivery and privacy”A delivered message may be stale by the time it is read. Open the run to inspect current effect and transaction state. Avoid putting private input values, signatures, secrets, or unnecessary calldata in authored notification bodies.