Let important changes move the rest of your system.
Webhooks notify an external workflow when selected Telos state changes, so automation and reporting do not depend on someone remembering to copy an update.
Subscribe the workflow to the events it needs
Open Settings → Webhooks, add the destination URL, select the state changes that matter, and give the subscription a description. Keep one subscription focused on one consumer so it is clear which workflow depends on it.
Use reliable notifications as a trigger
Telos signs webhook deliveries and retries failed sends. Use the Test action before connecting a downstream workflow, then pause a subscription when the consumer is being changed. Delete it only when the workflow is no longer part of the operating model.
Use webhooks for action, not explanation
Subscribe when another system should take an action, update a report, or start an agent run after a Telos change. Keep the decision record in Telos; use the webhook to carry that change into the places that need to respond.