Can I get notified when handbook procedures change?

Yes — subscribe to the handbook.procedure.* webhook events. Atender emits an outbound webhook every time a handbook procedure is created, updated, or deleted, so an external system can react without polling.

What fires

Three event types cover the content in this module:

• handbook.procedure.created — a new procedure is added.
• handbook.procedure.updated — a procedure changes in any way, including publishes, unpublishes, archives, review-state changes, translation syncs, and content edits — the payload’s data.change field describes the kind of update.
• handbook.procedure.deleted — a procedure is removed.

Each delivery carries a signed JSON payload identifying the procedure that changed. Treat it as a lightweight notification — refetch the full procedure via the public API when your integration needs the current content.

What you’d use it for

• Mirror or sync your procedures into an external source of truth — a Git repo, an internal wiki, a compliance system — and keep it current automatically.
• Trigger a review when a procedure changes, so a policy owner signs off.
• Audit changes to the internal runbook the AI follows.

Because the Handbook shapes what the AI does rather than what it says, these events suit teams that manage procedures as governed, versioned content.

How to set it up

This is a developer/admin feature, configured through the API rather than the Handbook editor. You create a subscription with POST /v1/webhooks using an API key from Settings → API Keys, list the events you want, and give Atender an HTTPS endpoint. Deliveries are signed so you can verify they’re genuine.

Full instructions and the complete event list live under Channels → API & Webhooks.

See also

• Subscribe to webhook events
• Webhook events reference
• REST API integration