Workflow notifications

Notifications help signers notice actionable workflow steps. They do not grant signing authority and do not replace the run page.

Connect a destination

Open Organisation settings → Notifications.
Choose Slack, Discord, or Telegram.
Complete the provider’s verified sign-in or linking flow.
Select or configure the organisation destination.
Send a test when the UI offers one.

Notification identities are linked per user and organisation. Destination secrets are encrypted and shown only as masked previews.

When messages are sent

txcast queues a notification when a run is published with ready transaction work or when a transaction step later becomes ready again. Signers are resolved from the frozen signature requirement.

Messages are delivered from an outbox in the background. Provider rate limits or outages can delay a message without rolling back the workflow transition.

Troubleshooting

Confirm the integration is still linked to the same organisation.
Check the destination and provider permissions.
Open the run directly; never wait for a notification before checking a time-sensitive operation.
Reconnect an expired provider authorization.

Do not put webhook URLs, chat tokens, or other provider secrets in workflow descriptions or support messages.