Outbound webhooks
Use Settings → Webhooks to send supported programme events to an external system.
The deployment must have outbound webhooks enabled. If the section or delivery service is unavailable, ask the platform administrator to confirm this as well as your management permission.
Configure a destination
- Agree the receiving service and event requirements with its owner.
- Open Webhooks and add a destination.
- Enter the approved endpoint and select the supported events you need.
- Save the configuration and securely transfer the signing secret shown on creation to the receiver’s administrator. It is not shown again after the reveal is dismissed.
- Verify the destination. The receiver must answer the signed handshake by echoing the challenge before it receives events. Changing the destination URL requires verification again.
- Use the available test controls and review delivery results before relying on the connection.
Webhook management requires its own permission. Use the secure secret-reveal controls only when needed to configure the receiving service; keep signing secrets out of shared documents.
Monitor deliveries
Open the destination’s deliveries panel to inspect outcomes and available retry controls. Investigate repeated failures with the receiving service’s administrator rather than creating duplicate destinations.
Journal event scope
Ordinary journal-entry notifications follow the public-sharing threshold: both the journal and entry must allow Public visibility. A notification can also occur when an existing entry first becomes public after a visibility change.
These journal event payloads contain metadata rather than the full answers or media. Collaborator reflections are excluded from these journal webhook events.
Changing a journal’s audience can therefore affect external notifications as well as the public feed. See Journal visibility.